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

How a corporate fiat on-ramp works

A corporate fiat on-ramp converts money received from a business bank account into stablecoins such as USDC or USDT. In Stablerail, the company uses bank instructions for the relevant fiat route, sends funds from its corporate account, converts the credited balance and delivers the stablecoins to its selected company vault.

The process has two distinct legs:

1. Bank transfer: Fiat moves from the company’s bank account to the designated receiving account through a rail such as SEPA, Fedwire, ACH or SWIFT.
2. Stablecoin conversion: After the payment is received and credited, an authorised user converts the available fiat balance into USDC or USDT for delivery on a supported blockchain.

These legs should be reconciled separately. A bank showing a transfer as completed does not necessarily mean the receiving institution has credited it, and a credited fiat balance does not necessarily mean stablecoins have been purchased. Some routes may require an authorised user to review and approve a conversion quote.

Before sending funds: confirm company eligibility

The company must complete the required know-your-business review before it can use an on-ramp. The exact information depends on its jurisdiction, ownership, industry and expected activity, but commonly includes:

• Certificate of incorporation or an equivalent registry record
• Registered and operating addresses
• Directors, beneficial owners and authorised users
• Identity documents for relevant individuals
• A description of the business and expected transaction activity
• Source-of-funds or source-of-wealth evidence when requested

Complete onboarding and confirm that the intended currency corridor is available before instructing a significant transfer. An approved company account does not automatically mean every currency, jurisdiction or transaction type is supported.

The remitting bank account should normally be held in the onboarded company’s legal name. Payments from a founder, employee, customer, affiliate or other third party may be returned or paused for evidence. If the bank account belongs to a group entity with a different name, obtain confirmation that the arrangement is acceptable before sending.

Choose the currency and bank transfer rail

Use the funding instructions generated for the exact currency and route. Do not assume that EUR and USD share the same beneficiary account, or that local bank details can receive an international SWIFT transfer.

These are general banking timeframes, not guaranteed delivery times. Cut-offs, weekends, local holidays, intermediary banks and compliance reviews can extend them. Treasury teams should work backwards from the time the stablecoins are needed rather than treating the bank’s release time as the delivery deadline.

Copy the current bank instructions exactly

Open the relevant fiat balance and retrieve its current instructions. Depending on the route, these can include the beneficiary name, IBAN or virtual IBAN, account and routing numbers, receiving bank details, SWIFT or BIC code and a unique payment reference.

Verify the instructions each time instead of relying on an old payment template. Banking details can differ by currency, corridor or legal entity and may change. An independent reviewer should compare the details entered in the bank portal with the instructions displayed in the approved account.

Copy the payment reference exactly. Do not replace it with an invoice number or add internal notes unless the instructions explicitly allow that. A missing or altered reference can prevent automated reconciliation and lead to manual investigation.

Release the bank transfer under treasury controls

Create the payment in the company’s banking portal and apply the same maker-checker process used for other treasury transfers. The approver should check the sending entity, beneficiary, amount, currency, rail and reference before release.

For a new beneficiary or route, consider a small validation transfer before moving the full treasury amount. A test payment does not eliminate compliance review, but it can expose incorrect bank details or reconciliation references before a larger transfer is made.

Retain the originating bank’s confirmation and transaction identifier. For a SWIFT payment, keep the message or tracking data available from the bank. These records allow the receiving institution to investigate a payment that has left the sender but has not been credited.

Distinguish sent, received and credited funds

Bank transfer status can be misleading if finance teams use one label for several events:

• Sent: The originating bank has accepted or released the payment.
• Received: The funds have reached the receiving banking chain or account.
• Credited: The payment has been matched to the company and is available in its fiat balance.
• Converted: The credited fiat has been exchanged for USDC or USDT.
• Delivered: The stablecoins are visible in the intended vault on the selected network.

A payment may require additional information before it is credited. The provider or a bank may ask for an invoice, contract, bank statement, source-of-funds explanation or payment-purpose evidence. The documents should match the amount, remitting entity, counterparty and stated business activity.

Review the stablecoin conversion quote

Once fiat is available, select the amount and supported stablecoin corridor. Before approval, review the exchange rate, stated fees, net stablecoin amount and quote expiry. If the quote expires before approval, request or review a new one rather than assuming the prior economics still apply.

Compare total economic output, not only the advertised transaction fee. The useful calculation is the total fiat debited from the company against the net USDC or USDT delivered. For SWIFT funding, intermediary charges may reduce the amount received before conversion.

The conversion should follow the company’s approval matrix. Separate the person requesting the conversion from the final approver where practical, and apply stronger approval requirements to larger or unusual transactions. Stablerail supports approvals and signing quorum, along with exportable evidence that can be retained for audit and reconciliation.

Confirm the asset, network and destination vault

Stablecoin names alone are not enough to define delivery. Before confirming the conversion, record three destination fields:

1. Asset: USDC or USDT.
2. Network: The supported blockchain selected for delivery.
3. Vault: The intended company-controlled wallet or vault.

A wallet address may look valid on more than one blockchain, but that does not make the networks interchangeable. The receiving system, exchange, vendor or payout workflow must support the exact token and network used. A network mismatch can make funds difficult or impossible for the intended recipient to access without a recovery process.

An MPC vault distributes signing authority across protected key shares rather than relying on one conventional private key. Quorum signing can require more than one authorised approval before assets leave the vault. Those controls protect subsequent transfers, but they do not replace the need to verify the network selected during the initial conversion.

Why fiat funding transfers are delayed

The sender name does not match. A payment from a personal account, customer or unapproved affiliate may trigger review or return. Use a bank account owned by the onboarded company unless another arrangement has been accepted.

The reference is missing. The payment can reach the right bank but remain unmatched. Provide the bank confirmation and transaction identifier rather than immediately sending a duplicate transfer.

The wrong currency or rail was used. Sending USD to EUR-only instructions or using SWIFT details for a local transfer can result in rejection, delay or bank conversion. Confirm the route before release.

Charges reduced the payment. Intermediary banks can deduct charges from some cross-border transfers. Wait for the credited amount before calculating the stablecoins expected.

A cut-off or holiday was missed. A wire released after cut-off may wait until the next relevant banking day. The sender’s local calendar and the receiving route’s calendar can both matter.

The conversion is still awaiting action. Fiat can be credited while the quote, stablecoin, network or vault remains unconfirmed. Treat conversion and delivery as separate workflow steps.

Finance team reconciliation checklist

Retain one evidence package for each on-ramp transaction:

• Approved funding request and named approvers
• Bank instructions used, including currency and route
• Sending bank confirmation and transaction identifier
• Evidence supporting the source and purpose of funds
• Fiat credit record and any deducted bank charges
• Conversion quote, rate, fees, expiry and approval record
• Stablecoin asset, network, destination vault and net amount
• Blockchain transaction hash or final delivery record
• Accounting entry linking the fiat outflow to the stablecoin receipt

Reconcile the bank leg and the blockchain leg using a shared transaction reference in the treasury ledger. Record fees separately from the stablecoin asset value, and document the exchange rate methodology used for the company’s functional-currency books. This creates a traceable path from the original bank approval to the final USDC or USDT balance.