Fiat on-ramp for companies: funding a stablecoin balance by bank transfer

A corporate fiat on-ramp converts money received from a bank account into stablecoins such as USDC or USDT. The basic flow is straightforward: obtain the correct bank instructions, send EUR or USD from the company’s bank account, wait for the funds to be credited, review the conversion quote and deliver the stablecoins to the company vault.

The operational details matter. Currency, payment rail, beneficiary name, transfer reference and destination blockchain must all be correct. A mismatch can delay the transfer or cause it to be returned.

This guide explains how to fund a USDC balance through Stablerail using a bank transfer, what happens at each stage and how finance teams can avoid common business crypto funding problems.

How the fiat on-ramp works

The process has two distinct legs:

• Bank transfer: The company sends fiat currency to the account details displayed in Stablerail. Depending on the currency and route, this may use SEPA, SEPA Instant, Fedwire, ACH or SWIFT.
• Stablecoin conversion: Once the fiat is available, the company converts it into USDC or USDT using the available corridor. The stablecoins are delivered to the selected self-custodial MPC vault on a supported network.

An MPC vault is a blockchain wallet whose signing authority is divided between multiple protected key shares. Quorum signing means the company can require more than one approval before funds leave the vault.

The bank transfer and conversion are separate events. A completed bank transfer does not necessarily mean that stablecoins have already been purchased. Finance teams should check whether the selected route converts automatically or requires an authorised user to approve a quote.

Step 1: Complete company onboarding

Before receiving bank details or converting funds, the company must complete know-your-business checks. Typical documents include:

• Certificate of incorporation or equivalent registry document
• Registered and operating addresses
• Ownership and director information
• Identity documents for relevant individuals
• Description of the company’s business and expected payment activity
• Source-of-funds or source-of-wealth evidence where requested

Eligibility depends on the company’s jurisdiction, industry and intended use. Complete this stage before instructing a large transfer. Sending funds while an account or corridor is still under review can create avoidable delays.

Step 2: Select the currency and transfer rail

Choose the funding currency and use the bank instructions generated for that route. Do not reuse instructions from another currency or entity.

These are general banking timeframes, not guaranteed delivery times. Reviews by the sending bank, receiving institution or intermediary can extend them.

Step 3: Copy the bank instructions exactly

Open the relevant fiat balance and obtain its current funding instructions. Depending on the route, these can include:

• Beneficiary name
• IBAN or virtual IBAN
• Account and routing numbers
• Receiving bank name and address
• SWIFT or BIC code
• A unique payment reference

The sender should normally be the onboarded company, and the remitting bank account should be held in that company’s legal name. Transfers from founders, customers, affiliates or unrelated third parties may be rejected or require additional evidence.

Save the instructions used with the payment record. Bank details can vary by currency or corridor, so verify them in the account each time rather than relying on an old treasury template.

Step 4: Send the bank transfer

Create the payment in the company’s banking portal and complete any internal approval workflow. Check the beneficiary, amount, currency and reference before release.

For a time-sensitive transfer, confirm the bank’s cut-off and holiday calendar. A Fedwire sent after the applicable cut-off may not move until the next US banking day. A standard SEPA transfer submitted late on Friday may not arrive until the next business day, while an eligible SEPA Instant transfer can operate outside normal banking hours.

Keep the bank confirmation. For SWIFT transfers, retain the payment message or tracking reference. For domestic wires, save the bank’s transaction identifier. These records help trace a payment if it does not arrive as expected.

Step 5: Wait for the fiat balance to be credited

Once received and reconciled, the money appears in the relevant fiat balance, such as EUR or USD. It has not yet become USDC or USDT unless the selected route explicitly supports automatic conversion.

A transfer may show as sent at the originating bank before it is available to convert. “Sent,” “received” and “credited” represent different stages. Crediting can depend on successful reconciliation, required payment information and any necessary review.

Step 6: Review and approve the conversion

Select the fiat balance, stablecoin and amount to convert. Before confirming, review the displayed corridor pricing and quote details. These may include the exchange rate, fees, expected stablecoin amount and quote expiry.

Do not compare only the headline fee. Compare the total fiat sent with the net USDC or USDT delivered. For SWIFT payments, also account for any charges deducted by intermediary banks before the funds arrive.

The conversion should be approved under the company’s treasury policy. Larger amounts may require multiple approvers or a lower user limit than routine payments.

Step 7: Confirm where the stablecoins will land

The converted funds land in the selected company stablecoin vault, not in the original bank account. Confirm all three destination fields:

• Asset: USDC or USDT
• Network: The supported blockchain selected for delivery, such as Ethereum, Base, Arbitrum, Polygon, Tron, BNB Chain, Optimism or Solana
• Vault: The company’s intended self-custodial MPC wallet

The same wallet address format can sometimes exist on multiple networks, but that does not make the networks interchangeable. The finance team should record the token and network alongside the amount. This is particularly important when funding a balance for payroll, vendor payouts or transfer to an exchange.

Companies planning to make multiple payments can use the funded balance through stablecoin payouts. More information about holding and operating USDC is available on the USDC business account page.

Common reasons a funding transfer fails or is delayed

The sender name does not match

A transfer from a personal, customer or affiliate account may not satisfy the account’s funding rules. Send from a bank account owned by the onboarded legal entity unless another arrangement has been approved.

The payment reference is missing or incorrect

A virtual account can simplify reconciliation, but some routes still require a unique reference. Missing references can lead to manual review. Copy the reference without adding invoice numbers or internal notes unless the instructions permit them.

The wrong currency or rail was used

Sending USD to EUR-only instructions, using a domestic route for an international transfer or directing a SWIFT payment to local-only details can cause rejection or conversion by a bank at an unfavourable rate.

Bank charges reduced the amount

Correspondent banks may deduct fees from SWIFT payments. The credited balance can therefore be lower than the amount instructed. Do not assume an exact conversion amount until the fiat has arrived and the quote is displayed.

The transfer missed a cut-off

Banking days, local holidays and cut-off times affect standard SEPA and wire payments. Check both the sending bank’s submission deadline and the operating calendar for the rail.

Additional information is required

A bank or payment provider may request an invoice, contract, bank statement or explanation of the source and purpose of funds. Respond with documents that match the transfer amount, counterparties and stated activity.

The destination network was not confirmed

The bank transfer can complete correctly while the conversion remains pending because the stablecoin asset, network or vault has not been selected. Treat fiat arrival and stablecoin delivery as separate reconciliation checkpoints.

A practical reconciliation checklist

For every fiat on-ramp transaction, retain a simple evidence set:

• Approved funding request
• Bank instructions used
• Sending bank confirmation and transaction reference
• Fiat credit record
• Conversion quote and fee breakdown
• Stablecoin, network, vault and final amount received
• Blockchain transaction identifier, where applicable

Reconcile the bank debit, fiat credit, conversion cost and stablecoin receipt as separate entries. This gives the finance team a clear record from the original bank transfer through to the funded treasury balance—and makes exceptions much easier to investigate.