CA prepaid program vs US neobank program

Canada vs United States (two BaaS structures)

Same job: Run a sponsor-bank card program where a fintech owns the UX and the bank is issuer of record.

The decision: Same BaaS shape on both sides (a fintech program manager owns the UX and ledger, a sponsor bank is issuer of record and holds cardholder funds in an FBO account, settlement runs bank-to-bank). The differences are jurisdiction and structure: a Canadian Schedule I prepaid program (OSFI / FCAC) versus a US neobank debit program (OCC / CFPB) that also carries a program-manager-funded reserve to collateralize program losses.

The diff

Pulled from each rail’s audited flow. Highlighted rows are where the two differ.

Attribute	Canadian prepaid card via Schedule I sponsor	US neobank debit via sponsor bank
Jurisdictiondiffers	CA	US
Primary railsdiffers	Visa · EFT / bank transfer	Visa Debit · ACH
Rails on the legsdiffers	EFT / load · Program ledger · Visa · VisaNet · Visa clearing · Intrabank transfer · Visa settlement (interbank) · Merchant funding	ACH / payroll · Core ledger · Visa Debit · Network clearing · Intrabank transfer · Network settlement (interbank) · Merchant funding · Bank transfer · Program ledger
Currencydiffers	CAD	USD
Number of partiesdiffers	9	10
Settlement venuediffers	FBO cardholder funds account · Sponsor bank settlement account	Pooled FBO account · Sponsor bank settlement account · Program reserve account
Settlement timingdiffers	T+1 (EFT batch) · T+0 end-of-day batch · T+1 net settlement · T+1–T+2 batch payout	Effective date (next-day or Same Day ACH) · T+0 end-of-day batch · T+1 net settlement · T+1–T+2 batch payout · Per program agreement
Message standard	n/a	n/a

Both flows, side by side

Canadian prepaid card via Schedule I sponsor

Visa · EFT / bank transfer · CAD · CA

The fintech owns the customer experience and ledger, but the Schedule I sponsor bank is issuer of record and holds cardholder funds in an FBO account. Loads increase the FBO pool and fintech ledger. Card spend authorizes merchant to acquirer to Visa to the sponsor issuer. Visa carries the authorization and clearing messages; the money settles bank-to-bank. Settlement runs from the FBO through the sponsor bank's own settlement account to the acquirer's settlement bank, and the acquirer funds the merchant net of fees.

How it moves, step by step

1
moneyCardholder FBO cardholder funds account
Load prepaid balance
EFT / load · T+1 (EFT batch)
2
messageFintech program manager FBO cardholder funds account
Ledger mirrors FBO
Program ledger
3
messageCardholder Merchant
Card spend
Visa
4
messageMerchant Merchant acquirer
Auth to acquirer
Visa
5
messageMerchant acquirer Visa network
Route auth to network
VisaNet
6
messageVisa network Card processor
Route to processor
VisaNet
7
moneyCard processor Schedule I sponsor bank
Issuer approval
VisaNet
8
messageMerchant acquirer Visa network
Clearing records
Visa clearing · T+0 end-of-day batch
9
moneyFBO cardholder funds account Sponsor bank settlement account
Cover card settlement
Intrabank transfer · T+0 end-of-day batch
10
moneySponsor bank settlement account Merchant acquirer
Issuer settles acquirer (bank-to-bank)
Visa settlement (interbank) · T+1 net settlement
11
moneyMerchant acquirer Merchant
Merchant funded net of fees
Merchant funding · T+1–T+2 batch payout
12
messageCard processor Fintech program manager
Post spend to ledger
Program ledger

Grounded in operator & regulator sources

US neobank debit via sponsor bank

Visa Debit · ACH · USD · US

The neobank provides the app and ledger while a sponsor bank holds customer funds in a properly titled FBO account and issues debit cards. Debit authorization routes through the network to the sponsor issuer. The network carries the authorization and clearing messages and nets each day's positions; the money settles bank-to-bank. Settlement runs from the FBO through the sponsor bank's own settlement account to the acquirer's settlement bank, the merchant is funded net of fees via its acquirer, and a program-manager-funded reserve collateralizes program losses.

How it moves, step by step

1
moneyCustomer Pooled FBO account
Deposit funds
ACH / payroll · Effective date (next-day or Same Day ACH)
2
messageNeobank program manager Pooled FBO account
Customer subledger
Core ledger
3
messageCustomer Merchant
Debit purchase
Visa Debit
4
messageMerchant Merchant acquirer
Auth to acquirer
Visa Debit
5
messageMerchant acquirer Debit network
Route auth to network
Visa Debit
6
messageDebit network BaaS / card processor
Processor decisioning
Visa Debit
7
moneyBaaS / card processor Sponsor bank issuer
Issuer approval
Visa Debit
8
messageMerchant acquirer Debit network
Clearing records
Network clearing · T+0 end-of-day batch
9
moneyPooled FBO account Sponsor bank settlement account
Cover card settlement
Intrabank transfer · T+0 end-of-day batch
10
moneySponsor bank settlement account Merchant acquirer
Issuer settles acquirer (bank-to-bank)
Network settlement (interbank) · T+1 net settlement
11
moneyMerchant acquirer Merchant
Merchant funded net of fees
Merchant funding · T+1–T+2 batch payout
12
moneyNeobank program manager Program reserve account
Fund program reserve
Bank transfer · Per program agreement
13
messageBaaS / card processor Neobank program manager
Post transaction
Program ledger

Grounded in operator & regulator sources

See each in the studio

Canadian prepaid card via Schedule I sponsorAudited template · loads instantly US neobank debit via sponsor bankAudited template · loads instantly

All rail comparisons

Educational, plain-English explainers. Not legal, compliance, tax, or financial advice. These cover fundamentals, not current fees, limits, or rates (which change). Rails and parties vary by program and country, so verify specifics against primary sources. Last reviewed June 2026.