B2B2C remittance fintech: what the consumer app owns and what the stablecoin settlement layer provides

A B2B2C remittance fintech is a consumer app that sells money transfers to individuals while an institutional settlement layer moves the value underneath in regulated stablecoins. The fintech owns everything the consumer can see and everything a consumer regulator will ask about: KYC, disclosures, licensing or registration in each sending market, complaints, refunds and the brand. The settlement layer owns the institutional plumbing: stablecoin settlement to a payout partner, sanctions and wallet screening on each transfer, Travel Rule data exchange and the final credit to a local bank account. This article sets out that division of labour, follows a single transfer from the app to a local account, and lists what the fintech must have in place before launch.

What does the consumer remittance fintech own?

The fintech owns the customer, and with the customer comes the full consumer-protection stack. It performs KYC on every sender under its own AML programme, including identity verification, sanctions and PEP screening at onboarding, and ongoing monitoring. It holds the licence or registration that permits it to accept funds from consumers in each sending jurisdiction: a FinCEN MSB registration and state money transmitter licences or a sponsor arrangement in the United States, a FINTRAC MSB registration and, where applicable, Bank of Canada registration under the Retail Payment Activities Act in Canada, and the equivalent in any other send market.

It also owns the consumer disclosures, the receipt, the cancellation right, the error-resolution procedure, the complaint log and the refund policy. In the United States these are not matters of preference: the Remittance Transfer Rule in subpart B of Regulation E specifies what the pre-payment disclosure must show, what the receipt must show, a cancellation window after payment and how errors must be investigated. The fintech is the remittance transfer provider in the consumer's eyes and in the regulator's, whatever happens underneath.

Finally, the fintech owns the funds flow at the consumer end. It collects the send amount through a card, a bank debit or a wallet balance, holds it under its own safeguarding rules, and instructs the settlement layer only once the consumer's funds are good. The consumer's money should never sit in the settlement layer's name.

What does the institutional settlement layer provide?

The settlement layer is a B2B service to the fintech, and its customer is the fintech, not the consumer. It provides a settlement account or wallet arrangement in which the fintech keeps custody of its float; the conversion of the fintech's fiat into a regulated stablecoin such as USDC or USDT, or acceptance of stablecoin the fintech already holds; the on-chain settlement leg to a payout partner in the destination country; the off-ramp into local currency; and the final credit through local clearing, whether that is ACH, SEPA, EFT or a comparable domestic rail.

On each transfer the layer runs the institutional controls that a consumer app is poorly placed to run alone: sanctions screening of originator and beneficiary against current lists, wallet screening of the destination address, KYT monitoring on the stablecoin leg and the attachment of Travel Rule data in IVMS101 form. It returns the outcome of each control to the fintech as a structured event, and it keeps a tamper evident audit trail so that the fintech can answer a regulator's question about any single transfer months later. It also handles the messaging where the payout partner is a bank: a pacs.008 customer credit transfer into the local rail, a pacs.002 status report back, and a pacs.004 return if the beneficiary account rejects the credit.

• The fintech owns sender KYC, consumer disclosures, the receipt, cancellation and error resolution, complaints, refunds and the licence or registration in each send market.
• The settlement layer owns fiat-to-stablecoin conversion, the on-chain settlement leg, screening on each transfer, Travel Rule data exchange, the off-ramp and the local clearing credit.
• The fintech decides whether a flagged transfer proceeds; the settlement layer supplies the screening result and blocks nothing on its own except a confirmed sanctions match.
• The fintech files suspicious activity or suspicious transaction reports on its senders; the settlement layer supplies transaction data on request to support the filing.
• Both parties reconcile daily, and the reconciliation must tie the fintech's consumer ledger to the settlement layer's transfer log by a shared reference on every item.

How does a consumer payment become a local-account payout?

Follow one transfer. A sender in the app enters a recipient's bank account details in the destination country, an amount and a purpose. The app runs its own screening on the recipient name, shows the Regulation E pre-payment disclosure with the exchange rate, fees and the amount to be received, and collects the send amount. Once the funds are good, the app calls the settlement layer with a payment instruction that carries the amount, currencies, originator and beneficiary data and a unique reference that will follow the transfer to the end.

The settlement layer screens the instruction, converts the fintech's fiat to a stablecoin or draws on stablecoin the fintech already holds, and settles on chain to the payout partner's wallet in the destination country. That partner, a licensed local institution, off-ramps into local currency and initiates a credit through domestic clearing to the recipient's account. Each step emits a status event to the fintech: screened, settled on chain, off-ramped, credited. The app maps those to the language the consumer sees and to the receipt it must retain. If the beneficiary bank returns the credit because the account is closed, the return travels back the same path, the fintech is notified with a reason code, and the consumer receives a refund under the fintech's own policy.

The consumer sees a promise and a receipt. Everything between them is a chain of named owners, each handing over a reference number and a timestamp.

Who is licensed for what, and where?

Licensing splits by which party faces which counterparty. The fintech is licensed or registered where it accepts money from consumers, because that is the activity consumer regulators regulate. The settlement layer is licensed or registered where it provides payment or settlement services to the fintech, and its payout partners are licensed where they credit local accounts. A fintech launching from Canada into two receive markets therefore needs its own FINTRAC registration and, subject to the Act's scope, Bank of Canada registration, while relying on the settlement layer's regulated status for the institutional leg and on the payout partners' local licences for the last mile.

The question a diligence team should ask is not whether the settlement layer is licensed, but whether it is licensed for the specific activity it performs for the fintech, in the place it performs it. A layer that converts fiat to stablecoin and settles on chain may need a different registration from one that only orchestrates transfers between wallets the fintech controls. Ask for the registration reference, the regulator's name and the scope of the permission, and file the answer in the vendor record.

What consumer disclosures and protections stay with the fintech?

All of them. The pre-payment disclosure must show the exchange rate, the fees, taxes collected by the provider, the total to be paid and the amount to be received. The receipt must repeat those items and add the date of availability, the recipient's details and the provider's contact and regulator information. The consumer has a cancellation right within the window the rule sets, and the fintech must refund within the period the rule sets after a valid cancellation. Errors must be investigated within the rule's deadlines. The settlement layer's speed makes the availability date easier to meet, but it does not change who signs the disclosure.

There is a design point here that is easy to miss. The disclosed exchange rate must be the rate the consumer actually receives. If the settlement layer quotes a wholesale rate that moves between disclosure and execution, the fintech must either hold the quoted rate itself or obtain a firm quote from the layer that is valid for at least the disclosure window. A model in which the rate is fixed only when the stablecoin is off-ramped is a compliance problem, not a treasury problem.

What does the fintech need to build before launch?

The build is smaller than a full remittance stack but it is not small. The fintech must have a licence, registration or sponsor in each send market and a written confirmation of scope; a payout partner, through the settlement layer or directly, in each receive market, with the local clearing rail and cut-off times documented; a consumer ledger that records every transfer with the shared reference; a disclosure and receipt engine that meets the Remittance Transfer Rule or the local equivalent; a complaint and refund procedure with a named owner; and a daily reconciliation that ties the consumer ledger, the fintech's float and the settlement layer's transfer log to zero.

• Confirm in writing which party holds the stablecoin float at each step and in whose name, because that determines whose safeguarding rules apply.
• Run a full transfer in a test environment from app to local account and back as a return, and check that every status event arrives with the shared reference.
• Prepare the regulator's likely first questions: the licence scope, the flow of funds diagram, the vendor file on the settlement layer and the Travel Rule data-flow diagram.
• Write the consumer-facing plain-language explanation of what happens when a transfer is held for review, and test it on someone outside compliance.

Where StableNet fits

StableNet, built by SpendTheBits, is a cross border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs, and B2B2C is one of its three commercial models: a fintech offers the service to consumers while StableNet supplies the settlement layer beneath the app. Settlement runs in regulated stablecoins such as USDC and USDT on public blockchains, completing in minutes with on chain auditability, and customers keep custody, so the fintech's float stays in its own name. Rails out include local fiat through ACH, SEPA and EFT for last-mile delivery, alongside SWIFT payout where a corridor needs it, with pacs.008, pacs.002 and pacs.004 messages tracked end to end by UETR. Sanctions and PEP screening, wallet screening, KYT and FATF Travel Rule data in IVMS101 form are built in, with a tamper evident audit trail. SpendTheBits is a Bank of Canada registered payment service provider and a named finalist in the Swift Hackathon 2026 Technical Challenge.