Customers ask how to convert stablecoins into bank deposits for a practical reason: they want the money back in an account they understand, with insurance and a statement. Banks ask the same question from the other side, because the answer determines what they record, when a deposit liability exists and when deposit insurance applies. The GENIUS Act and the agency proposals of 2026 now give both sides a clear sequence.
This article walks through that sequence as it works between a stablecoin issuer and a bank, and then describes the shorter path available when the same bank stands behind both instruments.
Two instruments, one customer
A payment stablecoin is an obligation of its issuer. Section 2 of the GENIUS Act defines it as a digital asset used for payment or settlement that the issuer is obligated to convert, redeem or repurchase for a fixed amount of monetary value. The same definition excludes deposits, including deposits recorded using distributed ledger technology.
A deposit is an obligation of a bank. The FDIC's April 2026 proposal states that deposit insurance does not depend on the technology used to record the deposit, and that reserves held at a bank to back a stablecoin are not insured to the stablecoin's holders on a pass-through basis. Converting between the two therefore means ending one legal relationship and starting another. The steps below are how that happens.
Step one: redemption by the issuer
The customer asks the issuer to redeem. Section 4 of the Act requires a permitted issuer to publicly disclose a redemption policy that establishes clear and conspicuous procedures for timely redemption, to disclose all purchase and redemption fees in plain language, and to give at least seven days' notice before changing those fees. The FDIC proposal would define timely as no later than two business days after the request.
Redemption is for the fixed amount the token represents, one dollar for a one-dollar token, not for whatever the token last traded at. Before paying, the issuer runs the checks the Act imposes on it as a financial institution under the Bank Secrecy Act: identity, sanctions screening and transaction monitoring. A request can be held, investigated or blocked at this stage. When the checks pass, the issuer burns or retires the tokens and releases dollars from its reserves.
Step two: settlement into the account
The dollars travel to the customer's bank over an ordinary rail: ACH, wire, RTP, FedNow or, when the issuer's reserve account sits at the same bank, a book transfer. The receiving bank credits the customer's account, and at that moment a deposit liability exists. From then on the balance is insured like any other deposit, subject to ownership category and limits. Nothing earlier in the chain was insured to the customer.
The bank treats the credit as it treats any incoming funds. It knows the customer through its own onboarding, it sees the originator of the payment, and it applies its monitoring to the pattern. Two things are specific to this flow and worth recording explicitly: that the funds are redemption proceeds from a named issuer, and which wallet they came from, because a later examiner question about source of funds will start there.
| Stage | Who acts | What the customer holds | Insured |
|---|---|---|---|
| Token in wallet | Customer | A claim on the issuer | No |
| Redemption request and checks | Issuer | A pending claim | No |
| Dollars in transit | Issuer and payment rail | A payment in process | No |
| Credit to the account | Bank | A deposit | Yes, subject to ownership category and limits |
Going the other way
Turning a deposit into a stablecoin runs the sequence in reverse, and one point deserves emphasis. The customer leaves deposit insurance at the moment the bank debits the account and the issuer mints the token. That is a disclosed, recorded event in a well-designed product and never a side effect of a transfer. An issuer that mints only after the funds have arrived has no tokens in existence without backing, which keeps its monthly reserve report simple. We explain the two instruments and their jobs in tokenized deposits vs stablecoins, and the status of the issuer in what is a permitted payment stablecoin issuer.
The one-step version
When the bank's own subsidiary is the issuer and the bank offers a tokenized deposit as well, the trip no longer needs a payment rail. In the LedgerBridge Regulated Money Platform a customer who converts a stablecoin into a deposit, or a deposit into a stablecoin, does it in a single atomic transaction inside the same wallet. The stablecoin is burned and the deposit token is minted together, with the backing funds moving in lock-step under a two-phase commit. There is no bridge wallet and no in-between state.
The legal consequences are unchanged. The customer still moves from an issuer's obligation to a bank deposit, insurance still starts when the deposit exists, and the same identity, sanctions and monitoring checks still run. What changes is that all of it happens in one recorded step on one audit trail, and the customer sees one balance throughout. The design is patent-pending. Whether a tokenized deposit is insured is covered in are tokenized deposits FDIC insured, and the payment experience built on it in our payments product.
If you are designing either flow for your institution, bring your compliance team to a working session.
Frequently asked questions
How long does it take to convert a stablecoin into a bank deposit?
Under the FDIC's April 2026 proposal, a permitted issuer would have to redeem no later than two business days after the request. Settlement into the customer's account then depends on the rail used, from near real time on RTP or FedNow to one or more days on ACH. When the issuer and the deposit are at the same bank, conversion can be a single immediate transaction.
Is a stablecoin insured once it reaches my bank?
The stablecoin itself is never insured. Deposit insurance applies to the deposit the bank creates when it credits the customer's account with the redemption proceeds, subject to ownership category and limits. Under the FDIC proposal, reserves that an issuer holds at a bank are not insured to the stablecoin's holders on a pass-through basis.
Can a stablecoin be redeemed for less than its face value?
A payment stablecoin is defined by the issuer's obligation to redeem it for a fixed amount of monetary value, and the Act requires the issuer to disclose any redemption fees in plain language and give at least seven days' notice before changing them. Market prices on exchanges may vary, but redemption with the issuer is for the fixed amount, less any disclosed fee.
Does the bank need to identify a customer who is converting?
The bank already knows its own depositor through its customer identification program, and it applies its monitoring to the incoming funds as it does to any payment. The issuer, as a financial institution under the Bank Secrecy Act, runs its own identity and sanctions checks before redeeming. Both sets of checks apply regardless of the technology used.
Can a deposit be turned back into a stablecoin?
Yes, by reversing the sequence: the bank debits the account, funds move to the issuer's reserves, and the issuer mints the token to the customer. The customer leaves deposit insurance at that point, so the step should be disclosed and recorded as a distinct transaction. On a platform where the bank stands behind both instruments, it can be a single atomic conversion.
This article is general information, not legal advice. The agency rules discussed are proposals and may change. Consult your counsel and your primary regulator.