For on-ramp partners

Short answers to the questions your compliance team will ask first

Your customer is an individual buying an asset from you, in your window, into a general-purpose wallet only they control. What they do with it afterwards, including paying a licensed merchant that accepts USDC, is a separate transaction they authorise from that wallet. Mint-Rail provides the wallet and carries the merchant's request, is named on every purchase as the referring integration, keeps the record, and leaves the regulated steps with the regulated parties.

Licensed merchants only

Every merchant holds a licence from a recognised regulator. We check it before onboarding, the merchant warrants it in the agreement, and we re-check it on renewal. A business without one is not onboarded, wherever it is based.

The customer stays yours

You verify the customer under your own policy, as the seller of the asset, and deliver to a wallet only they control. Identity and the card are handled in your own window, never in a frame of ours. Nothing from the merchant shapes the purchase: no customer identifier, no pre-filled details, unless agreed with you in writing, and the amount is the customer's to change. Mint-Rail never receives identity documents or card numbers, and never asks the customer for either.

No custody, ever

No address Mint-Rail controls ever holds value, and Mint-Rail holds no signing authority over any wallet. The wallet is general-purpose: the customer sees the balance and can keep it, send it to any address or export the key. The only signature in the flow is the customer's: the asset moves from the customer's own wallet to the settlement address the merchant nominates. Mint-Rail does not convert fiat to digital assets or back.

A purchase, then a payment

The purchase from you and the payment to the merchant are two transactions, each authorised by the customer. Funds that land in the wallet stay there until the customer taps to pay; nothing moves on arrival. The merchant's request is a request, and it can be left unpaid.

Fail closed

Inbound events are signature-verified or quarantined — an unverified payload is never interpreted. A payment is confirmed against the chain, not against a provider's message: the transfer is decoded from the mined receipt and must pay the merchant's settlement address in full before anything is reported as complete.

A complete audit trail

Every record change, every outbound request and every inbound event is captured with its request id and the actor behind it. A payment can be traced from the card purchase on your side, through the on-chain transfer, to the merchant's address and the event that reported it.

Our reference, on every transaction

Each purchase you process carries Mint-Rail's payment reference as its external transaction id, so your records and ours reconcile line by line without either side guessing.

Built for

  • Merchants licensed by a recognised regulator
  • Authorised financial-services firms
  • Businesses that already verify every customer

Not for

  • Unlicensed businesses, wherever they are based
  • Any business or person subject to sanctions
  • Anyone hoping to get around a provider's checks

Questions beyond these? [email protected] — or the terms and privacy policy for the formal statements.