Skip to main content

How SchoolSet Handles Credit Card & ACH Information

Overview of how SchoolSet handles credit card and ACH wallets, merchant accounts, and updates to existing payment plans.

Written by Aron Lampin
Updated over a month ago

Keeping your families’ and donors’ financial information secure is a top priority at SchoolSet.
SchoolSet is a PCI‑compliant platform, which means we follow strict industry standards for handling payment data.

This article explains:

  1. Why SchoolSet does not store credit card or ACH details

  2. Where payment data is actually stored

  3. How multiple merchant service accounts work

  4. Why payment data cannot be transferred between gateways

  5. How payments can be moved within the same merchant provider (e.g., between two Sola accounts)

  6. Updating cards/ACH for existing plans inside SchoolSet


1. SchoolSet does not store credit card or ACH information

For security and compliance reasons:

  • SchoolSet never stores full credit card or ACH (bank account) details.

  • We cannot access, export, or show full payment numbers.

  • Full payment data cannot be retrieved from our system — it simply isn’t stored.

SchoolSet only keeps secure tokens returned by your payment gateway that allow us to process payments safely.

Key point: SchoolSet never holds sensitive payment data, so it cannot be accessed or provided to you.


2. Payment data is stored with your merchant service provider

When a payer enters card or bank information:

  • It goes directly from their browser to the merchant service provider (e.g., Sola, Stripe, Banquest).

  • The provider stores the sensitive information.

  • SchoolSet receives a token that represents the card/ACH for billing.

Key point: Payment gateways, not SchoolSet, store all sensitive card and ACH details.


3. Using multiple merchant accounts: data does not sync between them

If your organization uses multiple merchant accounts (for example: Sola + Stripe + Banquest):

  • A card or ACH entered under Sola exists only inside Sola’s secure vault.

  • It will not appear in Stripe or Banquest.

  • To use a payment method with a different provider, it must be re‑entered.

Key point: Each merchant provider stores its own vault. Payment methods do not sync or transfer across providers.


4. Payment details cannot be transferred between gateways (permanent limitation)

Payment methods cannot be migrated, imported, copied, or transferred between providers — ever.
This is a permanent limitation based on how PCI compliance and gateway security work.

Examples that are not possible:

  • Stripe → Sola

  • Sola → Banquest

  • Banquest → Stripe

  • Any provider → any other provider

Even within one organization:

  • Switching gateways requires families or donors to re-enter their payment details.

Key point: Payment methods are permanently tied to the gateway where they were originally entered.


5. Moving payment data within the same merchant provider

If you have multiple accounts under the same merchant provider (e.g., two Sola accounts):

  • The merchant service provider (not SchoolSet) may be able to move payment data between the two accounts.

  • This is handled directly by the merchant provider, not by SchoolSet.

  • You or your school can reach out:

    • to your merchant provider rep, or

    • to SchoolSet Support, who can help coordinate if needed.

Key point: Only the merchant provider can move data between their own accounts (e.g., Sola → Sola). SchoolSet cannot perform or initiate this transfer.


6. Updating cards/ACH on existing plans in SchoolSet

If a user adds a new card or ACH account (a new “wallet”) to SchoolSet:

  • You do not need to create new plans or subscriptions.

  • Existing plans can be updated to charge the new payment method.

  • This is fully supported and does not require recreating anything.

This gives families and organizations flexibility when:

  • Cards expire

  • ACH accounts change

  • A payer wants to switch to a new payment method

Key point: Once the new wallet exists in SchoolSet, you can simply update the plan’s payment method — no need to recreate plans.


Summary

  • SchoolSet is PCI‑compliant and does not store any sensitive payment data.

  • All card/ACH information lives with your merchant service provider.

  • Payment info does not sync across different providers (Sola ↔ Stripe ↔ Banquest).

  • Payment data cannot be transferred between providers under any circumstances.

  • If you have multiple accounts with the same provider (e.g., two Sola accounts), the provider may be able to move payment data — contact Support or your provider to explore this.

  • Existing SchoolSet plans can be updated with new wallets without needing to recreate any plans.

Did this answer your question?