A US neobank that lets customers send dollars abroad is usually a remittance transfer provider under Regulation E (Reg E), which means every transfer needs a pre-payment disclosure, a receipt, a 30-minute cancellation right and a formal error process. The rule is subpart B of 12 CFR part 1005, issued by the Consumer Financial Protection Bureau (CFPB), and it reaches the send-money screen. A missed disclosure item is a defect on every transfer the screen sends, a cancelled transfer is a full refund inside three business days, and every notice of error starts a 90-day investigation clock.
This post reads 12 CFR 1005.30 to 1005.36 and the Official Interpretation of 1005.31, and maps each disclosure field to the payout leg. Whether the rule binds a given product is for counsel, and FinCEN registration is a separate federal duty it neither replaces nor depends on.
Who the rule covers, and where the 500-transfer line sits
The definitions are in 12 CFR 1005.30. The sender is a consumer in a US state who asks, primarily for personal, family or household purposes, for money to go to a designated recipient in a foreign country. A transfer counts even if it is also an electronic fund transfer ((e)(1)), so subpart A of Reg E can apply on top.
Two carve-outs matter. Transfers of $15 or less are excluded under paragraph (e)(2)(i). Paragraph (f)(2)(i) deems a person not to provide remittance transfers in the normal course of business if it made 500 or fewer in the previous calendar year and makes 500 or fewer in the current one, a threshold set by the 2020 amendment (85 FR 34904, June 5, 2020).
Who the provider is when a sponsor bank sits behind the app
The provider is any person that provides remittance transfers in the normal course of its business, whoever holds the charter. Section 1005.35 makes a provider liable for violations by an agent acting for it. A payout provider is not automatically an agent, and an app is not automatically the provider; the contract and the facts decide. This post assumes the neobank, or its sponsor bank by agreement, is the provider of record.
The pre-payment disclosure, item by item
Section 1005.31(b)(1) lists eight items. Under paragraph (e)(1) the sender gets them when requesting the transfer but before paying, and under paragraph (f) they must be accurate when payment is made, except where section 1005.32 permits an estimate. An item that does not apply may be left off or shown as "N/A" (comment 31(b)-1).
The eight pre-payment items in 12 CFR 1005.31(b)(1), and what feeds each one in a Lumx-backed payout.
Para. | Term on the screen | What fills it |
(i) | Transfer Amount (USD) | The amount the sender entered |
(ii) | Transfer Fees, Transfer Taxes (USD) | The neobank's own fees and taxes. A Lumx partner fee on a locked quote is part of the quote, and whether it can sit in the rate or must be a Transfer Fee is for counsel |
(iii) | Total (USD) | Sum of (i) and (ii) |
(iv) | Exchange Rate, 2 to 4 decimal places | The rate actually applied, from the locked quote |
(v) | Transfer Amount (local currency) | Only if covered third-party fees apply |
(vi) | Other Fees (local currency) | Covered third-party fees, if any |
(vii) | Total to Recipient (local currency) | The final target amount in the quote |
(viii) | Non-covered fees statement | Only where such fees or taxes do or may apply |
The locked quote is USDC to local currency, but the sender funds in USD, so the neobank decides with counsel how the USD-to-USDC leg shows up in (i), (iii) and (iv), where the Exchange Rate runs from funding currency to receiving currency.
Items (v) and (vi) drop out when no covered third-party fee applies (comment 31(b)(1)-2). Lumx does not deduct a fee from the amount that reaches the recipient on a Pix (Brazil's instant payment system, run by the Central Bank) or SPEI (Mexico's interbank transfer system, run by Banxico) payout, so (v) and (vi) can stay off that screen unless another party imposes a fee. Non-covered fees, which the recipient's institution charges for receiving the money, get the (viii) warning statement, not a deduction (1005.30(h)).
For written and electronic disclosures, paragraph (c) sets grouped items, close proximity, a minimum eight-point font, equal prominence and segregation from unrelated content. Paragraph (a)(5) exempts disclosures made via mobile application from retainability and from the grouping, proximity, font-size and segregation rules, but only for a transaction conducted entirely by telephone via mobile application or text message, with the cancellation-rights statement given before payment. The (viii) statement must still follow the Total to Recipient, and (c)(3) exempts the font size, not equal prominence. A neobank with a web flow builds to the full paragraph (c).
What the receipt adds to the disclosure
The receipt under 1005.31(b)(2) is due when payment is made ((e)(2)). It repeats items (i) through (viii) and adds six:
The Date Available.
The recipient's name and contact details.
An error-resolution and cancellation statement, in the wording of Model Form A-37 or similar.
The provider's name, telephone number and website.
A statement that the sender may contact the State agency that licenses or charters the provider, if any, and the CFPB.
The Transfer Date, for transfers scheduled three or more business days ahead.
Paragraph (b)(3) allows one combined disclosure shown before payment, with proof of payment afterward. The Date Available must be exact: a range or an estimate does not comply, and a provider that does not know the date discloses the latest one, optionally with "may be available sooner" (comment 31(b)(2)-1). A late-evening US send can carry the next calendar day in Brazil, so store the Date Available as a date in the recipient's country; a UTC timestamp can show the wrong day.
When can a neobank show an estimate?
Section 1005.32 is where product teams assume flexibility that is not there. The temporary exception for insured institutions expired on July 21, 2020. The permanent ones in paragraph (b) are conditional: certain countries where local law or method rules out an exact figure ((b)(1)), transfers scheduled five or more business days ahead ((b)(2)), and, for an insured institution only, an estimated exchange rate within 1,000 transfers to that country in the prior year ((b)(4)) or estimated covered third-party fees within 500 to that recipient institution ((b)(5)), when sent from the sender's account with it.
A neobank that is not itself an insured institution cannot use (b)(4) or (b)(5), and a prepaid account counts as the sender's account only if it is a payroll card or government benefit account, so the account type decides whether a sponsor bank can rely on them. An estimate is labeled "Estimated" (1005.31(d)). Without an exception the plan is exact figures, the design reason to work from a rate locked before the sender confirms.
When I scope a US payout integration, I draw the disclosure screen before I write the payout call. A payout that works in sandbox does not tell me which amount the sender confirms, which clock the quote runs on, or what the app does at minute thirty-one. A missing field costs a wireframe edit on day one and a rework in production later.
How does the rule affect pricing?
The rule does not regulate how much a neobank charges. It regulates whether the sender can see it.
A quote that carries a partner fee returns a base and a final amount, and the sender-facing numbers have to match the final one. The fee lowers the final rate and target amount instead of appearing as its own line, while the rule asks for the provider's fees under (b)(1)(ii) and the rate actually used under (b)(1)(iv). Where a partner fee falls is for counsel. What to charge is in how stablecoin payout pricing works.
Rounding is the quiet trap. The screen shows a rate rounded to two to four places, but amounts are computed from the unrounded rate (comment 31(b)(1)-3). In the Lumx remittances guide, 500.00 USDC at a final rate of 5.1636 returns a final target amount of 2,581.81, a cent more than 500.00 times 5.1636. Show the amount the quote returns, not one recomputed from the displayed rate.
Lumx's docs describe locks of 30 seconds, one minute and five minutes; only the 30-second lock is free of a volatility fee. A provider need not hold terms for any period, but if a disclosure is inaccurate when the sender pays, new disclosures come first (comment 31(f)-1). The lock has to outlast the confirmation screen, and an expired quote means a new disclosure, not a retry.
How do cancellation and error windows work on fast rails?
The 30-minute right is in 1005.34. An oral or written request received within 30 minutes after 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 is the full amount, fees included, within three business days of the request. The right runs at any hour (comment 34(a)-3).
The deposit condition is what changes on fast rails. Pix and SPEI payouts are instant on a 24/7/365 rail per the Lumx cut-off table, so funds are usually in the recipient's account long before the window closes. Two designs follow: execute at once and show cancel only until deposit, or hold execution for a short window and show a fresh disclosure if the numbers move, at a cost in speed. Either way, key the cancel button off the transaction status webhooks and have counsel decide which status ends the right; a status mapped wrongly can turn a cancellation request into a refund the neobank may not recover.
The error process is in 1005.33. A notice is timely within 180 days of the disclosed Date Available. The provider decides within 90 days of receipt and reports the result within three business days after finishing. A late payout caused by an investigation that fraud screening, the Bank Secrecy Act of 1970 or OFAC (the US Treasury sanctions office) rules require is not an error under paragraph (a)(1)(iv)(B). Paragraph (h) shields a provider from a wrong account number only on five conditions, including a warning before payment. Scheduled transfers follow 1005.36. Keep the disclosure version shown with each transfer: 1005.13(b)(1) requires evidence of compliance for at least two years.
When the Remittance Transfer Rule is the wrong frame
Four situations fall outside it, and the AML obligations fintechs carry still apply: a business sender, a provider inside the 500-transfer safe harbor, a transfer of $15 or less, and a recipient in the United States. A stablecoin payout is also the wrong tool where no local rail fits the recipient's account type; check the supported countries list first. The Latin America cross-border comparison covers the traditional alternative, and the Lumx and BlindPay comparison provider selection.
The payout leg with Lumx behind a Reg E screen
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in. SWIFT payouts run in USD.
Lumx is not a bank. The remittances guide in the Lumx docs describes the flow: each sender is onboarded as an individual customer who accepts the terms of service and completes KYC (know your customer, the verification of an individual), the wallet is funded in the home currency, the recipient is registered as a destination, and an off-ramp runs against a locked rate. USD funding runs through a named virtual account, which can take up to one business day to activate per the accounts documentation. With a prefunded wallet, whether the 30-minute clock starts at the deposit or at the confirmation is for counsel; payment is made, for example, when it is authorized (comment 31(e)-2).
Each Reg E field has a source. The locked quote returns a base and a final target amount, a base and a final exchange rate, and an expiry time, and the off-ramp moves through transferring stablecoin, trading, transferring fiat and success, with a webhook on each change. Rails and settlement times are on the coverage page, and the operator map shows who performs which leg. See also the stablecoin corridor explainer, global payments, USDC to COP and what stablecoin banking means.
Pix to Brazil (USDC to BRL) and SPEI to Mexico (USDC to MXN) run 24/7/365 per the Lumx cut-off table, which also lists Banxico's non-business days for SPEI, so set the Date Available in the recipient country. A transfer can be held for an RFI (request for information, a compliance hold that asks for a document), the case the investigation exception in 1005.33 describes, and the cut-off page adds up to two business hours of review on larger transfers, so copy should not promise a date it cannot keep. Per the sender of record page, a Pix recipient sees Lumx on the statement and a SPEI recipient sees the customer's registered name, so show the sender name per rail on the support screen.
Methodology and sources
12 CFR 1005.30 through 1005.36 and 1005.13 were read on October 30, 2026 on the Cornell Legal Information Institute site, linked above, with the Official Interpretations of 1005.31 and 1005.34 in the supplement to part 1005. The eCFR blocks automated readers, so it is cited by name without a link; its API listed Title 12 as current through October 28, 2026 and July 21, 2020 as the latest amendment to subpart B. The Appendix A model forms and the CFPB's country list for the (b)(1) exception were not read.
Lumx statements come from docs.lumx.io pages on remittances, exchange rates, partner fees, accounts, webhooks, sender of record and cut-off times, read on October 30, 2026.
Verified on October 30, 2026. Operational context, not legal, tax, or investment advice. 12 CFR part 1005, subpart B (sections 1005.30 to 1005.36), section 1005.13 and the Official Interpretation of 1005.31 checked against the Cornell LII text on October 30, 2026. Lumx documentation checked against docs.lumx.io on October 30, 2026.
Cover photo: Adrien Olichon on Unsplash.
Does the Remittance Transfer Rule apply to a US neobank?
It applies to a person that provides remittance transfers for consumers in the normal course of business. Transfers of $15 or less are excluded, and a provider with 500 or fewer in the previous and current calendar year is deemed outside it.
What must the pre-payment disclosure show?
Section 1005.31(b)(1) lists eight items, from Transfer Amount to a statement on non-covered fees. All must be accurate when the sender pays, unless an estimate is permitted.
How long does a sender have to cancel a remittance transfer?
A request received within 30 minutes after payment must be honored if it identifies the sender and the transfer and the funds are not yet picked up or deposited. The refund is the full amount, fees included. On rails that settle in seconds, the deposit condition usually ends the right first.
How long does a sender have to report an error?
Notice is timely if received within 180 days after the disclosed Date Available. The provider decides within 90 days and reports the result within three business days after finishing.
