Adding remittances to a US neobank: the Remittance Transfer Rule, disclosures, and pricing

A US neobank that lets consumers send money abroad usually becomes a remittance transfer provider under Regulation E. That means a pre-payment disclosure, a receipt with the date funds arrive, a 30-minute cancellation right, and an error process. BlindPay's locked payout quotes return the exact rate, fees, and amount received, which is what those disclosures need.

Most guides on remittances talk about cost. This one covers the rules a US neobank has to build into the send-money screen, and how pricing fits inside them. It is part of our guide to building a neobank. For the cost side, see stablecoin remittance costs vs traditional transfers.

This is educational content, not legal advice.

Key takeaways

• The rule covers consumers in a US state sending money abroad for personal purposes, above $15.
• There is a safe harbor at 500 or fewer transfers a year, in both the prior and current year.
• The disclosure names five numbers. A locked quote gives you all of them.
• Senders can cancel within 30 minutes if funds haven't been deposited, with a refund in three business days.
• Low fees come from fewer intermediaries, not from hiding the FX margin.

When does the Remittance Transfer Rule apply?

It applies when a consumer asks you to send money electronically to a recipient abroad, and you do it in the normal course of business.

The definitions in 12 CFR 1005.30 set the scope:

• Sender: a consumer in a US state, sending primarily for personal, family, or household purposes. Business payments fall outside.
• Designated recipient: a person the sender names to receive the money at a location in a foreign country.
• Small transfers: transfers of $15 or less are excluded.
• Safe harbor: a provider that made 500 or fewer remittance transfers in the previous calendar year, and makes 500 or fewer in the current year, is not treated as providing them in the normal course of business. A provider that crosses 500 has up to six months to start complying.

Most neobanks that market a send-money-abroad feature will cross 500 quickly. Plan to comply from launch.

Who is the provider when a neobank uses a payout API?

Usually the company the consumer asks to send the money, which is the neobank.

The consumer sees your app, your price, and your receipt. Your payout provider executes the payment, but the disclosures, cancellation, and error handling are customer-facing duties. Work out the split with counsel and write it into your provider agreement. Our neobank compliance checklist has a row for consumer disclosures; this feature fills it in.

What must the pre-payment disclosure show?

Five core numbers, before the sender pays. 12 CFR 1005.31 names them:

If covered third-party fees apply, the disclosure also shows the Transfer Amount in the receiving currency and those "Other Fees." The receipt repeats the numbers and adds the Date Available in the recipient's country, the recipient's details, and a statement of the sender's error resolution and cancellation rights.

How do cancellation and refunds work?

The sender can cancel for 30 minutes after paying, unless the money already landed.

Under 12 CFR 1005.34, a request received within 30 minutes of payment must be honored if it identifies the sender and the transfer and the funds have not been picked up or deposited into the recipient's account. The refund covers the full amount, fees included, within three business days.

Instant rails change the product question. A SPEI or Pix payout can land in seconds, so the window often closes in practice before 30 minutes pass. Two options:

1. Execute immediately and show "Cancel" only while the payout hasn't been deposited.
2. Hold execution for a short window so the sender can cancel. You then need a fresh quote at execution, and a new disclosure if the numbers change.

Option 1 fits a fast-transfer promise. Either way, write the rule into your status logic.

How do error claims work?

The sender has 180 days after the disclosed Date Available to report an error. You investigate within 90 days.

The best defense is a correct Date Available. Base it on each rail's real timing and cut-offs, covered in payout cut-off times on weekends and holidays.

How should a neobank price a remittance?

Price with one visible fee and an FX margin you're willing to show, then disclose both.

Remittances are expensive in the traditional model because several parties each take a cut: the sending bank, correspondents, and the paying agent. A transfer funded in stablecoins and paid over a local rail cuts most of those hops. You keep the margin in your own fee instead of losing it to intermediaries.

Three pricing patterns:

• Flat fee, near-market rate. Easy to read. Works for small, frequent transfers.
• No fee, FX margin. Looks free, but the margin must show in the Exchange Rate and Total to Recipient.
• Tiered fee by amount. Fair for large transfers. Keep tiers simple enough to disclose.

On BlindPay, a partner fee adds your margin to each transaction, so the quote you show already includes it.

Worked example: a $500 transfer to Mexico

Illustrative numbers only. A user in Texas sends $500 to their mother's CLABE account in Mexico.

The app requests a locked quote, renders these five lines, starts a countdown to the quote expiry, and executes on confirm. The receipt shows the same numbers, the Date Available, and the rights text. If the user waits past the expiry, the app re-quotes and shows a fresh disclosure.

What is the sender flow, step by step?

1. Pick or add the recipient and bank account.
2. Enter the amount to send, or the amount to arrive.
3. Get a locked quote.
4. Show the pre-payment disclosure with a countdown.
5. Confirm and take payment from the user's balance.
6. Execute the payout before the quote expires.
7. Send the receipt with Date Available and rights.
8. Track status by webhook and notify on arrival, or on failure.

Transparency checklist

• All five disclosure terms, named as the rule names them.
• Rate shown to 2 to 4 decimal places.
• Date Available based on the real rail, not a marketing promise.
• Cancellation button logic tied to payout status.
• Rights text on every receipt.
• Disclosure and receipt versions stored with each transfer.

What are common mistakes?

• Disclosing an estimated amount when a locked quote was available.
• Executing after the quote expired, so the delivered amount differs from the disclosure.
• Promising "instant" when the rail has cut-offs.
• Showing "no fees" while the margin hides in an undisclosed rate.
• Treating the payout provider as the party responsible for consumer disclosures.

How does BlindPay fit?

BlindPay is the payout layer behind the send button. A payout quote locks the exchange rate and fees for 5 minutes and returns the exact amount the recipient receives. That is the Exchange Rate and Total to Recipient for your disclosure. Quoting on the receiver side lets you promise an exact amount in local currency.

• Local rails: Pix in Brazil, SPEI in Mexico, ACH Colombia, Transfers 3.0 in Argentina, SEPA, Faster Payments, and SWIFT (POBO/COBO) elsewhere.
• Your margin in the quote through partner fees.
• Status webhooks so cancellation and Date Available logic follow the real payout. If a payout fails after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet; on Pix and other non-USD local rails the refund is automatic.
• Compliance in the flow: KYC on the sender, sanctions screening, and Travel Rule data on each transfer.

For corridor choice, see SWIFT vs local rails for neobank transfers.

What to do next

Draft your disclosure screen with the five terms above, then request a test quote on a development instance and map each field to a line. The payout quotes docs show the request and response.