Explainers

What is a stablecoin pay-in API? How it works, and how to choose one

A stablecoin pay-in API collects local currency or stablecoins from a payer and credits a stablecoin balance. How it works, how to choose one, and pricing.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: What is a stablecoin pay-in API? How it works, and how to choose one
Cover image for Lumx blog article: What is a stablecoin pay-in API? How it works, and how to choose one

A stablecoin pay-in API is an interface that lets a business collect money from a payer, either in local currency over a bank rail or in stablecoins on a blockchain, and receive it as a stablecoin balance, with every step reported back to the business's software. The payer pays the way they already pay, and the business holds dollars.

In practice, the API issues a payment instruction, watches for the money, converts it at a stated rate and credits a wallet, then sends an event for each change of state. This guide explains each step, how the main design choices differ, what to check when choosing a provider and how the price of a pay-in is built. For a ranked list of providers in Latin America, see best pay-in APIs for Latin America.

What does a stablecoin pay-in API do?

A pay-in API sits between a payer who wants to pay in their own money and a business that wants to receive something else. A Brazilian buyer pays in reais over Pix (Brazil's instant payment system, run by the Central Bank). A Mexican client pays in pesos over SPEI (Mexico's interbank transfer system, run by Banxico). A US customer sends a wire. The business ends up with USDC or USDT in a wallet, ready to hold, pay a supplier or convert again.

That sentence holds four jobs. The API gives the payer an instruction they can act on in their own bank app. It matches the money that arrives to the instruction it belongs to. It converts the local currency to a stablecoin at a rate it reports. And it tells the business's software what happened, through webhooks and a transaction record, so nobody has to check a bank statement by hand.

A pay-in is one of the three movements a stablecoin API handles, next to payouts and transfers between wallets. Some providers sell only pay-ins, some only payouts, and some sell both under one balance.

How a stablecoin pay-in works, step by step

The sequence is the same across providers, even when the names of the objects differ. Before the first payment, the receiver passes KYB (know your business, the verification of a company and its owners) or KYC (know your customer, the verification of an individual). After that, every payment starts with an instruction, such as a Pix code or a CLABE (the 18-digit Mexican bank account number) with a memo.

The six steps of a stablecoin pay-in, and what the business sees at each one.

Step

What happens

What the business sees

1. Onboard the receiver

The business, or its customer, passes KYB or KYC

A customer record with an approval status

2. Open the receiving account

The provider issues a local account in the customer's name or a deposit address

Bank details or a wallet address per currency

3. Issue the instruction

The API returns what the payer needs: a Pix code, a CLABE and memo, wire details or a wallet address

A payment instruction, with an amount and an expiry if it is per payment

4. Money arrives and is matched

The provider's banking partner receives the funds, and the provider ties them to the instruction

An event saying funds arrived

5. Conversion

The local currency is exchanged for a stablecoin at a floating or locked rate

Events for the trade and the transfer of the stablecoin

6. Credit and receipt

The stablecoin lands in the customer's wallet

A final event with the rate, the fees, the amount received and the blockchain transaction hash

Steps 1 and 2 happen once per customer. Steps 3 to 6 happen for every payment. The receipt at step 6 is what accounting reconciles against, so check that it carries the base rate, each fee and the final amount as separate fields, not only a total.

When the payer sends stablecoins directly to a wallet address, steps 3 to 5 collapse: there is no rail to watch and nothing to convert, and the deposit shows up as a wallet balance.

Pay-in, on-ramp and payout: which is which?

The words overlap, and vendors use them loosely.

A pay-in describes the business outcome: money comes in from a payer. An on-ramp describes the conversion: fiat becomes a stablecoin. Most stablecoin pay-ins are on-ramps under the hood, which is why many APIs name the object an on-ramp even when the product page says "collections". A payout is the opposite direction, money going out to a beneficiary, and the conversion inside it is an off-ramp.

The distinction matters when you compare pricing and features. An on-ramp quoted for a user buying stablecoins with a card is a different product from a pay-in that collects invoices from business payers over local rails. The longer comparison is in on-ramp versus off-ramp, and the conversion itself is explained in what a stablecoin on-ramp is.

Per-payment instructions or a standing account

The biggest design choice in a pay-in API is whether each payment gets its own instruction or the payer reuses one.

Two ways to collect, and where each fits.


Per-payment instruction

Standing instruction

What the payer gets

A new code or reference for each payment

One code or account they reuse every time

Who sets the amount

The business, in the instruction

The payer, when they pay

Rate

Floating, or locked for a short window

Floating, at the moment the money lands

Expiry

Yes, a payment window

No

Best for

Invoices, checkouts, any amount that must be exact

Top-ups, recurring payers, wallets that refill

Typical failure

The payer pays after the window closed

The payer sends a different amount than expected

Most platforms use both. Invoices go out as per-payment instructions, and customers who top up a balance every week get a standing one.

A second choice sits underneath: whether the account the payer sends to is in the receiving customer's own name or in the provider's name with a reference. A named virtual account (a local account number issued in the customer's own name) means the payer sees the right name in their bank app, which cuts the calls to support and the payments stopped by the payer's bank. A shared account with a reference is cheaper to run but leans on the payer typing the reference correctly.

How do you choose a stablecoin pay-in API?

Start from the payers you have, not from the provider's coverage map.

What to check, and how to test it before signing.

Criterion

What to ask

How to test it

Rails and currencies

Does it collect on the rails your payers use, in their currency?

Ask for the list per currency, then pay in sandbox on each one

Account model

Named accounts, shared accounts with a reference, or both?

Create a test account and look at the holder name a payer would see

Collection models

Per-payment, standing, or both? Locked or floating rates?

Create one of each and read the expiry and rate fields

Matching

What happens to a payment without its reference, or after expiry?

Ask for the written policy for each exception

Who operates each leg

Who holds the bank account, who converts, who holds custody?

Read the terms and the docs, and ask who the counterparty is on each step

Events and receipts

Does every state change send an event? Does the receipt split rate and fees?

Subscribe to webhooks in sandbox and inspect a receipt

Retries

Are create requests idempotent? Are events deduplicated by id?

Repeat a request with the same key and check that one payment results

Compliance holds

How does it ask for information on a flagged payment, and how long do you have?

Ask for the request for information flow and its deadline

Pricing

What are the components, and which ones are on top of the rate?

Ask for a sample receipt with every fee filled in

Two rows decide more deals than the others. The account model decides what the payer sees, and the matching policy decides how much of your support time pay-ins will eat. A provider that answers both in writing, edge cases included, has probably handled them before.

How pay-in pricing is built

A pay-in price has more parts than the headline rate, and providers bundle them differently, so compare the parts, not the total on the pricing page.

The usual components are a conversion fee, charged as basis points on the amount, sometimes with a flat amount per transaction; the FX spread, which is the gap between the rate you get and the market rate; a surcharge for locking a rate for longer; fees per verification for KYB and KYC; fees per account opened and per active account each month; and a platform fee or a monthly minimum. Some providers also pass on the bank's fee for receiving a wire.

The question that cuts through all of it is where the margin sits. A provider that shows a base rate and lists each fee separately lets you see what the conversion costs. A provider that shows only a final rate may be embedding a spread, and the only way to find it is to compare that rate with a market reference at the same minute. A platform that charges its own customers on top should check that the API can add its fee to the transaction and pay it out separately, rather than forcing a markup into the price.

For how these components compare across providers, see stablecoin API pricing compared. The same logic applied to the other direction is in how stablecoin payout pricing works, and the difference between a quote you can trust and one that moves is in indicative versus binding quotes.

I recommend asking every provider on a shortlist for the same thing: one real receipt from a sandbox pay-in, with the base rate, every fee and the final amount filled in. The receipt answers the pricing question better than any pricing page, and how quickly a provider sends it tells you how they will answer when a payment goes wrong.

When a stablecoin pay-in API is the wrong tool

A pay-in API is built for businesses that want to end up holding a stablecoin. If the money will be spent in the same currency it arrived in, a local bank account does the job without a conversion.

It is also the wrong tool for card acceptance. A consumer checkout that needs cards needs a card acquirer; pay-in APIs that collect over bank rails are push payments, and the payer has to start them. And it is the wrong tool for collecting from consumers who want to buy stablecoins for themselves: that is a retail on-ramp, with different verification, limits and pricing, and many business pay-in APIs do not serve individuals buying for their own account.

How Lumx runs a pay-in

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.

On Lumx, a pay-in starts with an approved customer and an account in that customer's name; the named virtual accounts page lists the currencies. From there you choose one of two collection methods. An on-ramp transaction is per payment: you set the amount, choose a floating rate or lock one with an exchange-rate quote for 30 seconds, 1 minute or 5 minutes, and get back the payment instruction, such as a Pix code. An autoconversion rule is standing: it returns a static Pix code, or a CLABE plus memo on SPEI, and converts every deposit at the market rate. Both carry your metadata on every webhook.

The on-ramp moves through awaiting funds, transferring fiat, trading, transferring stablecoin and success, with failed and expired as the other end states, and the success event carries the receipt: base rate, base amount, the Lumx fee as a rate plus a flat amount, any partner fee, the final amount and the blockchain transaction hash. A partner fee applies only when you send its id, and it is charged on top of what the payer funds. Pricing is a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding; there are no published plans. The rails per currency are on Lumx coverage, and a peso collection end to end is on MXN to USDC.

Methodology and sources

Lumx behavior comes from docs.lumx.io read on November 17, 2026: pay-in quickstart, transactions, autoconversion rules, partner fees, the exchange-rate API reference, concepts/accounts, concepts/wallets and developer/webhooks. The selection criteria and the pricing breakdown are our own framework for comparing providers, not a ranking.

Verified on November 17, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Michael Myers on Unsplash.

  • What is a stablecoin pay-in API?

    It is an interface that lets a business collect money from a payer, in local currency over a bank rail or in stablecoins on a blockchain, and receive it as a stablecoin balance. The API issues the payment instruction, matches the money that arrives, converts it and reports each step through events and a receipt.

  • How does a stablecoin pay-in work?

    The receiver is verified and gets an account or deposit address. For each payment, the API returns an instruction such as a Pix code or a CLABE with a memo. When the money arrives, the provider matches it, converts it to USDC or USDT and credits the wallet, then sends a receipt with the rate and the fees. On Lumx, each step is a webhook event on the on-ramp, from awaiting funds to success.

  • How much does a stablecoin pay-in API cost?

    Pricing is usually a conversion fee in basis points, sometimes with a flat amount, plus any FX spread, a surcharge for longer rate locks, per-verification and per-account fees, and a platform fee or monthly minimum. Compare the components, not the total. On Lumx, pricing is a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding.

  • How do you choose a stablecoin pay-in API?

    Start from the rails and currencies your payers use, then check the account model, whether it offers per-payment and standing instructions, how it handles payments without a reference or after expiry, who operates each leg, and whether every state change sends an event. Ask each provider for a sandbox receipt with every fee filled in.

  • Can someone other than the customer pay into a stablecoin pay-in?

    Usually yes, since collections on behalf of your customers (POBO and COBO) are a common model, but an unexpected payer can trigger a compliance review. Tell the provider which payers you expect. On Lumx, a flagged on-ramp is held while compliance asks about the relationship and purpose, and with no response in 24 hours it may be refunded to the sender.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

what-is-a-stablecoin-payin-api

A

what-is-a-stablecoin-payin-api

What is a stablecoin pay-in API? How it works, and how to choose one

Copy link

Copied!

what-is-a-stablecoin-payin-api

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Explainers

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.