# cryptoinfra — full site text ## Cryptoinfra — White Label Crypto Payment Gateway URL: https://cryptoinfra.net/ White-label crypto infrastructureLaunch your crypto brand. On white‑label infrastructure. Everything you need to build a crypto product, a SaaS or a payment gateway: checkout, wallets, payouts, cards, swaps and an exchange. One API, one dashboard, your brand. Start free →Talk to us 01Your brandYour appYour storeYour checkout one API · one dashboard 02Six productsGatewaycheckout Walletsdeposits Payoutssingle · batch CardsVisa Swapin your app Exchangeinstant Every coin · five networks Payment gatewayAccept crypto at checkout. Under your own name. A hosted checkout priced in USD, payment links, store plugins and a point-of-sale screen. Your customer picks the coin and the network. Explore the gateway →Start free 01Your customer paysOrder #1001 yourstore.com checkout$49.99 USDT on Solanatheir choice confirms on-chain · credits you 02You get paid+ 49.99 USDT in your balancePaid payment.paid → your server · 200 OK Every coin · five networks WalletsA wallet for every user. Deposits that credit themselves. One permanent address per customer on TRON, BNB Smart Chain, Solana, Bitcoin and TON. Each deposit is confirmed, credited and sent to you as a signed webhook. Explore wallets →Start free 01One API callPOST /v1/wallets · user 10482 a permanent address on every network 02Deposits credit themselvesBitcoinbc1q…7k2m TONUQBv…x4Te + 250.00 USDT on SolanaCredited Every coin · five networks PayoutsPayouts on five networks. Sent once, never twice. Pay one customer or a whole batch by API. Idempotency keys make sure a retried request can never pay twice. Explore payouts →Start free 01One requestPOST /v1/payouts · 3 recipients sends once · never twice 02Everyone is paid120 USDT on TRONSent 0.4 BNB on BNB ChainSent 0.01 BTC on BitcoinSent Every coin · five networks CardsVisa cards, under your brand. Funded with USDT. Issue virtual Visa debit cards inside your own app. Your users load them from their USDT balance and pay with Apple Pay or Google Pay. Explore cards →Start free 01Your user loads USDT100 USDTfrom their balance issues the card under your brand 02They spend anywhereYOUR BRAND•••• 4821VISA Apple PayGoogle PayOnline and in-store Every coin · five networks Swap & exchangeSwap and exchange. Every coin we support. Let your users swap between coins inside your app with one API call, or send them to a ready instant exchange. Explore swap →Open the exchange 01Your user sends0.05 BTCany coin quotes · swaps · pays out 02They receive≈ 21.4 SOLDone any coin ⇄ any coin · {{exchangeCoins}} coins Every coin · five networks 01 / 06 One balance behind every product USDTUSDCTRXcardsSigned webhooksFive networksCrypto checkoutFree sandbox USDTUSDCTRXcardsSigned webhooksFive networksCrypto checkoutFree sandbox By the numbersOne platform. Every crypto product. 5NetworksTRON, BNB Smart Chain, Solana, Bitcoin, TON 6Products on one APIGateway, wallets, payouts, cards, swap, exchange 13Store pluginsWooCommerce, WHMCS, Magento and more {{exchangeCoins}}Coins on the exchangeEvery one swaps with every other The whole platformSix products. One API. Your brand. Use one, or all six. They share one balance, one dashboard and one API. Payment gatewayHosted checkout, payment links and store plugins. WalletsA permanent deposit address for every customer. PayoutsSend crypto by API, one payout or a whole batch. CardsVirtual Visa debit cards your users fund with USDT. SwapSwaps between coins inside your own app. ExchangeAn instant exchange between every coin we support. Freeto start. No setup fee, no monthly fee. You get of our platform fee on every payout, swap and card No platform fee on deposits Free sandbox Go live the day you sign up A wallet for every user. Deposits that credit themselves. Wallets Give each customer their own address on every network with one API call. The addresses are permanent. app.yourbrand.com USDT balance1,284.00 TJYBSfZfwwa28mYZPkE9… Your deposit address Automatic deposits Deposits are found on chain and credited on their own. No platform fee on deposits. Deposits Sample data user 10482+ 250.00 USDT user 20917+ 1,400 TRX user 31150+ 75.50 USDC One balance per user Every coin, one dashboard, one balance behind wallets, payouts, cards and swaps. Balances Sample data USDT48,210.55 USDC12,904.10 TRX305,118 Signed webhooks Your server hears about every deposit the moment it is credited. Failed deliveries are retried. Webhook delivered to your server deposit.credited · user 10482200 OK card.status · active200 OK Explore wallets → Accept crypto at checkout. Hosted checkout Price an order in US dollars. Your customer picks the coin and the network, pays the exact amount, and your server gets a signed webhook. Payments Sample data Order #1001 · USDT on SolanaPaid Order #1002 · USDT on BNB Smart ChainPaid Order #1003 · USDT on TRONPaid Store plugins WooCommerce, WHMCS, PrestaShop, Magento 2, OpenCart and more. Download, paste your key, done. Links and buttons A payment link with a fixed price, or an open amount for donations, and a button for any web page. Point of sale A keypad for the counter. Type the amount, the customer scans and pays, and the screen turns green. Explore the payment gateway → Visa cards, under your brand. YourBrand•••• 7731 YourBrand4000 •••• •••• 1826 Issue virtual cards Your users get a virtual Visa card funded with USDT from your card programme's wallet, with your name on it. Explore cards → Add to wallet Card statusActive Funded fromUSDT Spend anywhere Visa works The card goes into Apple Pay or Google Pay and is accepted wherever Visa is. See the card API → Payouts on five networks, sent once. Payouts Pay out USDT or TRX on TRON, USDT, USDC or BNB on BNB Smart Chain, USDT, USDC or SOL on Solana, USDT or TON on TON, or BTC, from your user's balance. Batch payouts Send many payouts in one call. Each one stands alone, so one bad address never sinks the rest. Live network fee The network fee is priced live for each send, so no one overpays. Ask for a quote before you send. Never paid twice Retry a request as often as you like. The same key never pays twice. Explore payouts → Batch payout In progress TJYBSfZf…wEqBK1sent TQ8mK2dn…7hVx3Psent TLp41sRe…c9Yt2Asigning Sample data Swap and exchange, in one call. Two things your users can do without leaving your app. SwapUSDT and TRX, both ways Explore swap → USDTYou send — ⇅TRXYou receive — Swap Swap USDT and TRX in one call, with the result credited to the user's own balance. And pay out in thousands of other coins to any address, with your own fee on top of ours. White-label Your name on everything. Your customers use your app, your cards and your brand. We stay behind the scenes. Lumen Northpay Kora Amberly Your brand onlyNo partner names reach your customers. Not in the API, not in webhooks. A share of our fee of our fee on every payout, swap and card your customers make, paid to your balance automatically. Your own feeAdd your fee on top of ours on payouts and swaps. It is yours. Live in three stepsCreate your account, connect the API, launch. Your account is live as soon as you verify your email. LumenWalletUSDT balance1,284.00•••• 1826 · DepositSendCard Example brands and a sample balance. Different companies, the same infrastructure underneath. Earn from day one We share of our fees with you. Every time your customers send, swap or use a card, of our fee goes straight to your balance. Nothing to set up. You earn even if you never charge a fee of your own. Example · one USDT payout Our platform fee USDT → You get, automatically USDT 1 of our fee, automatic On every payout, swap, card issue, card load and card close. Paid into your balance the moment we earn it. 2Your own fee, all yours Want more? Add your own fee on top of ours on payouts and swaps. You choose the amount, and all of it is yours. 3See every cent Your Profit page shows each commission and each fee, and you can withdraw your earnings any time. Live prices Every price is public. Read live from the same price sheet the API serves. No setup fee, no monthly fee. Deposits on TRON USDT payout, all in USDT Card load fee + Setup and monthly fee None See the full price sheet → Security Built to protect every coin. ⚿Keys stay off our API servers The servers you talk to can create addresses but can never spend. ✓A code for every change Every dashboard change is confirmed with your authenticator. ≡Books checked against the chain Balances are matched with the blockchain every few minutes. 1×Every payout sent once Retry a request as often as you like. It never pays twice. How we keep money safe → One API for all of it. Create users, get their addresses and receive signed webhooks. Test everything free in the sandbox, then switch to real money. Quickstart →Documentation →API overview → # one call gives your customer a permanent wallet curl -X POST https://api.cryptoinfra.build/v1/users \ -H "Authorization: Bearer $KEY" \ -d '{"external_user_id":"10482"}' { "user_id": "10482", "addresses": [ { "chain": "tron", "address": "TJYBSfZf…" } ] } Frequently asked questions What is Cryptoinfra? Cryptoinfra is white-label crypto infrastructure. It lets any business launch crypto wallets, payouts, debit cards and swaps under its own brand, using one API and a ready dashboard. Which coins and networks do you support? Five networks. TRON: USDT and TRX. BNB Smart Chain: USDT, USDC and BNB. Solana: USDT, USDC and SOL. Bitcoin: BTC. TON: USDT and TON. Every network's own coin is a balance too, and every network cost is inside the fee. Can I accept crypto at checkout? Yes. Create a payment in US dollars and send your customer to a hosted checkout, where they pick the coin and network. Plugins for WooCommerce, WHMCS, PrestaShop, Magento 2 and more, payment links, donation buttons and a point-of-sale screen need no code. How much does it cost? There is no setup fee and no monthly fee. You pay only when money moves, and there is no platform fee on deposits. Every price is on our public price sheet and on the Pricing page. How do I earn from my customers? Two ways. You get a share of our platform fee on every payout, swap and card operation automatically, paid into your balance as the fee settles. And you can add your own fee on top on payouts and swaps, which is all yours. Will my customers see your name? No. Your app shows your brand, and partner names are removed from our API and webhooks. A few secure steps, like showing the full card number, open on a hosted page. How fast can I go live? Your account is live as soon as you verify your email. You can test with free sandbox money first, then switch to real money when you are ready. Can my users get a crypto debit card? Yes. Users can get a virtual Visa card funded with USDT from your card programme's wallet, add it to Apple Pay or Google Pay, and spend anywhere Visa is accepted. Build the next big crypto brand. Start free today. No setup fee, no monthly fee, no sales call. Start free → Talk to us --- ## About Cryptoinfra — Operated by SPDJMEDIA LLC URL: https://cryptoinfra.net/about About About Cryptoinfra. Cryptoinfra is a white label crypto payment gateway. Businesses use it to take crypto at checkout and to launch wallets, payouts, debit cards and swaps under their own brand. Cryptoinfra is built and operated by SPDJMEDIA LLC. Start free →Talk to us 01The company SPDJMEDIA LLC builds and operates Cryptoinfra 02Where we run Websitecryptoinfra.net Dashboardmerchant.cryptoinfra.build APIapi.cryptoinfra.build Docsdocs.cryptoinfra.net Operated bySPDJMEDIA LLC Official websitecryptoinfra.net Products6 Networks5 The companyWho runs Cryptoinfra. One company, one product and one website. Anything else carrying the name is not us. SPDJMEDIA LLC Cryptoinfra is a product of SPDJMEDIA LLC, which owns the Cryptoinfra name, the platform and this website. One official website Cryptoinfra's website is cryptoinfra.net. The dashboard and the API run on merchant.cryptoinfra.build and api.cryptoinfra.build, and the docs on docs.cryptoinfra.net. Not to be confused Other sites with a similar name are not part of Cryptoinfra. If an address is not on cryptoinfra.net or cryptoinfra.build, it is not us. What we buildCrypto infrastructure for your brand. Six products on one API, one dashboard and one balance. Payment gateway A hosted checkout, payment links, store plugins and a point-of-sale screen. Explore the gateway → Wallets and payouts One permanent address per customer on TRON, BNB Smart Chain, Solana, Bitcoin and TON, and payouts by API. Explore wallets → Cards and swaps Virtual Visa debit cards funded with USDT, and swaps between every coin we support. Explore cards → Talk to us. Questions about Cryptoinfra or SPDJMEDIA LLC? Write to us on Telegram, or start free in the sandbox. Start free →Contact on Telegram --- ## White Label Crypto Debit Cards (Visa) | Cryptoinfra URL: https://cryptoinfra.net/cards Cards Visa cards your users fund with USDT. Issue virtual Visa debit cards under your own brand, funded in USDT from your card programme’s wallet. Your users add them to Apple Pay or Google Pay and spend wherever Visa is accepted. Issued in one call, from the API or the dashboard. Apple Pay, Google Pay and Samsung Pay. Every fee shown first, before a user confirms. Start free →Read the docs 01A load in USDTCard active 100.00 USDTfrom your card wallet 02They spend anywhere YOUR BRAND•••• 4821VISA Apple PayGoogle Pay3-D Secure Online storePendingApproved Card issue fee USDT Card load fee Smallest opening balance USDT Card networkVisa How it worksFrom sign-up to first tap in four steps. A card programme without a bank relationship of your own. You fund one wallet, and every card is paid from it. Fund your card wallet Your card programme has its own wallet. Top it up in USDT on TRON or BNB Smart Chain; it pays for every card. GET /v1/cards/wallet Verify the cardholder Cardholders pass a quick identity check once. The API tells you the status, and your app shows the result under your brand. POST /v1/cards/kyc Issue the card One call creates a funded virtual Visa card. Ask for the price first and show it to your user. POST /v1/cards They pay with their phone The card goes into Apple Pay or Google Pay, and one-time 3-D Secure codes reach your app. card.status FeaturesA full card programme, ready today. Everything a cardholder does happens in your app and under your name. Issue in one call Create a funded virtual card for any user straight from the API or the dashboard. Cards Sample data •••• 4821 · user 10482Active •••• 7731 · user 20917Active •••• 1826 · user 31150IssuingActive Phone wallets Cards can be added to Apple Pay, Google Pay and Samsung Pay. Spend worldwide Online and in-store, anywhere Visa is accepted. Load from USDT Every load is paid in USDT from your card programme's wallet, on TRON or BNB Smart Chain. Secure codes One-time 3-D Secure codes reach your app, so users confirm payments inside your brand. Close any time Users can close a card whenever they like and see their exact refund before they confirm. Every line visible Each load, spend and refund is a line your user can read, and an event your server receives. Card activity Sample data Loaded from USDT+ 100.00 Online store− 24.90 Coffee shop− 4.50 Live pricingClear prices. Always live. WhatPriceCard issue feeOne time, per card USDTSmallest opening balanceLoaded onto the new card USDTCard load feePercentage of the loadCard load, flat partPer load USDTCard close feePlus the live network fee to send the balance back USDTNetwork fee on each loadThe live cost of the on-chain send USDTClose: taken from the refundThe card network’s charge to release the balancemin USDT · max USDT on refunds under USDTClose: when the refund arrivesBack in your card programme’s walletup to days A funded card, in one call. Ask for the price, show it to your user, then issue. The key makes a retry safe: one request, one card. Cards, end to end →The card API → # issue a virtual Visa card with an opening balance curl -X POST https://api.cryptoinfra.build/v1/cards \ -H "Authorization: Bearer $KEY" \ -d '{ "user_id": "10482", "initial_amount": "100.00", "idempotency_key": "card_2b9e17" }' QuestionsGood to know. What kind of card is it? A virtual Visa debit card in US dollars, funded in USDT from your card programme's wallet. Can users add it to Apple Pay or Google Pay? Yes. The card supports Apple Pay, Google Pay and Samsung Pay. How do users add money to the card? Each load is paid in USDT from your card programme's wallet, and the fee is shown first. What happens when a user closes the card? The remaining balance, less the fees shown up front, comes back to the card programme's wallet that paid for the card. Launch your own crypto card. Start free today. Build against the sandbox, then issue your first card. Start free → Talk to us --- ## Crypto Card API: Issue USDT Visa Cards | Cryptoinfra URL: https://cryptoinfra.net/crypto-card-api Crypto card API The crypto card API that issues a Visa card in one call. A crypto card API is a programming interface that lets your own app create, fund and manage debit cards paid for with crypto. Cryptoinfra's card API issues a virtual Visa card for any of your users, loads it in USDT from your card programme's wallet, delivers the 3-D Secure code to your app and reports every event with a signed webhook, all under your brand. One REST call to issue a funded virtual Visa card. White label: your users see your name, never a partner's. Free sandbox with test money, no setup fee, no monthly fee. Get an API key →Read the card API docs 01One REST callExample POST /v1/cards "initial_amount": "100.00" 201 Created · card issued 02Your user's card YOUR BRAND•••• 4821VISA Apple PayGoogle Pay3-D Secure card.statusSending200 OK Card issue fee USDT Card load fee Loads paid inUSDT Card networkVisa What the API doesEvery step of a card program, as an endpoint. You call the API from your own backend. Your users never leave your app. Issue a card One POST creates a virtual Visa card for a verified user and loads its opening balance in USDT from your card programme's wallet. The card number, expiry and security code are revealed to the cardholder inside your app. Load it from USDT A load moves USDT from your card programme's wallet onto the card. Every fee is quoted before the call so your app can show it to the user first. 3-D Secure in your app When a shop asks for a one-time code, the API delivers it to your server as a webhook, so your user confirms the payment inside your brand. Signed webhooks Issued, loaded, declined, closed: each card event reaches your endpoint signed with HMAC-SHA256 and is retried until you acknowledge it. Apple Pay and Google Pay Cards issued through the API can be added to Apple Pay, Google Pay and Samsung Pay, and spend online or in store wherever Visa is accepted. Close and refund A close call returns the remaining balance to your card programme's wallet, with the exact refund quoted before it is confirmed. IntegrationFrom API key to first card in four calls. Build users, deposits and webhooks against the free sandbox first. Cards run on the live rail, so your first card is your own, with a small load. Create the user Each of your users gets a permanent address on every network we serve. Deposits to them are credited to their balance on their own. Verify identity Cardholders pass a quick identity check once. The API tells you the status, and your app shows the result under your brand. Issue the card POST the user, the card product and the opening balance. The response carries the card and a reveal link for the cardholder. Listen for webhooks Loads, declines, 3-D Secure codes and closes arrive as signed events. Acknowledge them and update your own UI. Live pricingWhat a card costs through the API. Read live from our public price sheet. No setup fee, no monthly fee, no minimum volume. WhatPrice Card issue feeOne time, per card USDT Smallest opening balanceLoaded onto the new card USDT Card load feePercentage of the load Card close feeWhen a user closes a card USDT Your share of our feesPaid to your balance automatically Full price sheetCards overview Choosing a provider What to look for in a crypto card API. The questions that separate a card API you can build a business on from one that becomes a support problem. Cryptoinfra answers each of them. Must have Ask every provider this Is it truly white label? Partner and issuer names must never reach your users, in the app, the API or the webhooks. Is every fee quoted before the call? Issue, load and close fees should be readable from a public price sheet, so your UI can show them first. Where does the 3-D Secure code go? To your app, not to a partner's SMS, or your users leave your brand at checkout. Are writes idempotent? A retried issue or load must never create or charge twice. Is there a sandbox with the same API? You should build and test your side with test money, and be told plainly what the sandbox leaves out. Can you set your own price? Look for a public fee and room for your own price on top, not only a cost line. Warning signs Walk away when you see A setup fee, a monthly minimum or a volume commitment before you have a single cardholder Prices only available "on request", or fees that appear after the load Webhooks without signatures or retries, so a missed event means a wrong balance Documentation you cannot read before signing, or no machine-readable spec A partner's name on the card, the statement or the confirmation screen Our docs are public, the whole reference is one text file, and there is an MCP server so an AI coding tool can read the card API itself. Read our longer buyer's guide to crypto card APIs. QuestionsCrypto card API, answered. What is a crypto card API? A crypto card API is a set of HTTP endpoints that lets a business issue and manage debit cards that are funded with cryptocurrency instead of a bank balance. With Cryptoinfra, your backend calls the API to create a virtual Visa card for a user, load it in USDT from your card programme's wallet, receive 3-D Secure codes and events by webhook, and close the card. Your users only ever see your app and your brand. How do I issue a crypto card through the API? Create the user, let them pass the identity check, then send one POST to the cards endpoint with the user, the card product and the opening balance. The response returns the card and a link where the cardholder reveals the number, expiry and security code. Which crypto can fund the card? Cards are paid in USDT, from your card programme's balance, which you fund with USDT on TRON (TRC20) or BNB Smart Chain (BEP20). Each card issue or load is paid in one of the two. Is the card API white label? Yes. The card, the API responses and the webhooks carry no partner, issuer or processor name. Your users see your brand in your app, and the 3-D Secure code is delivered to your app rather than to a third party. What does the crypto card API cost? There is no setup fee, no monthly fee and no minimum volume. You pay a per-card issue fee, a percentage on each load and a fee when a card is closed, all published on our live price sheet. A share of our fee on every card your users issue, load or close comes back to your balance, and what you charge your users is up to you. Do the cards work with Apple Pay and Google Pay? Yes. Virtual Visa cards issued through the API can be added to Apple Pay, Google Pay and Samsung Pay and used online or in store wherever Visa is accepted. Is there a sandbox for the card API? Every account gets a free sandbox with test money for users, deposits, payouts and webhooks, on the same endpoints as production. Card calls need the live card rail, so in the sandbox they answer that cards are off. Build your side there, then issue your first real card to yourself with a small load. What makes Cryptoinfra a good crypto card API provider? One REST API covers the whole program: a permanent USDT address per user, card issuing, loads, 3-D Secure delivery, signed webhooks and closes. It is white label end to end, every fee is on a public sheet before you call, writes are idempotent, a free sandbox covers the rest of your integration, and you set the price your users pay. Start building Your card program. One API. Create a free account, issue your first test card in the sandbox, then go live under your own name. Get an API key → White-label card provider --- ## Crypto Payment Gateway — Accept USDT & USDC | Cryptoinfra URL: https://cryptoinfra.net/crypto-payment-gateway Crypto payment gateway The crypto payment gateway that credits itself. Price an order in US dollars and send your customer to a hosted checkout. They pick the coin and the network they already use, pay the exact amount, and your server hears the moment it is paid — from your own code, a store plugin, a payment link or the counter. No platform fee to receive No setup or monthly fee Free sandbox Create free account →Talk to us 01Your customer paysExample Order #1001 · yourstore.com $49.99 USDT on Solana · their choice 02You get paid + 49.99 USDT in your balanceConfirmingPaid payment.paid → your server · 200 OK Receiving on TRON Confirmations on BNB Smart Chain Setup and monthly feeNone Networks5 Networks Your customers pay on the network they already use. Every coin below, on the hosted checkout, on payment links and at the counter. Each coin on each network is its own balance. TRONtron · TRC20 USDTTRX BNB Smart Chainbsc · BEP20 USDTUSDCBNB Solanasol · SPL USDTUSDCSOL Bitcoinbtc · native BTC TONton · jetton USDTTON You never need a network's own coin for its fees: every network cost is inside the fee. How it worksFrom order to paid in three steps. Create a payment Send the order id and the price in US dollars — or let your store plugin do it. You get a checkout link back. The customer picks a coin The hosted checkout shows every coin and network you can be paid in, the exact amount and a QR code. The rate is locked when they choose. You fulfil the order Once the network confirms it, your server gets a signed payment.paid and the money is in your balance. Ways to take paymentsPlug it in, link it, or ring it up. Everything below is in the dashboard under Payments, and every one of them makes the same payment with the same webhooks. Store plugins Download, paste your API key and callback secret, done. Orders are marked paid on their own — and the payment page can sit inside your own checkout, or open on its own. WooCommerce Easy Digital Downloads Paid Memberships Pro Gravity Forms Restrict Content Pro WHMCS Blesta WISECP Clientexec PrestaShop OpenCart Magento 2 VirtueMart Laravel Payment links and buttons A reusable link with a fixed price, or an open amount for donations and tips. Share it anywhere, or drop a "Pay with crypto" button on any web page with one line of HTML. Point of sale A keypad screen for the counter. Type the amount, the customer scans the code and pays, and the screen turns green when it is paid. SDKs and no-code apps Write a few lines, or none at all. Node / TypeScript Python PHP n8n Zapier Make Telegram bot Two ways to get paid One order, or one customer for life. Use a payment when you sell something. Use a permanent address when your customers top up a balance. Per order A payment One order, one price in US dollars, one deadline The customer picks the coin and network on the checkout Paid, underpaid, expired or paid late — each is its own webhook Money sent late or in another coin is still credited to you Per customer A permanent address One address per customer on each network, saved once Nothing expires: they can pay today, next week or next year Each payment filed under the customer it belongs to A signed deposit.credited the moment it is credited Pricing None platform fee to receive a payment, and nothing added to your customer's price. No setup fee and no monthly fee. Create free account → Receiving on TRON or BNB Smart ChainCredited in full Receiving on the other networksOnly the network cost of moving it, priced liveNetwork cost Setup and monthly feeNone Sending USDT out on TRON, all inNetwork fee priced live, plus ours USDT Your own fee on paymentsOptional — all of it is yoursYou set it Every coin on the live price sheet → FeaturesEverything after "pay here", handled. Signed webhooks Every paid order reaches your server with what was asked, what arrived and in which coin — signed with HMAC-SHA256 and retried if your server is down. x-cryptoinfra-eventpayment.paid { "order_id": "wc-1001", "status": "paid", "amount": "", "currency": "USD", "asset_id": "usdt_spl", "paid_amount": "" } A price that never moves Stablecoins are priced one to one with the dollar; any other coin is locked at the live rate when the customer picks it. Auto-convert and auto-settle Daily rules convert one coin to another and send a coin to your own wallet. Owner only, confirmed with your authenticator, and a new address waits 24 hours. Your own fee Set a fee on incoming payments if you want one. It is taken from the payment and lands in your balance. A free sandbox Every call works with fake money, and one call pays a test payment so you can watch your webhooks arrive. SecurityBuilt to protect every coin. Keys off our API servers The servers your app talks to can create an address but never spend from one. A code for every change An authenticator code on every dashboard change. Books checked against the chain Balances are matched with the blockchain every few minutes. Every payout sent once Retry a request as often as you like — it never pays twice. QuestionsGood to know. Which coins can my customers pay with? USDT and TRX on TRON; USDT, USDC and BNB on BNB Smart Chain; USDT, USDC and SOL on Solana; BTC on Bitcoin; USDT and TON on TON. The checkout offers whatever is open right now. Is there a fee to receive a payment? There is no platform fee, and nothing is added to the price your customer sees. On TRON and BNB Smart Chain a payment is credited in full; on the other networks only the live network cost of moving it into our wallet is taken. Your own fee, if you set one, comes off too. Every figure is on the live price sheet. Which stores have a plugin? WooCommerce, Easy Digital Downloads, Paid Memberships Pro, Gravity Forms, Restrict Content Pro, WHMCS, Blesta, WISECP, Clientexec, PrestaShop, OpenCart, Magento 2 and VirtueMart, plus a Laravel package. Download them from the list above, or in the dashboard under Payments, Plugins. Can the payment page sit inside my own site? Yes. Every plugin has a setting to show the payment page embedded on your own order page instead of sending the customer away; on any other site, one script tag frames it. The frame is always exactly as tall as the page, fits any width down to a phone, and takes the customer to your thank-you page once they have paid. Can I use it on Shopify? Not as a native payment method yet — Shopify approves those itself. Add a manual "Pay with crypto" method and send the customer a payment link for the order. What if a customer pays too little, too late or in another coin? You get a webhook for each case — underpaid, expired or paid late — and decide. The money is never lost: whatever arrives is credited to your balance and shown on the payment. What if a customer pays on another network? The checkout shows the network next to the address, and the address takes only that network. Six of the networks use addresses that look alike (0x…), so coins sent over the wrong one are not credited. Always pay on the network shown. Do I need to run a node? No. We watch every network for you. Listen for the webhook, or read the payment over the API. How fast can I start? Your account is live as soon as you verify your email. A free sandbox with test money lets you try every call before you take real payments. Start today Your first crypto order, paid automatically. Create your account, test free in the sandbox, then go live with real payments. Create free account → Talk to us on Telegram No platform fee to receive No setup or monthly fee Free sandbox --- ## Crypto Payment Gateway API for Developers | Cryptoinfra URL: https://cryptoinfra.net/developers Developers An API that is easy to build on. Clear endpoints, signed webhooks and safe retries. Start in the free sandbox with test money, then switch one key to go live. Free sandbox with test money. No card needed. Signed webhooks, retried with backoff. Idempotent requests. A retry never moves money twice. Start free →Read the docs 01Your requestSandbox bash curl -X POST …/v1/users 201 Created { "user_id": "10482", "addresses": [ … ] } 02Your webhook deposit.credited200 OK withdrawal.confirmed200 OK payment.paidRetrying200 OK Built inRESTWebhooksIdempotencySandbox FormatREST · JSON AuthBearer key RetriesIdempotent SandboxFree How it worksFrom sign-up to live in three steps. The sandbox and the live API are the same API. What you build against test money runs unchanged on real money. Start in the sandbox Get a sandbox key, create users, simulate deposits and run payouts with test money. sandbox key Listen for events Register an endpoint and verify each signature over the raw body before you trust it. x-cryptoinfra-signature Switch to live Change the key and the base URL to live. Same endpoints, same payloads, real money. live key The APIEverything you need to ship. Written to be read once and integrated once, by a person or by an AI coding tool. Signed webhooks Every event is signed. Failed deliveries are retried with backoff. Webhook deliveries To your server deposit.credited200 OK card.status200 OK payment.paidRetry 2200 OK Simple REST API Predictable JSON, clear errors and exact amounts as whole-number strings. Idempotent by design Send an idempotency key and retry safely. One request, one result. Free sandbox Get a sandbox key in one call and test deposits, payouts and more. Ready for AI Our docs have an MCP server and llms.txt, so AI coding tools understand the API. Two keys, one switch A sandbox key for testing and a live key for real money. SDKs and plugins SDKs for Node/TypeScript, Python and PHP, store plugins, a Laravel package, and n8n, Zapier and Make apps. SDKs and plugins In the dashboard Node / TypeScript · Python · PHPSDK WooCommerce · WHMCS · Magento 2Plugin n8n · Zapier · MakeApp Trust an event before you act on it. Each webhook carries an HMAC-SHA256 signature of the raw body, made with your endpoint secret. Check it, then credit your customer. Quickstart →Webhooks →Build with AI → import { createHmac, timingSafeEqual } from 'node:crypto'; // check the signature on the raw body const expected = createHmac('sha256', SECRET) .update(rawBody).digest('hex'); const given = req.get('x-cryptoinfra-signature'); if (!timingSafeEqual(Buffer.from(expected), Buffer.from(given))) return res.sendStatus(401); QuestionsGood to know. Is there a test mode? Yes. The sandbox is free and uses test money. You can simulate deposits and run payouts before going live. How do I know a webhook is really from you? Each webhook carries an HMAC-SHA256 signature of the raw body, made with your endpoint secret. What happens if I retry a request? Send the same idempotency key and you get the original result back. Money is never moved twice. Are there SDKs and plugins? Yes. SDKs for Node/TypeScript, Python and PHP; store plugins for WooCommerce, WHMCS, PrestaShop, Magento 2 and more; a Laravel package; n8n, Zapier and Make apps; and a self-hosted Telegram bot. Download them in the dashboard under Payments, Plugins. See the payment gateway. Which networks does the API cover? TRON, BNB Smart Chain, Solana, Bitcoin and TON. Each coin on each network has its own asset id; the live list is GET /v1/assets. Do you have an OpenAPI spec? Yes. The full OpenAPI spec is linked from the docs, and an MCP server lets AI tools read it. Start building in minutes. Start free today. Test in the sandbox, then go live with real money. Start free → Talk to us --- ## Crypto Exchange — Swap Any Coin, No Sign-up | Cryptoinfra URL: https://cryptoinfra.net/exchange Live rate · No sign-up Exchange crypto instantly Swap any coin to any coin, straight from your wallet. Pick the pair, give the address that receives, and send — the other coin is paid to you as soon as yours arrives. Hundreds of coins on dozens of networks, any to any The least you will get, shown before you send Your coins never sit with us — wallet to wallet AccountNone Send fromAny wallet If it cannot completeRefund Coins{{exchangeCoins}} PopularPopular swaps How it worksThree steps. No account. From any wallet to your own address. Nothing is held with us in between. Pick two coins Choose what you send and what you get. The live rate and the least you will receive show as you type. Give your addresses Where the new coin is paid, and where yours comes back if the exchange cannot complete. Both are checked as you paste. Send from any wallet Send the exact amount to the one-time address we show. The other coin is paid to you once yours arrives. CoinsSwap by coin QuestionsGood to know. Do I need an account? No. Pick the coins, give your addresses and send from any wallet. Keep the page’s link — or the exchange ID — to follow your exchange. Is the rate fixed? The rate floats until your coin arrives, so the amount you get can move a little. You never get less than the minimum shown before you send. What if something goes wrong? If the exchange cannot complete, your coin is sent back to your refund address, on the network you sent from. How long does it take? Most exchanges finish within minutes of your coin arriving. Bitcoin and other slower networks wait for their confirmations first. Can I send a different amount? Send exactly the amount shown, before the address closes. A different amount can be refunded rather than exchanged. How do I follow an exchange later? Open the Track tab in the exchange box and paste your exchange ID, or open the page’s link again. Exchanges made on this device are listed there too. I run a business. Can my users swap too? Yes. The same exchange is in our API and dashboard, under your brand and with your own fee. See the swap API. Offer swaps under your own brand. Add this exchange to your own product with one API, and set your own fee on every swap. Start free → Swap API --- ## Fee Calculator — What One Payout or Card Costs | Cryptoinfra URL: https://cryptoinfra.net/fee-calculator Fee calculator What does one operation cost right now? Type an amount, pick the operation, and read the exact deduction and who pays it. Every figure is read from our public price sheet the moment you change anything, so this is the price of this minute, not of this page. Open the calculator →See all prices 01One USDT payoutLive Network fee USDT Our platform fee USDT All in USDT 02The price of this minute Read fromGET /v1/pricing RefreshedEvery minute Typed into this pageNothing Operations4 PricesLive Read fromGET /v1/pricing RefreshedEvery minute Operation Payout Card load Card issue Deposit Amount USDT 25 100 500 1,000 The amount the recipient receives. Receiving wallet Already holds USDT Holds nonenew or emptied This is the customer’s first ever send Card Add your own fee on topoptional Percent of the amount% Flat, per operationUSDT Whatever you add is yours in full. It is set per merchant in the dashboard and read back by your integration from GET /v1/fees. ReceiptOne USDT payout Loading… The API is the authority: GET /v1/withdrawal-fee-quote prices one payout with the recipient known, GET /v1/cards/products carries the card tariff. Full reference in the docs → How to read itFour operations. One rule. Every fee is our live network cost plus a flat platform fee. There is no platform fee on deposits. You earn a share of every platform fee, automatically. Payout The recipient receives the amount. The network fee, our flat platform fee and, once per customer, the first-send activation are held from the customer’s balance on top. A wallet that holds none of the coin costs more to reach. Card load The amount lands on the card. The load fee, a percentage plus a small flat part, and the gas for the on-chain send are paid from your card programme's wallet on top. Card issue The issue fee plus an opening balance, which is priced as a load. An amount under the product’s minimum opening balance is lifted to it. Deposit No platform fee. On TRON and BNB Smart Chain what the customer sends is what is credited, less any fee you set yourself; on the other networks the live network cost of moving the deposit is taken too. In your code Never type a fee into your integration. This page reads the same public sheet your backend should read. For one send, ask the API for the exact quote with the recipient known, and show that figure to your customer before they confirm. Public price sheet at /pricing.json, no key needed, cached for a minute. Exact quote per payout, with the recipient checked, from the fee quote endpoint. Your own fee on top, read back from the API with your key. Fees and pricing, in full Live price tables GET /v1/withdrawal-fee-quotelive # the price sheet, public curl https://cryptoinfra.net/pricing.json # one payout, priced for this recipient curl "https://api.cryptoinfra.build/v1/withdrawal-fee-quote?asset_id=usdt_trc20&amount=100&to=T..." \ -H "Authorization: Bearer $API_KEY" # → network_fee, platform_fee, total, dynamic: true, priced_at QuestionsGood to know. Are these the real prices? Yes. The calculator reads our public price sheet every time you change an input, and the receipt is the same arithmetic the API applies. For one specific send, the fee quote endpoint is the authority, because it checks the recipient’s wallet at that moment. Why does the total change during the day? The network part of a payout is the live cost of energy on TRON, which moves with the TRX price. We price it fresh instead of using a fixed guess, and the receipt says whether the figure is live or a fallback. What is the first-send activation? The first time a customer ever sends from their wallet, the network charges a one-time activation on top. It is held once per customer and never again. Where does my share come from? On every payout, swap, card issue, card load and card close, a share of our platform fee is paid into your balance as the fee settles. The current share is on the price sheet and shown on the receipt. Pay only when money moves. Start free today. Test in the sandbox with test money, then go live. Start free → See all prices --- ## Crypto Payouts API — Send USDT and USDC | Cryptoinfra URL: https://cryptoinfra.net/payouts Payouts Send crypto anywhere. Pay less for it. Send to any address on TRON, BNB Smart Chain, Solana, Bitcoin or TON with one call. We price the network fee live for each send, so you pay what the network costs today, not a fixed guess. Live network fee for every single send. Safe retries. The same request never pays twice. Your fee on top, credited to you on every payout. Start free →Read the docs 01One requestLive fee POST /v1/withdrawals/batch "idempotency_key": "pay_7f3a91" 02Everyone is paidSendingDone 120.00 USDT to TJYB…qBK1SigningSent 0.4 BNB to 0x4f…c91aSigningSent 0.01 BTC to bc1q…7k2mQueuedSent USDT payout, all in USDT Network fee right now USDT Our platform fee USDT Networks5 How it worksFrom request to on-chain in three steps. Ask what it costs, send it, and follow it to the chain. Every step is one call, and a retry is always safe. Ask for the price The fee is the live network cost of that exact send plus our platform fee. See it before any money moves. POST /v1/withdrawal-fee-quote Send it once One payout or a whole batch, each with its own key. Send the request again after a timeout and you get the first payout back. POST /v1/withdrawals Follow it to the chain A signed webhook tells your app when the payout is confirmed on-chain, with its transaction hash. withdrawal.confirmed FeaturesPayouts done right. Built for the two things a payout must never do: cost more than it should, or go out twice. Never pays twice Send the same request again after a timeout. It returns the first payout, never a second one. Retried request One key pay_7f3a91Sent pay_7f3a91 · retrySame payout pay_7f3a91 · retrySame payout Five networks USDT or TRX on TRON; USDT, USDC or BNB on BNB Smart Chain; USDT, USDC or SOL on Solana; USDT or TON on TON; or BTC. Cheaper network fees We use rented network energy instead of burning TRX, and the saving goes to your customer. Status you can follow Signed webhooks tell your app when a payout is sent and confirmed. Your own fee Set your own fee on payouts. It is added on top and lands in your balance. Checks before sending Mistakes like sending to the customer's own address are stopped before any money moves. A whole batch in one call Send many payouts together. Each one stands alone, so one bad address never sinks the rest. Batch payout Sample data TJYBSfZf…wEqBK1Sent TQ8mK2dn…7hVx3PSent TLp41sRe…c9Yt2ASigningSent Live pricingClear prices. Always live. WhatPriceUSDT payout, all inNetwork fee plus our platform fee USDTNetwork fee with usPriced live with rented energy USDTSame send, burning TRXWhat it would cost without rented energy USDTOur platform feePer payout USDTTo an address that never held USDTThe network charges more for a first-time receiver USDT Ask first. Then send, once. Quote the fee, then send with a key of your own. If the answer never reaches you, send the very same request again. Payouts guide →Idempotency → # one payout; the same key can never pay twice curl -X POST https://api.cryptoinfra.build/v1/withdrawals \ -H "Authorization: Bearer $KEY" \ -d '{ "external_user_id": "10482", "asset_id": "usdt_trc20", "to_address": "TJYBSfZf…", "amount": "120.00", "idempotency_key": "pay_7f3a91" }' QuestionsGood to know. How is the payout fee worked out? It is the live network cost of that exact send, plus a small platform fee. You see the full price before you send. What if my request times out? Send it again with the same key. You get the same payout back — money is never sent twice. Can I add my own fee? Yes. Set your fee in the dashboard. It is charged on top and paid into your balance. Which network do payouts use? The network of the coin you send. USDT and TRX go to any TRON address; USDT, USDC and BNB to any BNB Smart Chain address; USDT, USDC and SOL to any Solana address; BTC to any Bitcoin address; USDT and TON to any TON wallet (a payout carries no memo, so not to an exchange address that needs one). The network fee is always charged in the coin you send. Start sending crypto today. Start free today. Test in the sandbox, then go live with real money. Start free → Talk to us --- ## Pricing — Crypto Payment Gateway Fees | Cryptoinfra URL: https://cryptoinfra.net/pricing Live pricing Simple prices. Always live. No setup fee. No monthly fee. You pay only when money moves. And you earn of our platform fee on every payout, swap and card operation. No setup fee and no monthly fee. No platform fee on deposits. Every figure read live from the price sheet the API serves. Start free →Fee calculator 01One USDT payoutLive Network fee USDT Our platform fee USDT All in USDT 02And you earn on it Your share of our fee Paid to your balance USDT Setup feeNone Monthly feeNone Deposits on TRON USDT payout, all in USDT Earn from day one We share of our fees with you. Every time your customers send, swap or use a card, of our fee goes straight to your balance. Nothing to set up. You earn even if you never charge a fee of your own. Example · one USDT payout Our platform fee USDT → You get, automatically USDT 1 of our fee, automatic On every payout, swap, card issue, card load and card close. Paid into your balance the moment we earn it. 2Your own fee, all yours Want more? Add your own fee on top of ours on payouts and swaps. You choose the amount, and all of it is yours. 3See every cent Your Profit page shows each commission and each fee, and you can withdraw your earnings any time. Wallets, payouts and swapsSupported coins and fees. Deposit and withdrawal limits and fees for every supported coinCurrencyMin depositDeposit feeConfirmationsWithdraw fee iPriced live from our API. It is the network cost of the send on that coin's network plus our flat platform fee. Before every send we check the receiving wallet and show the exact fee first.Swap fee % + networkWallet already has the coin iThe receiving wallet already holds some of this coin — for example an exchange account or a wallet in daily use. For USDT right now: network USDT + our fee USDT.Wallet has none iThe receiving wallet holds none of this coin right now — it is brand new, or it was emptied. TRON uses more energy to create its balance. For USDT right now: network USDT + our fee USDT. TRX costs the same either way. new or emptyUSDTBNB Smart Chain (BEP-20) USDT USDT USDT—USDCBNB Smart Chain (BEP-20) USDC USDC USDC—BNBBNB Smart Chain (native) BNB BNB BNB—USDTTron (TRC-20) USDT USDT USDT + USDTTRXTron (native) TRX TRX TRX + TRXUSDTSolana (SPL) USDT USDT USDT USDT—USDCSolana (SPL) USDC USDC USDC USDC—SOLSolana (native) SOL SOL SOL SOL—BTCBitcoin BTC BTC BTC BTC—USDTTON USDT USDT USDT USDT—TONTON (native) TON TON TON TON— Built-in gas saver Lower network fees, built in. A normal TRON wallet pays the network fee by burning its own TRX. We rent network energy instead, which costs much less — and that saving goes straight to your customers. There is nothing to turn on. Live from our API for one USDT send. “Burning TRX” is what a wallet pays when it has no energy of its own. Burning TRXWith us, all inYou save Wallet already has USDT USDT New or empty wallet USDT Swaps between USDT and TRX run on the TRON network itself, even for small amounts. The fee is of the amount — at least USDT — plus the live network cost of the swap. A small USDT swap costs USDT all in right now. Why are there two withdraw fees? On TRON, sending USDT to a wallet that holds none of that coin uses more network energy, so it costs more. It does not matter if the wallet is brand new or was used before and is now empty — what counts is its balance of that coin at the moment you send. Lower feeThe wallet already holds some USDTExample: your customer sends to their exchange account or a wallet they use every day. Fee: USDT Higher feeThe wallet holds no USDTA brand-new wallet, or one that was emptied. The network charges more for the first USDT it receives. Fee: USDT Same feeSending TRXTRX costs the same whether the wallet is new or not. Fee: TRX You never have to guess. We check the receiving wallet before every send and charge the right fee, and you see the exact fee before you confirm. On BNB Smart Chain, Solana, Bitcoin and TON there is one fee for every wallet, new or not. Deposits under the minimum are not credited. Want the number for a given amount? Open the fee calculator → CardsVirtual Visa card. WhatPriceIssue a cardOne time USDTSmallest opening balanceLoaded onto the new card USDTLoad feeOf each loadLoad fee, flat partPer load USDTClose a cardPlus the live network fee USDTNetwork fee on each loadThe live cost of the on-chain send USDTClose: taken from the refundThe card network’s charge to release the balancemin USDT · max USDT on refunds under USDTClose: when the refund arrivesBack in your card programme’s walletup to days When the card is used Charged to the cardholder by the card network VISA WhatPriceEach card payment USD3-D Secure check USDPayment in another currencyATM withdrawalFlat part USDATM withdrawalPercentage partDisputePer case USD Spending limits Set by the issuer on this card. A payment over a limit is declined. LIMITS LimitUp toOne paymentLargest single purchase USDPer dayAll payments in one day USDPer monthAll payments in one month USDATM cashEach withdrawal USDATM withdrawalsPer day timesATM cashPer month USDCard is valid forFrom the day it is issued years QuestionsGood to know. Why do payout prices change? A payout fee is the live network cost of the send plus a flat platform fee. The network cost moves with the TRX price, so we price it fresh instead of using a fixed guess. Why does sending to an empty wallet cost more? The TRON network charges more to send USDT to a wallet that holds none of that coin — whether it is brand new or was emptied. We check the wallet before each send, charge the right fee, and show it to you before you confirm. How do I earn from my customers? Two ways. You get a share of our platform fee on every payout, swap and card operation automatically, paid into your balance as the fee settles. And you can add your own fee on top on payouts and swaps, which is all yours. Can I add my own fee? Yes. Add your own fee on top of ours in the dashboard, on payouts and swaps. You choose the amount, and all of it is yours. How much does one payout cost all in? Type the amount into the fee calculator and pick whether the receiving wallet already holds the coin. It reads the same live sheet as this page and shows the exact deduction, your share included. Can my app read these prices? Yes. The same price sheet is public at /pricing.json, and the exact fee for one payout comes from the fee quote endpoint in our API. Pay only when money moves. Start free today. Test in the sandbox, then go live with real money. Start free → Talk to us --- ## Privacy Policy — Cryptoinfra URL: https://cryptoinfra.net/privacy Legal Privacy Policy What personal data Cryptoinfra collects, why, who sees it and how long it is kept. Last updated 21 November 2026. 1. Who is responsible Cryptoinfra is a product of SPDJ MEDIA LLC (“SPDJMEDIA”, “we”), a California limited liability company with its principal place of business at 166 Geary St, 15th Floor, San Francisco, CA 94108-5631, United States. We decide how the data of our merchants, their team members and visitors to our sites is used. For the data of a merchant's own customers — their end users, the people who pay on our payment pages, and cardholders — we process it to provide the service to that merchant, and the merchant's own privacy policy also applies; we also use it ourselves where we must, for example to prevent fraud or to meet legal obligations. 2. What we collect Merchants and their team members Account: company name, email address, a Telegram username, an optional logo or profile picture; your password (stored only as a one-way hash) and your authenticator secret; your role, invitations and sign-in status. Sign-up and sign-in: IP address and the location derived from it, browser and device information (including a hash of browser headers used to recognise a device), the network the IP belongs to, and the time of each sign-in. How you found us: campaign tags, the referring site, the first page you visited and, if you came from an ad, its click identifier. Business details: your projects' names, websites, categories and descriptions, the support contacts you give your customers, and your webhook addresses. Use of the service: the actions taken in your dashboard and through your API keys, with time, IP address and browser; API requests (method, path, status and timing only). Support: your conversations with our support assistant and with us. Your end users (through the API) A numeric identifier you choose (we never ask for a name or email), the deposit addresses we create for it, and the transactions to and from them, including the sending and receiving blockchain addresses. People who pay on our payment pages The order details the merchant sends (order reference, amount, description and any extra fields) and, if the merchant or the payer gives it, an email address. The coin and network chosen and the transactions that pay the order. The IP address, used for a short time to limit abuse. Cardholders We keep the cardholder's email address, name, the card partner's reference and the verification status. Identity details given for a card (name, date of birth, address, phone, nationality, identity document number), photos of the identity document and a selfie, and a delivery address for a physical card, are passed to our card partner or identity verification provider and are not stored by us; a reference to an uploaded file is kept for at most 24 hours. Card transaction notifications from the partner, with card numbers, security codes and one-time codes removed. Visitors to our websites and the instant exchange Questions asked to our public assistant are sent to answer them; the conversation is kept only in your browser for that visit. For an exchange: the coins, amounts and the deposit, destination and refund addresses. We do not ask for a name or email. Web server logs with IP addresses, kept for about 14 days. 3. Why we use it to provide the service: open and secure accounts, create addresses, credit deposits, send payouts, run payments, swaps and cards, and notify you; to keep accounts and money safe: sign-in security, detecting linked or fraudulent accounts, preventing abuse; to meet legal obligations, including anti-money-laundering and sanctions rules, and to answer lawful requests from authorities; to answer support requests and improve the service and the documentation; to measure which of our ads bring sign-ups. Where the law asks for a legal basis, we rely on performing our contract with you, our legitimate interests in running a secure service, our legal obligations, and your consent where we ask for it. 4. Who we share it with We do not sell personal data. We share it only as needed with service providers who work for us under contract, in these categories: card issuing partners and an identity verification provider (cardholder data, as described above); hosting, content delivery and security providers that carry our traffic and check that a sign-up is not a bot; an email delivery provider (the address, subject and content of the emails we send); an AI model provider that powers our support assistant, which receives the questions asked and, for a merchant's assistant, the account information needed to answer them; an IP location service (the IP addresses of sign-ups, sign-ins and some account actions); blockchain network and data providers, and exchange routers, which receive addresses and transactions — and anything recorded on a public blockchain is public; an advertising platform that measures our own ads (pages visited, the ad click identifier and a sign-up event); encrypted backup storage. The merchant you deal with receives the data of its own payments, users and cardholders. We may also disclose data where the law requires it, to protect our rights or users, or as part of a sale or reorganisation of our business. 5. International transfers We and our providers process data in several countries, which may not have the same data protection laws as yours. Where the law requires it, we use appropriate safeguards for these transfers. 6. How long we keep it Sessions end after at most 12 hours of use. The general activity log is kept for 30 days and API request records for 14 days; records of operator actions are kept permanently. Sent emails are kept for 90 days, one-time-code emails for 24 hours. Account, transaction, payment, card and exchange records — and sign-in history — are kept while the account exists and afterwards for as long as the law and the prevention of fraud require. Encrypted backups are kept for up to 12 months. 7. Cookies and browser storage Sign-in cookies (mcid, mxchg, mrst on the dashboard): keep you signed in and carry a sign-in or reset step. Necessary; they cannot be switched off. ci_src: remembers how you first arrived (campaign tags, referring site, landing page, ad click id) for 90 days, so a sign-up can be credited to it. Advertising: our websites and dashboard load an advertising platform's tag to measure our ads, which may set that platform's cookies. In the European Economic Area, the United Kingdom and Switzerland it does not store ad cookies or ad user data. Bot check: the sign-up page loads a security provider's check. Page-view analytics: our content delivery provider adds a small script to our pages that counts visits and page speed without cookies. Browser storage: your theme, some dashboard layout choices, the public assistant's conversation for the visit, and the ids of your recent exchanges. These stay in your browser. The payment pages at pay.cryptoinfra.net — including when a merchant shows them inside its own site — set no cookies of their own and load no advertising tag. 8. Your choices and rights Depending on where you live, you may have the right to access, correct or delete your personal data, to object to or restrict its use, to withdraw consent, and to receive a copy of it. To use them, contact us (section 11); we may need to verify who you are, and we may keep data the law requires us to keep. If you are a merchant's customer, you can also ask the merchant. You may complain to your data protection authority. California residents. The California Consumer Privacy Act, as amended, gives you the right to know what personal information we collect and how we use it, to have it deleted or corrected, and to opt out of its sale or sharing. We do not sell personal information. The advertising tag described in section 7 may count as “sharing” for cross-context behavioural advertising; you can opt out by blocking advertising cookies in your browser or by emailing us, and we will not treat you differently for using any of these rights. 9. Security Passwords are stored only as hashes, sign-in requires an authenticator code, connections are encrypted, card secrets are not stored, and backups are encrypted. No system is perfectly secure; if a breach affects your data we will tell you as the law requires. 10. Children Cryptoinfra is for businesses and is not directed at children. We do not knowingly collect children's data. 11. Contact and changes SPDJ MEDIA LLC 166 Geary St, 15th Floor, San Francisco, CA 94108-5631, United States Privacy questions and requests: company@spdjmedia.com · Telegram: our support channel To use a right in section 8, email us; we will answer within the time the applicable law requires and may first need to verify who you are. We may update this policy. The date at the top shows the latest version; if a change is material we will tell merchants through the dashboard or by email. --- ## Security — How Cryptoinfra Protects Every Coin URL: https://cryptoinfra.net/security Security Built to protect every coin. Security is part of how every piece works, not an extra. Here is how we keep your money and your customers' money safe. Signing keys never live on our API servers. An authenticator code for every dashboard change. Books matched with the blockchain every few minutes. Start free →Read the docs 01Keys kept apart API serverswatch-only keysCreate addressesCannot spend Signing keysnever on the API serversSign each payout once 02Every change is confirmed Authenticator codeRequired Books against the chainCheckingMatched A retried payoutSent once Signing keysOff the API Every changeAuthenticator code BooksChecked on-chain Each payoutSent once How a payout stays safeThree checks before any coin moves. A payout passes each of these in turn. Failing one stops it, and the amount stays in the balance. Who is asking A request needs your API key. Signing in needs your password and an authenticator code, and every change is confirmed with the code. Is it allowed The balance must cover it, the address must be valid for the coin's network, and a mistake like paying the customer's own address is refused. Has it been sent The idempotency key is checked. A request we have already seen returns the first payout and never sends a second. How we protect youSafe by design. The rules the platform is built on, from where the keys live to the last retried request. Keys kept apart Addresses are made from watch-only keys. The servers you talk to can never spend money. What a server can do By design API server · create an addressYes API server · sign a payoutNever Signing keys · on the APINever A code, every time Signing in and every change in the dashboard need a code from your authenticator. Checked against the chain Balances in our books are matched with the blockchain every few minutes. One payout, once Idempotency keys make sure a retried request can never pay twice. Team roles Give each team member only the access they need. Your brand only Partner names are removed from the API and from webhooks before they reach your app. An alert on any gap Our books are compared with the blockchain every few minutes, and any gap raises an alert. Books against the chain Sample data USDT · TRONMatched BTC · BitcoinMatched SOL · SolanaCheckingMatched QuestionsGood to know. Where are the private keys? Not on our API servers. Those servers hold only watch-only keys, which can create addresses but never sign a payment. How do you stop someone taking over a dashboard? Every sign-in needs your password and an authenticator code, and every change is confirmed with the authenticator code. How do you know the balances are right? Our books are compared with the blockchain every few minutes, and any gap raises an alert. Build on infrastructure you can trust. Start free today. Test in the sandbox, then go live with real money. Start free → Talk to us --- ## Crypto Swap API — USDT and TRX Swaps | Cryptoinfra URL: https://cryptoinfra.net/swap Swap Swap coins. Pay out in any coin. Let users swap between the coins they hold and pay out in thousands of other coins, priced live, under your brand. Swap between USDT and TRX in one call. Pay out in thousands of other coins to any address. Your own fee on every swap, plus a share of ours. Start free →Read the docs Our swap fee Minimum fee USDT Network, USDT to TRX USDT Coins on the exchange{{exchangeCoins}} How it worksFrom quote to settled in three steps. A swap is three calls from your backend. Your user never leaves your app. Ask for a quote Each quote shows the estimate and the minimum the user will receive. POST /v1/swap/quote Place the order USDT and TRX swaps settle on-chain on TRON, from the user's own address, and the coins land in their balance. POST /v1/swap/orders Read the result Poll the order until it reaches a final state. There is no webhook for a swap. GET /v1/swap/orders/{id} FeaturesMore ways to move money. Two things your users can do without leaving your app: swap what they hold, and pay out in another coin. Swap in one call Get a quote, place the order, and the coins land in the user's balance. Quote Sample data You send100.00 USDT Estimate412.60 TRX Minimum you receive408.47 TRX Thousands of coins out Sell a coin and pay a different one out to any address. Honest quotes Each quote shows the estimate and the minimum the user will receive. On-chain on TRON USDT and TRX swaps settle on-chain, from the user's own address, with a transaction anyone can look up. Your margin Add your own fee on swaps. It is paid straight into your own balance, next to a share of our fee that goes to you automatically. Priced live Our fee and the network cost are read live for every quote, so the user sees the real price before they confirm. A ready exchange, too Send your users to an instant exchange between every coin we support. No account, no sign-up. Open the exchange → Exchange Sample data BTCYou send SOLYou receive OrderExchangingDone Live pricingClear prices. Always live. WhatPriceOur swap feeOf the amount, with a minimumMinimum feeOn a small swap USDTNetwork, USDT to TRXThe swap’s own gas on TRON, live USDTNetwork, TRX to USDTPaid in TRX TRXA small USDT swap, all inMinimum fee plus network USDT QuestionsGood to know. Which coins can users swap? USDT and TRX within their balance. With an exchange order they can pay out in thousands of other coins. Is the swap price fixed? A quote shows an estimate and a minimum. The user receives what actually arrives, never less than the minimum. Can I add my own fee? Yes. Set your own swap fee in the dashboard. It is added on top and paid into your own balance, next to your share of ours. Is there a webhook when a swap finishes? No. Swaps and exchanges are read by polling the order until it reaches a final state. The docs show how. Give your users more ways to pay. Start free today. Test in the sandbox, then go live with real money. Start free → Talk to us --- ## Terms of Service — Cryptoinfra URL: https://cryptoinfra.net/terms Legal Terms of Service The terms on which SPDJ MEDIA LLC provides Cryptoinfra. Last updated 21 November 2026. 1. Who we are and what these terms cover Cryptoinfra is a product of SPDJ MEDIA LLC (“SPDJMEDIA”, “we”, “us”), a California limited liability company with its registered office at 166 Geary St, 15th Floor, San Francisco, CA 94108-5631, United States. These terms govern your use of Cryptoinfra: the merchant dashboard and the API at cryptoinfra.build, the hosted payment pages at pay.cryptoinfra.net, the website and documentation at cryptoinfra.net, the store plugins and SDKs we publish, and the instant exchange. By opening an account, using an API key or installing one of our plugins you accept these terms on behalf of the business you represent. Cryptoinfra is a service for businesses. You must be able to enter into a binding contract and use it for a lawful business. 2. What Cryptoinfra does Wallets. We give each of your users deposit addresses on the networks we support and credit deposits to your account once the network has confirmed them. Payouts. We send coins from your balance to the addresses you instruct, on the network you choose. Every movement of money is an on-chain transaction. Payment gateway. You create a payment priced in US dollars; your customer pays it on our hosted page (on its own, embedded in your site, or through a payment link); we tell you when it is paid and credit it to your account. Swaps and exchange. We convert one supported coin into another at the rate shown before you confirm. Cards. Where offered, debit cards for you or your users, issued and run by our card partners. The coins and networks we support, and the features available to an account, are listed in the dashboard and the documentation and may change. 3. Your account You give true information when you sign up and keep it current. We may refuse or close an account at our discretion. Your account is protected by your password and your authenticator app. You keep them, your API keys and your callback secret confidential, and you are responsible for everything done with them. Tell us at once if you think any of them has been exposed. You are responsible for the people you invite to your dashboard and for what they do. 4. Custody of your balance Cryptoinfra is a custodial service: the coins credited to your account are held in wallets we control on your behalf, and your balance is what our records show you are owed. Your balance is not a bank deposit and is not covered by any deposit protection scheme. We do not lend out your coins. 5. Blockchain transactions A transaction confirmed on a blockchain cannot be reversed by us or by anyone. Coins sent to a wrong address, on a network other than the one shown, or as a coin other than the one asked for may be lost. We are not responsible for such losses, though we will tell you what we can see. A deposit is credited only after the number of network confirmations we require. The network fee of a payout is charged in the coin you send. Networks can be slow, congested, forked or halted. We may delay or pause deposits, payouts or swaps on a network while that lasts. 6. Payments from your customers When you take payments through the gateway, you, not we, are the seller. You are responsible for your goods and services, your prices, refunds and disputes with your customers, and for the information you send us about them. A payment closes at its deadline; an amount that arrives short or late is shown to you to decide on, and the payment page tells the customer so. You fulfil an order only on a notification we have signed (or a payment you have read back from the API), never on what a browser tells you. 7. Your users and your compliance You are responsible for your own customers and end users: for knowing who they are where the law requires it, for the products you offer them under your brand, and for complying with the laws that apply to your business, including anti-money-laundering, sanctions, consumer protection and tax laws. You will give us the information we reasonably ask for to meet our own legal obligations. 8. What you may not do use Cryptoinfra for anything illegal, for fraud, or to move the proceeds of crime; use it for or with persons or places under sanctions that apply to us; try to get into accounts, systems or data that are not yours, test our security without our written permission, or interfere with the service; resell access to your account, or misrepresent your relationship with us; copy, reverse engineer or build a competing service from our software, except as the licences of our published plugins and SDKs allow. 9. Fees Our fees are shown on the pricing page and in your dashboard, and are deducted as described there. We may change them; a change applies to transactions made after it is published. 10. Cards Cards are issued and operated by our card partners, and a cardholder's identity may be verified by them. Their own terms may also apply. We may stop offering a card programme, or a card, where a partner or the law requires it. 11. Suspension and closure We may suspend or limit an account, or hold a transaction, where we reasonably suspect a breach of these terms, fraud or illegal activity, where the law or an authority requires it, or to protect the service. You may stop using Cryptoinfra at any time. When an account is closed we will, unless the law prevents it, let you withdraw your remaining balance to an address you control, after any fees owed. 12. Our plugins and SDKs The store plugins, SDKs and code samples we publish are licensed under the licence stated in each package (for the WordPress plugins, GPL v2 or later). They are provided as they are; you install and run them on your own systems. 13. Availability and changes We work to keep Cryptoinfra running and correct, but we do not promise that it will be uninterrupted or free of errors. We may change, add or remove features. We will give notice of a change that removes something you depend on where we reasonably can, through the dashboard, the changelog or email. 14. No warranties Except as these terms expressly say, Cryptoinfra is provided “as is” and “as available”, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement, to the fullest extent the law allows. 15. Limits on our liability To the fullest extent the law allows, we are not liable for indirect, incidental, special or consequential losses, lost profits or lost data, and our total liability arising from these terms or the service in any twelve-month period is limited to the fees you paid us in that period. Nothing in these terms limits liability that cannot be limited by law. 16. Indemnity You will cover our losses and reasonable costs arising from your breach of these terms, from your products and your dealings with your customers, or from your violation of any law or of anyone else's rights. 17. Changes to these terms We may update these terms. The date at the top shows the latest version. If a change is material we will tell you through the dashboard or by email before it applies; using Cryptoinfra after that means you accept the new terms. 18. Law and disputes These terms and any dispute arising from them are governed by the laws of the State of California, United States, without regard to its conflict of laws rules. The state and federal courts located in San Francisco County, California have exclusive jurisdiction, unless the law where you are based gives you rights that cannot be taken away. 19. Contact SPDJ MEDIA LLC · D-U-N-S® Number 092506169 166 Geary St, 15th Floor, San Francisco, CA 94108-5631, United States Email: company@spdjmedia.com · Telegram: our support channel --- ## Crypto Wallet API for USDT and USDC | Cryptoinfra URL: https://cryptoinfra.net/wallets Wallets A crypto wallet for every customer. Create a user with one API call and get a permanent address on every network: TRON, BNB Smart Chain, Solana, Bitcoin and TON. When money arrives, we credit it and tell your app right away. One address per customer on each network. It never changes. No platform fee on deposits, in full on TRON and BNB Smart Chain. Signed webhooks the moment a deposit is credited. Start free →Read the docs 01One API callSandbox POST /v1/users { "external_user_id": "10482" } 02Deposits credit themselves TRONTJYB…qBK1 Bitcoinbc1q…7k2m + 250.00 USDT on SolanaConfirmingCredited Networks5 Deposit fee on TRON Smallest USDT deposit USDT Confirmations on TRON How it worksFrom API key to first deposit in three steps. You never run a node, watch a chain or touch a key. Create the user, show the address, and wait for the webhook. Create the user One call with the id this customer has in your own system. Send it again and you get the same user back. POST /v1/users Show the address Each customer gets one address per network. Show it once in your app: it works for good. GET /v1/users/{id}/addresses Hear when money lands We watch the chain, wait for the confirmations and credit the balance. Your server gets a signed webhook. deposit.credited FeaturesEverything to hold and move crypto. One balance per coin behind every customer, credited by itself and checked against the chain. Automatic crediting We watch the chain, wait for confirmations and credit the balance. No manual work, and nothing for you to reconcile. Deposits Sample data user 10482+ 250.00 USDT user 20917+ 1,400 TRX user 31150ConfirmingCredited Permanent addresses Each customer gets one address per network: TRON for USDT and TRX, and one each on BNB Smart Chain, Solana, Bitcoin and TON. Webhooks you can trust Every deposit event is signed, and tells you who sent the money and how much arrived. Balance you can check See each balance next to what the address holds on-chain, side by side. Free sandbox Test with fake money. Simulate deposits and see the whole flow before going live. Keys kept safe Addresses are made from watch-only keys. Our API servers can never spend. Every network's own coin, too TRX, BNB, SOL and TON are balances like any other. Each coin on each network is held and credited on its own. Balances Sample data USDT48,210.55 BNB12.4081 TON3,050.00 Live pricingClear prices. Always live. WhatPriceDeposits on TRONCredited in fullSmallest USDT depositSmaller amounts are ignored as dust USDTSmallest TRX deposit TRX The whole wallet, in one event. When a deposit clears its confirmations, your server gets one signed request. Verify the signature, credit your customer, done. Static wallet addresses →Webhooks → # sent to your server the moment a deposit is credited x-cryptoinfra-event: deposit.credited x-cryptoinfra-signature: 9f2c41… { "userExternalId": "10482", "assetId": "usdt_trc20", "chain": "tron", "amountCredited": "250.00", "fromAddress": "TQ8mK2dn…" } QuestionsGood to know. Which coins can my customers hold? USDT and TRX on TRON; USDT, USDC and BNB on BNB Smart Chain; USDT, USDC and SOL on Solana; BTC on Bitcoin; USDT and TON on TON. Each coin on each network is its own balance, each network's own coin included. Does the address ever change? No. Each customer keeps the same address for good. Creating the same user again returns the same address. How do I know a deposit arrived? We send your app a signed webhook as soon as the deposit is credited, with the amount and the sender. Do deposits cost anything? There is no platform fee on a deposit. On TRON and BNB Smart Chain the customer receives the full amount; on the other networks only the live network cost of moving the deposit into our wallet is taken. Your own fee, if you set one, comes off too. Give your customers a wallet today. Start free today. Test in the sandbox, then go live with real money. Start free → Talk to us --- ## White Label Crypto Card Provider | Cryptoinfra URL: https://cryptoinfra.net/white-label-crypto-card-provider White label cards A white label crypto card provider your users never see. A white label crypto card provider runs the card rail, the funding, the security codes and the settlement, while your company puts its own name on the product. Cryptoinfra issues virtual Visa debit cards funded with USDT for your users, inside your app, with your brand on every screen and your fee on every card. Your brand only. Partner names are removed from the API, webhooks and screens. Your price. Charge your users what you like; we bill only your card programme's wallet. Live after sign-up. No contracts to negotiate, no setup fee, no monthly fee. Launch your card program →Talk to us 01Your app, your cardYour brand YOUR BRAND•••• 4821VISA Apple PayGoogle PayYour prices 02What your user sees Card and screensYour brand Security codesYour brand Partner namesNone Card issue fee USDT Card load fee Partner names shownNone Card networkVisa What white label means hereWe run the rail. You own the customer. White label is not a logo swap. It is every place a user could meet a third party, closed off. Your app, your screens Users apply, reveal the card, load it and close it inside your product. There is no redirect to anyone else's page. Security codes in your brand 3-D Secure one-time codes are delivered to your server, so your user confirms a payment in your app, not in a partner's SMS. Clean API and webhooks Responses and events name no issuer, processor or network partner. What your developers read is what your users could read. Your prices Charge your users your own price for issuing, loading and closing cards, in your own app. Our fee is public, so you always know your margin. Funded from USDT Cards are paid from your card programme balance, which you fund with USDT on TRON (TRC20) or BNB Smart Chain (BEP20). Every issue and load shows its fee first. Apple Pay and Google Pay The cards work in phone wallets and anywhere Visa is accepted, online and in store. Revenue Your card wallet funds every card. You set the price. Every card you issue and every load is paid from your card programme's wallet. What your users pay you for a card is your decision, and the difference is yours. A share of our own fee comes back to your balance on every issue, load and close, automatically. 1A card wallet per project Fund it in USDT on TRON or BNB Smart Chain. It pays for every card and every load of that project's users. 2Your price Charge your users what you like, in your own app. Users see one price, yours. 3Every line visible Your dashboard lists each issue, load and close with what it cost. Card issue feeOurs, one time USDT Card load feeOurs, on each load Card close feeOurs, when a card is closed USDT Setup or monthly feeNone Your price to usersYou set it How it worksYour branded card program in three steps. Create your account Sign up with your email. The account is live at once, with a free sandbox and test money. Connect the card API Create users, run the identity check, issue and load cards, and listen for signed webhooks. The crypto card API page shows the calls. Launch under your name Switch to the live key, set your prices and issue real cards. Your users never learn who runs the rail. Who it is forBuilt for businesses whose users already hold USDT. Wallet and exchange apps Give users a way to spend the USDT they already keep with you, without sending them to another brand. Payment and remittance companies Pay out to a card instead of a bank account, in the same app your customers already use. Fintech and neobank products Add a USDT-funded Visa card to an existing account product, priced and branded by you. Platforms that pay creators or freelancers Let the people you pay spend their earnings the same day, on a card with your name on it. Agencies and resellers Launch a card product for your own clients, set your own price on every card, and keep the relationship. Developers testing an idea The sandbox is free and the API is the same as production, so a prototype costs nothing to build. Choosing a provider How to evaluate a white label crypto card provider. CheckWhy it mattersCryptoinfra Partner names hidden everywhereOne issuer name on a statement or an SMS undoes the whole white label.Removed from API, webhooks and screens Public pricingYou cannot price your own product if the provider's prices are "on request".Live public price sheet Your marginA provider that bills your users directly leaves nothing to build a margin on.You set the price your users pay Time to liveMonths of contracts kill most card ideas before launch.Live after email sign-up Sandbox parityTesting on a different API than production means bugs at launch.Same endpoints, test money Security modelSigning keys on an API server are one breach away from your users' funds.Keys kept off the API servers; an authenticator code on every change Machine-readable docsYour developers, and their AI tools, should read the API before you sign anything.OpenAPI spec, llms.txt, MCP server QuestionsWhite label crypto cards, answered. What is a white label crypto card provider? A white label crypto card provider operates the card rail, funding, 3-D Secure and settlement behind the scenes, while your business sells the card under its own brand. Cryptoinfra is one: it issues virtual Visa debit cards funded with USDT for your users through one REST API, and nothing your users see carries a partner's name. Will my users ever see Cryptoinfra or a card partner? No. Your users use your app. The API responses, webhooks and screens carry no issuer, processor or network partner name, and the 3-D Secure code is delivered to your app rather than to a third party. How do I make money as a white label card provider? You set the price your users pay for a card and for each load, in your own app. Our fee is public, and the difference between your price and ours is yours. On top of that, of our own fee on every card operation is paid into your balance automatically. What does it cost to launch a white label card program? Nothing up front. There is no setup fee, no monthly fee and no minimum volume. Our per-card fees are on the live price sheet. How are the cards funded? From your card programme balance, in USDT. You fund it on TRON (TRC20) or BNB Smart Chain (BEP20), and each card issue or load is paid in one of the two after the fee is quoted. Are the cards virtual or physical? Virtual Visa cards, which can be added to Apple Pay, Google Pay and Samsung Pay and used online or in store wherever Visa is accepted. How long does it take to go live? Your account is live as soon as you verify your email. Build against the free sandbox, then switch to the live key when your app is ready. Do I need my own developers? Someone who can call a REST API and receive a webhook is enough. The docs are public, the whole reference is one text file, and an MCP server lets an AI coding tool read the API directly. Start today Your card. Your brand. Your revenue. Create your account, build against the sandbox, then issue your first card under your own name. Launch your card program → See the card API --- ## White Label Crypto Payment Gateway | Cryptoinfra URL: https://cryptoinfra.net/white-label-crypto-payment-gateway White label gateway Launch your own crypto payment gateway. Offer USDT payments to your clients under your own brand. We run the addresses, confirmations, webhooks and payouts — you set the prices and keep your fees. Your brand only No setup or monthly fee Free sandbox Create free account →Talk to us 01Your client's checkoutExample YYour brand Checkout · USDT on TRON120.00 02You keep the customer Payment receivedConfirmingCredited Partner names shownNone Your own feeYou set it Receiving on TRON Partner names shownNone Setup and monthly feeNone Networks5 Earn from day one You earn of our fee. Every time one of your clients sends funds out, part of our fee goes straight to your balance. Nothing to set up — and your own fee on top is all yours. 1 of our fee, automatic On every payout your clients make, paid into your balance the moment we earn it. 2Your own fee, all yours Add your own fee on payments and payouts. You choose the amount. 3See every cent Your Profit page shows each commission and each fee, and you can move earnings out any time. Earnings calculator Payouts your clients make each month 1,000 Your own fee per payout optional USDT From your share of our fee— USDT From your own fee— USDT Your earnings each month— USDT Worked out from today's live prices: our fee of USDT per payout and your share. An estimate, not a promise. Build or launch Skip the plumbing. Everything a payment gateway needs underneath is already running. You bring the brand and the clients. Building it yourself Your team runs the hard parts Run and monitor your own node on every network Guard signing keys and build safe key storage Track confirmations and handle chain reorgs Write webhook retries, network fee pricing and reconciliation Launching on Cryptoinfra You ship the brand All of it already running, behind one REST API Your name on every screen your clients see Your own fees on payments and payouts Live right after sign-up, with a free sandbox to start What you getA whole gateway, without building one. Your brand, end to end Your app, your checkout, your name. Partner names are removed from our API and webhooks. A permanent address per customer Each of your clients' customers gets one address for life on TRON and one on BNB Smart Chain. Payments to it are credited on their own. Signed webhooks Every payment and payout reaches your server signed with HMAC-SHA256, ready to pass on under your name. Payouts on the same API Send USDT or TRX on TRON, or USDT on BNB Smart Chain, with the network fee priced live for each send. A free sandbox Every call works with test money first. Switch to real payments when your checkout is ready. A code for every change An authenticator code on every dashboard change, and keys kept off our API servers. How it worksYour gateway, live in three steps. Create your account Sign up with your email. Your account is live right away — no waiting for approval. Build on our API Create customers, show their addresses in your own checkout and listen for signed webhooks. Launch under your name Go live with real payments and set your own fee on every payout your clients make. Pricing to receive a payment on TRON or BNB Smart Chain. No platform fee on any network, no setup fee and no monthly fee. Create free account → Receiving on TRON or BNB Smart ChainCredited in full Setup or monthly feeNone Our fee per payoutPlus the network fee, priced live USDT Your own feeOn payments and payoutsYou set it QuestionsGood to know. Will my clients see your name? No. Your clients use your app and your brand. Partner names are removed from our API and webhooks. How do I earn from it? Two ways. You get a share of our platform fee on every payout your clients make, paid into your balance automatically. And you can add your own fee on top, which is all yours. Can I add my own fee? Yes. Add your own fee on payments and payouts in the dashboard. You choose the amount, your clients pay one price, and all of your fee is paid into your balance as each operation settles. What does it cost to start? Nothing. There is no setup fee and no monthly fee. There is no platform fee to receive a payment — on networks other than TRON and BNB Smart Chain only the live network cost of moving it is taken — and you pay our fee only when money is sent out. Every price is on our live price sheet. Which coins and networks? USDT and TRX on TRON; USDT, USDC and BNB on BNB Smart Chain; USDT, USDC and SOL on Solana; BTC on Bitcoin; USDT and TON on TON. Your clients can also take orders on a hosted checkout, with store plugins, payment links and a point-of-sale screen — see the payment gateway. Do I need my own developers? You need someone who can call a REST API and receive a webhook. The docs, a free sandbox and ready examples cover the rest. How fast can I go live? Your account is live as soon as you verify your email. Test with free sandbox money first, then switch to real payments when you are ready. Start today Your gateway. Your brand. Your revenue. Create your account, build in the free sandbox, then launch under your own name. Create free account → Talk to us on Telegram Your brand only No setup or monthly fee Free sandbox --- ## Best Crypto Card API: 7 Questions to Ask Before You Choose URL: https://cryptoinfra.net/blog/best-crypto-card-api-what-to-look-for Published: 2026-11-08 You have decided to add a card to your product. You search for the best crypto card API and get a long list of names that all say the same thing: we issue cards. The real differences show up later. A partner's name on a statement. A fee that appears after the load. A webhook that never arrives. This guide gives you seven questions to ask any provider, including us, before you sign. Each one comes with the bad day it prevents. In shortEvery provider can issue a card. What differs is what happens after the card exists. Seven questions cover it: white label, the 3-D Secure code, public fees, your own price, safe retries, signed webhooks and a real sandbox. A good provider lets you read the docs, see the prices and build against a sandbox before you talk to sales. The best crypto card API is the one that passes all seven for your product. #What does a crypto card API do? A crypto card API is a set of HTTP endpoints. Your backend calls them to run a card programme, and your users never leave your app. One card, from the first call to the last01Create the cardholderA user record, with an identity check 02Issue the cardA virtual Visa debit card, funded with a stablecoin such as USDT 03Load itValue moves from a crypto balance onto the card, for example 100 USDT 04Deliver codes and eventsThe 3-D Secure code, and a webhook for issued, loaded, declined and closed 05Close itThe remaining balance is returned If a provider cannot show you each step in public documentation before you talk to sales, that is the first answer you needed. #Will your users ever see another company's name? Picture one of your users a week after launch. Her card statement shows a company she has never heard of. Then a payment code arrives by text message from an unknown sender. She does not think "white label partner". She thinks "scam". #1. Is it white label all the way down? "White label" often means your logo on someone else's app. Real white labelling means your users never meet anyone but you: not on the card, the statement, a text message, or an API response your developer copies into a screen. Ask: where could my user see a partner's name? The right answer is "nowhere". Our white label crypto card provider page shows how we close each gap. #2. Where does the 3-D Secure code go? When a cardholder pays online, the shop may ask for a one-time code. If the provider sends that code by its own SMS, your user has just learned who really runs the card, and you cannot show the code in your app. The code should reach your server, so that your app presents it under your brand. The full flow is in how 3-D Secure works on a crypto debit card. #Will you know every price before you build? You are about to set a price for your own users. You cannot do that on top of a number you have not seen. #3. Are all fees public before the first call? Prices "on request" ask you to design a product blind. Look for a public, machine-readable price sheet that lists the issue fee, the load fee, the close fee and anything charged per card per month. Then check the API itself. It should quote the exact fee before the load, so your app can show it to the user first. A fee that appears after the money has moved becomes a support ticket. #4. Can you set your own price? A provider that bills your users directly leaves you nothing to build a margin on. The better model: the provider publishes its fee, you set the price your users pay, and the difference is yours from the first card. See how to set your own fee. #What happens on a bad day? A demo only shows good days. Your users will live through the other kind: a dropped connection, a server restart, a bug that only appears in production. #5. Are writes idempotent? Your server sends "load the card". The connection drops before the answer comes back, so your server sends it again. Did your user just pay twice? With an idempotency key, no. Every write that moves value should accept a key and return the original result on a retry. Without it, you spend your support budget on refunds. #6. Are webhooks signed and retried? A card programme runs on events. Imagine a load finishes while your server is restarting. If the provider sends the webhook once and gives up, the balance in your app is now wrong. Look for a signature on every webhook, so nobody can forge one, and retries until your server acknowledges the event. Our guide to receiving webhooks safely covers both. #7. Does the sandbox match production? Some providers offer a demo that behaves differently from the live API. The real bugs then appear at launch, in front of real customers. A proper sandbox has the same endpoints and the same events, with test money. Going live should be a change of key, not a rewrite. Here is how to use a sandbox well. Ask, too, what the sandbox does not cover, and judge the honesty of the answer. Ours runs deposits, payouts and webhooks on test money. Card calls need the live card rail, so a card gets its first test for real: your own card, with a small load. #What does a good answer look like? Put the seven questions to every provider on your list. Then compare the answers side by side. The seven questions on one pageA weak answerA good answerPartner namesOnly on the statementNowhere — not on screens, codes, the API or webhooks3-D Secure codeBy SMS, from the providerTo my server, shown in my appFeesOn requestOn a public sheet, and quoted before each callMy own priceThe provider bills my usersTheir fee is public and my price is mineRetried requestsRetry at your own riskAn idempotency key on every writeWebhooksSent once, unsignedSigned, and retried until acknowledgedSandboxA separate demoSame endpoints and events, with test money Paste this into your evaluation sheet, one column for each provider. #Which red flags should end the conversation? Some answers are not weak. They are reasons to walk away. Four mistakes buyers makePaying before the first cardholderA setup fee, a monthly minimum or a volume commitment costs you before a single card exists. Choose a provider with none. Signing to read the documentationPick public docs, with a machine-readable version an AI coding tool can read. Parking a float in a bank accountDo not pre-fund a provider's bank account. Fund cards with a stablecoin your users already hold. Accepting a partner's brand in "just one place"One place is enough to confuse a user. Accept none. #How does Cryptoinfra answer the seven questions? We built our crypto card API around this list. White label end to end. Partner names are removed from the API, the webhooks and every screen. The 3-D Secure code is delivered to your app. Public prices. Every fee is on a live sheet on the pricing page and quoted before the call. No setup fee, no monthly fee, no minimum volume. Your own price. Every card is paid from your card programme's wallet. A share of our fee comes back to you on each issue, load and close, and what you charge your users is your own price. Ready for bad days. Idempotent writes, and signed webhooks retried until you acknowledge them. A free sandbox with the same API for deposits, payouts and webhooks, and a live account the moment you verify your email. Cards run on the live rail, so your first card is a real one with a small load. Cards people can use. Virtual Visa cards funded with USDT on TRON or BNB Smart Chain, usable in Apple Pay, Google Pay and Samsung Pay and anywhere Visa is accepted. Docs you can read first. A public reference, one text file for AI assistants and an MCP server your coding tool can query. Start on the developers page. #Questions people ask What is a crypto card API? A set of HTTP endpoints your backend calls to issue and manage debit cards funded with crypto instead of a bank balance. It covers the cardholder, the card, loads, security codes, events and closing. Which crypto card API is best? The one that passes all seven questions for your product, from white label and public fees to safe retries and a sandbox that matches production. How much does a crypto card API cost? The usual fees are for issuing a card, for each load and for closing a card. Some providers add a setup fee or a monthly minimum. Cryptoinfra does not, and its current prices are on the pricing page. Can I test a crypto card API before going live? Partly, and it depends on the provider. Cryptoinfra's free sandbox runs the same API on test money for deposits, payouts and webhooks. Card calls need the live card rail, so the first card you issue is a real one. Make it your own, with a small load. #Try it The docs and the prices are public and the sandbox is free, so you do not have to take our word for any line on this page. Create your free account, build against the sandbox, then issue your first card to yourself and check all seven answers. Then read how to launch a crypto card programme for what comes next. --- ## Custodial vs Non-Custodial Wallets: Which Fits Your Business? URL: https://cryptoinfra.net/blog/custodial-vs-non-custodial-wallets-for-businesses Published: 2026-11-02 A seller on your marketplace writes to support: "I lost my phone. Is my money gone?" Your answer was decided long before that message arrived. It was decided the day you chose who holds the private key to that seller's wallet. If the seller holds it, the honest answer is often yes. If a provider holds it, the seller signs in again and the balance is still there. This guide follows that one marketplace through both wallet models, and ends with a short way to choose. In shortEvery wallet comes down to who holds the private key: the user (non-custodial) or a provider (custodial). Non-custodial fits when the user's own control is the product. Custodial fits when crypto is one feature inside a bigger product. Custodial lets you show balances, add your own fee and help with a stuck payment. Non-custodial mostly does not. Custodial is not blind trust: ask the provider exactly how the keys are kept. #What is the difference, in one minute? A private key is what signs a payment. Whoever holds it can move the money, and nobody else can. So the whole comparison comes down to one question: where does the key live? In a non-custodial wallet, the key stays with the user. They write down a seed phrase, usually a list of words, and their app signs each payment on their own device. Your business never touches the key. In a custodial wallet, a provider keeps the key. The user sees an address and a balance, and asks for a payment. The provider checks the request, signs it and sends it to the blockchain. Neither model is better everywhere. They solve different problems for different products. #What changes in your product day to day? Go back to the marketplace. Sellers earn USDT, lose phones and write to support. Here is how seven everyday moments look under each model. One marketplace, two wallet modelsNon-custodialCustodialWho can move the moneyOnly the sellerThe provider, when your app asksA seller loses the phone or seed phraseThe money is usually gone for goodThey sign in again and the balance is still thereShowing balances and history in your appOnly by reading the blockchain yourselfFrom one APIAdding your own fee to a payoutHard, because the seller signs the paymentIt is part of the payout requestHelping with a stuck paymentVery littleEvery payment has a record and a statusWhat a seller must learnSeed phrases, network fees and gas tokensHow to sign inTime to launchLong, because you build the wallet appShort, because you call an API Read it one row at a time, and ask which answer your support team could live with. #When is non-custodial the right choice? Non-custodial makes sense when the user's control is the product. Think of a wallet app for people who already hold crypto. They want nobody between them and their coins, and they are comfortable keeping a seed phrase safe. It also fits when your business must never be able to move user money, for legal or trust reasons, and you have the team to build and maintain a secure app on every platform your users have. The cost is real, though. You cannot reverse a mistake. You cannot recover a lost key. And every support ticket about a missing payment ends the same way: "we can't see or change that." #When is custodial the right choice? Custodial makes sense when crypto is a feature inside a bigger product. Our marketplace, paying its sellers in USDT, is one example. Here are others: a freelancer or creator platform with payouts; a game or app that keeps a balance for each player; a remittance or payroll service; an online store that accepts stablecoins. In all of these, users want the money to arrive and to be able to send it on. They do not want to learn about private keys. And you need to see every payment, add your own fee and help when something goes wrong. Still unsure? Ask three questions. Do your users want to hold their own keys, and know how? Then non-custodial fits. Do you need to see payments, add a fee or help with support? Then custodial fits. Do you want to launch in weeks, not months? Then a custodial wallet API is the shorter road. Most businesses that add crypto to an existing product land on custodial. Their users came for the product, not for key management. #What should you ask a custodial provider? Custodial does not mean "trust us and hope". The provider takes on the job of keeping the keys safe, so check how they do it. Seven questions to ask before you chooseWhere do the signing keys live? Apart from the servers your app talks to. If an API server can sign a payment, one bug can drain wallets. How are addresses made? From watch-only keys, which can create an address but never spend from it. Are the books checked against the blockchain? Balances in a database can drift. The provider should compare them often and alert on any gap. Can a retried request pay twice? A payout should take an idempotency key, so a repeat returns the first payout, not a second one. How is the dashboard protected? A password alone is not enough. Look for an authenticator code on every change. Can you test without real money? A sandbox with the same API saves you from learning on live funds. Does it stay under your brand? Your users should see your name, not the provider's. On Cryptoinfra, signing keys never live on the API servers, addresses come from watch-only keys, balances are matched with the blockchain every few minutes, and every dashboard change needs an authenticator code. The security page explains each part. #How does a custodial wallet work, step by step? Here is the path one seller takes with a custodial wallet API. One seller, from sign-up to payout01Seller signs upYour app creates them on the API with your own user id Address is issuedA permanent deposit address that never changes Deposit is creditedThe transfer is confirmed, the balance goes up and your server gets a signed webhook 04Seller withdrawsYour app asks for a fee quote, shows it, then sends the payout with an idempotency key Payout goes on-chainYou read its status until it is confirmed and show the transaction The seller never sees a seed phrase. Your team never handles a private key. You see every step. Each customer gets one permanent deposit address per network: TRON, BNB Smart Chain, Solana, Bitcoin and TON. On TRON, the same address receives both USDT and TRX, so a seller can save it once and reuse it. The wallets page and the payouts page show both halves in more detail. To see what "confirmed" means, read how crypto deposits are confirmed on TRON. #Which mistakes cost the most? Most wallet trouble starts with one of these five decisions. Choosing non-custodial for a mass-market appUsers lose seed phrases and blame you. Use custodial when crypto is a feature, not the product. Choosing custodial without asking about keysOne weak server can put every wallet at risk. Ask where the signing keys live, and get the answer in writing. Keeping your own copy of balances as the truthYour numbers drift away from the chain. Read balances from the API instead. Skipping two-factor on the dashboardOne stolen password then controls payouts. Require an authenticator code for every team member. Going live without a sandbox runThe first real error then happens on real money. Test deposits, payouts and errors first. Only the first mistake is about the model. The other four are about how well it is run, so hold your provider to the seven questions above. #Questions people ask What is the difference between a custodial and a non-custodial wallet? In a custodial wallet a provider holds the private key and signs payments when your app asks. In a non-custodial wallet the user holds the key, usually as a seed phrase. Is a custodial wallet safe for a business? It depends on how the provider keeps the keys. Ask where the signing keys live, how addresses are made and how balances are checked against the blockchain. Can a lost seed phrase be recovered? Usually not. Nobody else holds the key, so the money is usually gone for good. A custodial wallet has no seed phrase to lose: the user signs in again. Which wallet type is better for a marketplace or a payout platform? Usually custodial. Users want the money to arrive, and you need to see every payment, add your own fee and help when something goes wrong. #Try it Decide today what you will tell the seller with the lost phone. Then run the whole flow in the Cryptoinfra sandbox — create a customer, receive a deposit, send a payout — before any real money moves. Start free, or read the white-label crypto wallet API guide first. It walks through every call. --- ## How to Test Crypto Payments in a Sandbox Before Going Live URL: https://cryptoinfra.net/blog/test-crypto-payments-in-sandbox Published: 2026-11-01 Your app is about to send its first real payout. If the code sends it to the wrong address, or sends it twice, there is no bank to call and no "reverse" button. On a blockchain, a mistake is final. So the first real payment your app makes should not be its first payment at all. A sandbox is a copy of the platform that runs on fake money: a separate key, a separate database and the same API. You can break things there as often as you like, and nobody loses anything. This guide takes one test customer from a fake deposit to a finished payout, then breaks the flow on purpose. In shortA sandbox is the same API running on fake money. A mistake there costs nothing; on a blockchain it is final. Get a key with one request, fund a test user from the faucet, and send a payout through every status. Then test what "never happens": a deposit that is too small, a repeated event, a reused key, a payout larger than the balance. The sandbox does not cover cards, real network fees or your own hosting. Check those live, starting small. Going live should mean changing two settings, the key and the base URL, and nothing in your code. #What should a good sandbox give you? Not every test mode is equal. Some only return canned answers, so your code passes in testing and then meets a new error on day one of real traffic. A useful sandbox should: run the same code paths as production, not a mock; let you create money on demand, because you cannot send real coins to it; answer with the same errors production would; move your test payouts through the same statuses as real ones; keep test money fully separate from real balances. The Cryptoinfra sandbox is built this way. A simulated deposit is a real deposit record pushed through the real crediting logic, with your fees and the deposit minimum applied. A sandbox payout walks the real state machine, from queued to confirmed, just without a chain underneath. The test data lives in its own database, and the live ledger never sees it. Sandbox and live, side by sideSandboxLiveThe API and its errorsThe sameThe sameMoneyFake, created by the faucetReal coins on a blockchainDepositsSimulated, through the real crediting logicSent on-chain by your customerPayoutsThe real statuses, with no chain underneathThe real statuses, on-chainNetwork fees and confirmation timesNot part of the testReal, read from the quoteDataIts own databaseThe live ledger #Step 1: Get a sandbox key You can get a sandbox key with one request, no signup needed: bashCopyCopiedPress ⌘Ccurl -sX POST https://merchant.cryptoinfra.build/sandbox/v1/signup-key The response gives you an api_key that starts with ck_sandbox_, and the base_url to use. Put both in environment variables, never in your code: bashCopyCopiedPress ⌘Cexport CRYPTOINFRA_KEY=ck_sandbox_your_key export API=https://merchant.cryptoinfra.build/sandbox Going live later means changing these two values and nothing else. If your code needs a code change to go live, something is hard-coded that should not be. #Step 2: Test your webhook handler on its own The sandbox delivers webhooks, so you can watch them arrive. It still pays to test your handler by itself first. Pick a test secret. Write a small script that takes a sample event body, signs the exact bytes with HMAC-SHA256 and that secret, and posts it to your handler with the x-cryptoinfra-event and x-cryptoinfra-signature headers. Now you can send a good event, a repeated event and a forged one whenever you like. Our guide to receiving crypto webhooks safely explains the signature check step by step. While you test against the sandbox, let your app learn results by reading the API, as the next steps do. That is the habit you want in production too. #Step 3: Create a user and fund them Create a user with the id they have in your own system. They get one permanent deposit address per network. You cannot send real coins to a sandbox address, so the sandbox has a faucet instead: bashCopyCopiedPress ⌘Ccurl -sX POST $API/v1/simulate/deposit \ -H "Authorization: Bearer $CRYPTOINFRA_KEY" \ -H "Content-Type: application/json" \ -d '{"external_user_id":"","asset_id":"usdt_trc20","amount":""}' This credits the user through the same logic a real transfer goes through. Read GET /v1/users/{id}/balances to see it land. Try it with every asset you plan to offer, because each asset has its own decimals and its own minimum. #Step 4: Send a payout and watch it finish Ask for a fee quote, then send a withdrawal with an idempotency_key. You get 202 and the status queued. A few seconds later the sandbox moves it through signing and broadcast to confirmed. Read the withdrawal with GET /v1/withdrawals/{id} until it is final. Get into the habit now: in production a webhook will tell you sooner, but the read is always the answer. The payouts page shows how statuses work end to end. If you sell through the payment gateway, the sandbox covers that too: POST /v1/simulate/payment with the payment's id pays it with fake money, and the payment events reach your endpoint as in production. #Step 5: Break it on purpose Most bugs live in the cases that "never happen". The sandbox is where you make them happen on purpose. Work through this plan before you go live. The test plan, and what you should seeSimulate a normal depositStatus credited, and the balance goes up. Simulate a deposit below the minimumStatus ignored_dust. No credit, no surprise. Post the same signed event to your handler twiceIt credits only once. Post an event with a wrong signatureYour handler rejects it. Send a payout, then repeat it with the same keyOnly one payout exists. Repeat the key with a different amount409 idempotency_conflict. Send a payout larger than the balance409 insufficient_balance, nothing queued. Send to an invalid address400 invalid_address, nothing queued. Kill your payout worker mid-request, then restart itIt reuses the stored key. One payout. The dust case matters more than it looks. A deposit below the asset's minimum is not credited, in the sandbox and in production alike. If your app shows "payment received" from its own records before the platform credits it, this is where you will find out. The tests that reuse a key are explained in our guide to idempotency keys. #What does the sandbox not cover? Be honest about the gaps, so they do not surprise you later: Cards. The sandbox has no card rail. Card calls answer 503 cards_disabled. Use it to check that your code handles that error cleanly, then test card flows carefully with small real loads. The cards page explains how loads work. The real network. Sandbox payouts confirm without a blockchain underneath, so real network fees and real confirmation times are not part of the test. Always read the fee from the quote, never from a number you saw in testing. Your live endpoint. Register your live webhook URL and check that the first live event reaches it and passes the signature check with the live secret. Your own hosting. A sandbox cannot tell you if your production server, firewall or DNS is set up right. #How do you go live? When the whole test plan passes, going live is a short list. Going liveSwap the key and the base URL in your environment, not in your code. Register your production webhook endpoint and store its new secret. Confirm your handler verifies signatures with the live secret. Make one small real deposit and one small real payout, and read both back. Set your own fee, if you charge one, and check it on a real quote. Live numbers are on the pricing page. #Mistakes to avoid These five slip through even careful testing. Testing only the happy pathThe first real error breaks production. Run the full test plan above. Hard-coding the sandbox URLLive traffic goes to the sandbox. Read the URL from the environment. Skipping signature checks "for now"They never get added. Verify signatures from day one. Keeping your test signing secretLive events fail to verify. Use the secret your live endpoint gets. Copying a fee from a test runUsers see a wrong number. Always show the live quote. #Questions people ask What is a crypto sandbox? It is a copy of a payment platform that runs on fake money. The API is the same as the live one, so you can test deposits, payouts and errors without risking real coins. Can I test crypto payments without real money? Yes. In the Cryptoinfra sandbox a faucet call creates a deposit for a test user, and payouts confirm without a blockchain underneath. Do I need an account to get a sandbox key? No. One request to the sandbox returns a key that starts with ck_sandbox_, and the base URL to use. Is the sandbox the same as production? The API, the errors and the payout statuses are the same. Cards, real network fees and real confirmation times are not part of it. What changes when I go live? Two settings: the API key and the base URL. You also register your live webhook endpoint and use the new secret it gets. #Try it Get a key, fund a user from the faucet and push a payout through every status. Then break things on purpose: repeat events, reuse keys, send too little and too much. The quickstart in our docs has every call in order, and the developer overview shows the rest of the API. When your tests pass, sign up free for your live key. --- ## Idempotency Keys: How a Crypto Payout Never Pays Twice URL: https://cryptoinfra.net/blog/idempotency-keys-crypto-payouts Published: 2026-10-31 Your app pays a freelancer. The request leaves your server, and then the connection drops. No answer comes back. Did the payout happen or not? Guess "no" and send it again, and you may pay her twice. On a blockchain that is final: an on-chain transfer has no "undo" button. Guess "yes" and do nothing, and she may never be paid. An idempotency key removes the guess. It is a name you give to one payout, so that asking twice still pays once. This guide follows a single payout — row 8814 in your database — through a timeout, a retry and a safe ending. In shortAn idempotency key is a name you give to one movement of money. Send it with the request, and a repeat can never create a second payout. Create the key once, save it in your own database before the first call, and reuse it on every retry. After a timeout, send the same request again with the same key, or look the key up. Never retry with a new key. A 409 idempotency_conflict means two different payouts share one key. That is a bug to fix, not an error to retry. #What does an idempotency key do? A request is idempotent when sending it once and sending it ten times have the same effect. Reading a balance is like that by nature. Sending money is not — unless the API gives you a way to say "this is the same payout as before". That is the key's job. It is a string you create and send with the request. The API remembers it. If the same key arrives again, the API does not create a new payout. It returns the one that already exists. A payout that times out, and still pays once01You save the payoutRow 8814 in your database, with the key payout-8814 02First requestIt reaches the API, but the connection drops before the answer One payout is createdThe key is stored with it 04You retry with the same keyThe identical request goes out again The same payout comes backNothing new is sent, and you read its status The retry is safe whether the first request landed or not. #Which requests need a key? On Cryptoinfra every request that moves money accepts an idempotency_key in the request body. It is required on: withdrawals, which are on-chain payouts; card issuing and card top-ups. It is optional, but strongly recommended on swap and exchange orders. Treat it as required there too: a repeated swap is still money moving twice. Keys belong to your merchant account, so they can never clash with another merchant's keys. They also do not expire, which means a retry days later is still safe. #Step 1: Create the key before the first attempt The most important rule: one key per intended movement of money, not per HTTP attempt. The order that keeps a payout safeWrite the payout rowYour app decides to pay someone and saves a row in your own database. Create the keyDo it right then, and save it in that same row. Call the APIOnly now does the request go out, carrying the key. Retry from the rowEvery retry of that payout reads the key from the row and sends it again. A random UUID is a fine default. A key built from your own record id is even better — payout-8814, or card-topup-2291. It survives a crash: if your process restarts in the middle of a payout, it can rebuild the exact same key from the row, instead of making a new random one and paying again. #Step 2: Know what a repeat returns When you send the same key with the same details, the API returns the original record. No second payout, no second hold on the balance, no second order. What the API does with a keyWhat happensPayouts sentA new keyA new payout is createdOneSame key, same detailsThe existing payout is returnedStill oneSame key, different detailsRefused with 409 idempotency_conflictStill oneA fresh key on a retryA second payout is created. This is the bugTwo The record comes back as it is now. If the payout has already confirmed on-chain, the repeat shows it as confirmed. That makes a repeat a handy status check as well. #What does a key conflict mean? "Same details" means the fields that describe the movement. For a withdrawal that is the user, the asset, the address and the amount. The quoted network fee is not compared, because it can change between honest retries of one payout. If the details differ, the API will not guess what you meant. It refuses with 409 idempotency_conflict. It never quietly returns the old payout for a new request, and it never quietly creates a second one. When you see this error, do not retry. It means two different payouts got the same key. The usual causes: the key is built from something that is not unique, such as the user id alone; the key is built from the date, and the same user is paid twice in one day; a test script reuses a hard-coded key. #What should you do after a timeout? This is the case from the top of the page. The request timed out, and you do not know if the payout exists. There are two safe moves, and they always agree. Send it again with the same key. If the first try never landed, this one creates the payout. If it did land, you get the existing payout back. One call, one answer. Look the key up. GET /v1/withdrawals?idempotency_key=… returns the withdrawal for that key, or 404 if none was ever created. Use this when you want to know the state before you write anything. Never retry with a new key: that is exactly how customers get paid twice. And never treat a timeout as a failure and refund, or the customer may be refunded and also paid. #Which errors are safe to retry? Here is a simple policy you can copy into your payout worker. A retry policy that worksRetry?With which keyTimeout, dropped connection, 500, 502, 504Yes, with backoffThe same key, always429 too many requestsYes, after waitingThe same key503 service unavailableYes, later, unchangedThe same key409 idempotency_conflictNo. Fix key generation—Other 409, such as low balanceOnly after the state changesThe same key400, 401, 403No. Fix the request— When you finally stop retrying, check the payout with the key lookup or the withdrawal read before you tell your customer or your support team anything final. #Why is a pending card order not a failure? Card money calls return 202 Accepted. Our ledger has moved, but the card programme has not confirmed yet. The final answer comes later, through a card.topup webhook or our reconciler. Do not read 202 as a failure, and do not "fix" it by sending a new request. Refund your user only on a clear failure: a 409 provider_rejected at request time, or an order whose status becomes failed. #How do you stop duplicates on your own side? The key protects the API call. Your own system needs the same habit. A payout job can run twice after a deploy. A user can double-click "Withdraw". Two workers can pick up the same row. Put a unique constraint on the key column in your payouts table. Have the "Withdraw" button create the payout row once, and disable it while it waits. Let only one worker claim a payout row at a time. When a webhook arrives, deduplicate it as well. Our guide to receiving crypto webhooks safely shows how. #How do you test it before real money moves? The sandbox behaves like production, so you can rehearse every case above without risk. How to test crypto payments in a sandbox shows how to get a key. Five tests for your payout codeSend a payout, then send it again with the same key. Only one exists. Send the same key with a different amount. You get 409 idempotency_conflict. Kill your worker in the middle of a payout and restart it. It reuses the stored key. Look up a key that was never used. You get 404. Double-click your "Withdraw" button. One payout row, one API call. #Questions people ask What is an idempotency key? It is a unique string you send with a request that moves money. If the same key arrives again, the API returns the payout it already created, not a second one. How do I generate an idempotency key? A random UUID works. A key built from your own record id, such as payout-8814, is better, because your code can rebuild it after a crash. Can a crypto payout be reversed if it was sent twice? No. An on-chain transfer is final, so the only protection is to prevent the second payout. What should I do when a payout request times out? Send the same request again with the same key, or look the key up with GET /v1/withdrawals?idempotency_key=…. Never retry with a new key. #Try it Create the key once, save it before the first call, reuse it on every retry, and look it up when you are unsure. Then a dropped connection is a small delay, not a double payout. The full rules are in the idempotency docs, and the developer overview covers the rest of the API. Sign up free, then send a payout twice in the sandbox. Only one will exist. --- ## Crypto Webhooks: How to Receive Payment Events Safely URL: https://cryptoinfra.net/blog/crypto-webhooks-receive-payment-events-safely Published: 2026-10-30 A message reaches your server: deposit credited, customer 10482. Your code adds the money to her account. There is one problem. She never paid. Someone found the address of your server and wrote that message themselves. That message is a webhook: a note our platform sends your server the moment money moves. It is how your app hears about a payment without asking every few seconds. It is also a door into your system, and three bad things can come through it — a fake message, the same message twice, and no message at all while your server was down. This guide follows one deposit from the blockchain to your database, and shows how to stop all three. In shortA webhook is a signed message we send your server when money moves: a deposit is credited, a payout is confirmed, a card is loaded. Anyone on the internet can post to your webhook address. Check the signature on every message before you believe it. The same event can arrive more than once. Remember what you have handled, and make crediting safe to repeat. A webhook is a hint, not the record. Read the API before you credit, refund or tell anyone that money moved. #What is a webhook, and what is it not? Think of a webhook as a doorbell. It tells you someone may be at the door. It does not prove who is there, and it does not open the door for you. On Cryptoinfra every delivery is an HTTPS POST to the endpoint you registered. It carries two headers: x-cryptoinfra-event — the event type, for example deposit.credited; x-cryptoinfra-signature — a hex HMAC-SHA256 of the exact request body, made with your endpoint's secret. Delivery is at-least-once. If your server does not answer with a success code, we send the event again, so the same event can reach you more than once. One deposit, from the blockchain to your database01Customer paysThe transfer confirms on the blockchain We credit and notifyThe balance goes up and a signed deposit.credited is sent to your server 03You verify and queueCheck the signature, save the event, answer with a success code 04You confirm and creditA worker reads the balance from the API, then updates your own records The last two steps are yours. #Which events will you receive? Six events carry most of the money news. The main money eventsAboutFires whendeposit.creditedDepositsA deposit has enough confirmations and the user's balance went upwithdrawal.confirmedPayoutsAn on-chain payout is confirmedwithdrawal.failedPayoutsA payout could not completecard.topupCardsA card load finishedcard.statusCardsA card changed statuscard.transactionCardsA card was used to pay The full list, with a payload example for each, is in the webhooks docs. One thing to know early: swaps emit no webhook. If you offer swaps, poll the swap order until it reaches a final status. #Step 1: Register one clean endpoint Create the endpoint from the dashboard or the developer API. Four rules save trouble later: Use HTTPS and a public hostname. Register the final URL. Redirects are not followed, and a redirect counts as a failed delivery. Use a path that exists only for this, like /webhooks/cryptoinfra. Save the secret the moment you see it. It is shown once and never again. Treat that secret like a password. Keep it in your secrets store, not in your code or your git history. If it ever leaks, regenerate it. The old secret stops working at once, so do it at a time you can watch. #Step 2: Check the signature before anything else This is the step that stops the fake message from the top of this page. Without it, anyone who learns your URL can send a fake deposit.credited and be credited for money they never sent. Verifying one webhookRead the raw bytesTake the request body exactly as it arrived, before any JSON parser touches it. Compute the HMACHMAC-SHA256 of those bytes, keyed with your endpoint secret, written as hex. Compare in constant timeCheck your result against the x-cryptoinfra-signature header. A normal string compare leaks timing that can help an attacker. Reject on any doubtIf the two differ, or the header is missing, refuse the request and stop. The most common bug is the first step. Many web frameworks parse JSON for you. If you sign the parsed object turned back into text, the bytes change — key order, spaces, number format — and the signature never matches. Developers then "fix" this by turning the check off. Do not do that. Configure the route to hand you the raw body instead. The docs have ready examples for Node.js and Python. #Step 3: Answer fast, do the work later Each delivery waits only a short time for your answer. If your handler is slow — it calls another service, sends an email, writes to many tables — the delivery is marked failed and sent again. Now you process the same event twice. The safe pattern has four moves: verify the signature, put the event on a queue or into a jobs table, reply with a 2xx code right away, and let a background worker do the real work. Your answer only means "I received it". It does not mean "I finished handling it". #Step 4: Expect every event twice Because delivery is at-least-once, you will see duplicates. A timeout that actually succeeded, a brief network problem or an error on your side all cause a retry. There is no separate delivery id. Deduplicate on the pair of event type and entity id — the deposit id, withdrawal id, card id or order id in the payload. Keep a small table with that pair as its primary key. When an event arrives, try to insert it. If the row already exists, you have handled it before: reply with success and stop. One exception: a status event such as card.status fires once per change, so one card can send many. Key those on event type, entity id and the new status. Then make the work itself safe to repeat. Crediting an order should first ask "is this order already paid?". Two layers of protection beat one. For money going out, an idempotency key does the same job. #Step 5: Confirm with the API before money moves Even a valid, signed webhook only says that something may have changed. Before you credit a customer, refund someone or tell support that money moved, read the record from the API: the user balances read for deposits; the withdrawal read for payouts; the card order read for card loads; the swap order read for swaps. A webhook tells you to look. The API tells you what happened. This matters most after your server has been down for a long time. Retries do stop after a while, and a webhook that never arrived must not leave money stuck in your system. Run a regular sweep that checks every record that is not yet final against the API, whether a webhook came or not. #How do you test the handler before going live? Do not wait for real money. Use the sandbox and the test button for your endpoint. It sends a signed test event through the real delivery system, so it checks your actual signature code, not a simulation. You can pick the event type you want to rehearse. Rehearse five cases: a valid event is accepted and queued, a changed body is rejected, a missing signature header is rejected, the same event sent twice is handled once, and a slow worker does not slow down the reply. How to test crypto payments in a sandbox has the wider plan. Before the first live event, walk through this list. The safe webhook checklistThe endpoint is HTTPS, public and the final URL, with no redirects. The secret is stored like a credential and can be rotated. The raw body is verified with HMAC-SHA256 in constant time. A missing or wrong signature is rejected, never "logged and processed". The handler replies with a 2xx quickly and queues the work. Events are deduplicated on event type and entity id. Crediting and refunding are safe to repeat on their own. Money decisions are confirmed with an API read. A sweep runs over the records that are not yet final. Swaps are polled, because they send no webhook. #Questions people ask What is a webhook in crypto payments? It is a message the payment platform sends your server when money moves, such as a deposit being credited or a payout being confirmed. Your app does not have to keep asking for news. How do I verify a webhook signature? Compute HMAC-SHA256 over the raw request body with your endpoint secret, and compare it in constant time with the x-cryptoinfra-signature header. Reject the request if they differ. Why did I receive the same webhook twice? Delivery is at-least-once. If your answer was slow, failed or was lost, the event is sent again. Deduplicate on event type and entity id, so the second copy changes nothing. What happens if my server is down when a webhook is sent? The delivery is retried for a while, then the retries stop. That is why you also run a sweep that checks every unfinished record against the API. #Try it A safe handler checks the signature on the raw body, answers fast, ignores duplicates and confirms money decisions against the API. That makes webhooks a live feed you can trust for your wallets and payouts. Sign up free and send your first signed test event from the sandbox today. The developer overview shows the rest of the API. --- ## How Crypto Deposits Are Confirmed on TRON (Step by Step) URL: https://cryptoinfra.net/blog/how-crypto-deposits-are-confirmed-on-tron Published: 2026-10-29 A customer says, "I sent it." Your dashboard shows nothing. A few seconds later they send a screenshot, and then they ask again. The payment is real, but it is not final yet. Between the customer pressing send and your balance going up, the TRON network and your platform run several checks. This guide follows one USDT payment through each of them, so you can answer "where is my money?" with confidence. In short"Sent" is only a request. A payment counts once it is in a block, it really succeeded, and enough new blocks sit on top of it. On TRON the wait is short: often around a minute after the payment lands in a block. A failed or dropped transfer is never credited, and a transfer below the minimum is set aside as dust. Your signal to act is the signed deposit.credited webhook, never a screenshot or a transaction ID. #Why is "sent" not the same as "paid"? When a customer sends USDT or TRX, their wallet signs a transaction and broadcasts it to the network. At that point it is only a request. It is not yet part of the blockchain. Three things still have to happen. A block producer has to put the transaction into a block. The transaction has to actually succeed when it runs. And enough new blocks have to be added on top, so the payment cannot be undone. Only then is it safe to treat the money as yours. Crediting a balance earlier is how businesses get burned. One USDT payment, from send to credited01Customer presses sendThe wallet signs a transfer of 100 USDT and broadcasts it 02It lands in a blockAnyone can look it up by its transaction ID The result is checkedA transfer that failed on-chain is never credited Confirmations pile upNew blocks are added on top Balance is creditedYour server gets a signed webhook The customer's wallet often says "success" at the second step. Your balance moves at the fifth. #Step 1: The payment lands in a block TRON makes a new block every few seconds, and each block holds a batch of transactions. Once a transaction is inside a block, anyone can look it up by its transaction hash, often called the TXID, on a TRON block explorer. This is when the customer's wallet often shows "success". It is good news, but it is the start of the process, not the end. On Cryptoinfra, a scanner reads every new block and looks for transfers into the addresses issued to your users, for both USDT and TRX. When it finds one, it records a deposit for that user and starts tracking it. You do not run a node, and you do not poll the chain yourself. #Step 2: The transfer must really succeed This step surprises many people. A transaction can be in a block and still fail. USDT on TRON is a TRC20 token, so moving it means calling a smart contract. If that call runs out of resources or is rejected, the transaction is recorded on-chain as reverted. The sender may still pay a network cost, but no tokens moved. A system that only asks "is the TXID in a block?" would credit this empty payment. A careful one checks the result. On Cryptoinfra, a reverted transfer is marked as orphaned and never credited. What is TRC20? explains the smart-contract side. #Step 3: Confirmations pile up Each new block added after the one that holds your transaction is one confirmation. More confirmations mean the payment is buried deeper, and reversing it becomes practically impossible. Why wait at all? In rare cases the network briefly disagrees about its newest blocks. When that settles, a very recent block can be replaced, and a transaction in it can disappear. Waiting protects you from crediting a payment that later vanishes. Cryptoinfra waits for a fixed number of confirmations on TRON before it credits anything. The exact number is shown live on the pricing page. TRON blocks come quickly, so the wait is usually short — often around a minute from the moment the payment lands in a block. A transaction that is seen and then drops out of the chain, or is never found again after a long time, is marked orphaned and never credited. #Step 4: The balance moves and a webhook fires When the confirmation count is reached, three things happen together: the user's balance goes up in a double-entry ledger; the deposit moves to the credited status; your server receives a signed deposit.credited webhook. That webhook is your signal to act: mark the order paid, unlock the feature, send the receipt. Check its signature first, and deduplicate it, because a webhook can arrive more than once if your server was slow to answer. Receiving crypto webhooks safely shows how. #What does each deposit status mean? These are the four statuses your support team will meet. The four deposit statusesWhat it meansIs the money credited?confirmingIn a block, counting confirmationsNot yetcreditedEnough confirmations. The balance moved and the webhook was sentYesorphanedReverted on-chain, or dropped from the chainNeverignored_dustBelow the minimum deposit for that tokenNever The last row is worth knowing. Very small transfers are often spam, sent to many addresses at once. A deposit below the token's minimum is recorded as dust and not credited. The minimums are on the pricing page. There is no deposit fee on TRON: a deposit at or above the minimum is credited in full, less only your own fee if you have chosen to set one. #What should your customer see while they wait? Do not show "Paid" when the customer presses send. Show something honest, such as "Payment detected — confirming", and switch to "Paid" only when the deposit.credited webhook arrives. Customers stay calm when they can see progress. Never credit an account because a customer sent a screenshot or a TXID. A screenshot can be faked, and a TXID can point to a reverted or wrong-token transfer. The webhook is the one source of truth. #How do you credit the right balance and the right order? Two details trip up new integrations. The token. One TRON address receives both TRX and USDT. The webhook names the token, so credit the right balance for each and never assume every deposit is USDT. The wallets page explains how one permanent address per user works. The order. A user's address stays the same forever, so the address alone cannot tell you which order was paid. Keep your own record of what the user owes, and match the credited amount and time against it. If you sell single orders, the payment gateway gives you a hosted checkout priced in US dollars instead. #Before you go live: the deposit checklist Your screen shows "confirming" until the credited webhook arrives. Your webhook handler verifies the signature before it trusts the body. Your handler deduplicates on the event type and the deposit id. Your handler answers quickly with a success code and does the work afterwards. Each token is credited to its own balance. Your help page tells customers to pick TRON as the network when they send. Your support team knows how to look up a TXID on a block explorer. You have tested a full deposit flow in the sandbox. #Which mistakes credit the wrong money? Each of these five has a one-line fix. Crediting on "in a block"A reverted transfer gets treated as paid. Credit only on deposit.credited. Trusting screenshotsFake or wrong payments get through. Use the webhook, never the customer's word. No deduplicationThe same deposit is credited twice. Store the event type and the deposit id. A slow webhook handlerDeliveries time out and repeat. Reply fast and do the work in the background. Assuming USDT onlyA TRX deposit looks unpaid. Read the token from the webhook. #Questions people ask How long does a USDT TRC20 deposit take to confirm? TRON makes a new block every few seconds, so a deposit is often credited around a minute after the payment lands in a block. How many confirmations does a TRON deposit need? Each platform chooses its own number. Cryptoinfra waits for a fixed number, shown live on the pricing page. My wallet says "success" but the deposit is not credited. Why? "Success" usually means the transaction is in a block. It still has to gather confirmations, and it is credited only if the transfer really succeeded on-chain and is at or above the minimum deposit. Can I credit a customer from a transaction ID or a screenshot? No. A screenshot can be faked, and a transaction ID can point to a reverted or wrong-token transfer. Credit only on the signed deposit.credited webhook. #Try it Build the screen that answers "I sent it" before the customer asks. You can send your first test deposit in the Cryptoinfra sandbox today, with signed webhooks and one address per user under your own brand, and no node to run. Start free, or read the deposit address docs first. --- ## What Is TRC20? A Plain-English Guide for Businesses URL: https://cryptoinfra.net/blog/what-is-trc20-guide-for-businesses Published: 2026-10-28 Your customer wants to pay you in USDT. Their exchange shows a short list of networks: TRC20, BEP20 and a few more. They pick one and press send. Whether that money reaches you depends on that one choice. Most lost crypto payments start right there, with a network mix-up. Yet many business owners nod along at the word TRC20 without being sure what it means. This guide explains it in plain words: what TRC20 is, how a transfer really works, and what to check before you accept or send it. In shortTRC20 is not a coin and not a company. It is the standard that tokens on the TRON blockchain follow, so "USDT TRC20" simply means USDT on TRON. TRX is TRON's own coin. USDT is a TRC20 token. One TRON address, starting with a capital T, holds both. The same coin name exists on several networks that do not talk to each other, so always write the network next to the coin. Before you go live: validate addresses, credit only confirmed deposits, and keep each token as its own balance. #What does TRC20 actually mean? TRC20 is a technical standard for tokens that live on the TRON blockchain. That is all. It is a set of rules that a token follows, so that every wallet, exchange and app on TRON knows how to read its balance and how to move it. Think of a plug shape. A device with the right plug works in any matching socket. A token built to the TRC20 standard works in any TRON wallet that supports TRC20. So when the exchange offers your customer "USDT TRC20", it is offering to send USDT over the TRON network. TRC20 names the road, not the cargo. #How is TRX different from a TRC20 token? TRON has two kinds of money, and they behave differently. TRX is the coin the network itself runs on. USDT is a token that a smart contract created on top of it. TRON's coin and TRON's tokensTRXTRC20 tokens such as USDTWhat it isThe native coin of TRONA token created by a smart contract on TRONPriceMoves with the marketA stablecoin aims to stay at one US dollarHow a transfer worksA simple transfer between two accountsA call to the token's smart contractNetwork resources usedMostly bandwidthBandwidth and energyHeld on the same addressYesYes The last row matters most for a business. A TRON address starts with a capital T, and that one address can hold TRX and USDT at the same time. You do not need a separate address for each token. #What happens when someone sends USDT TRC20? When your customer "sends USDT TRC20", no coin physically travels between wallets. A smart contract updates its records. One USDT transfer on TRON01Wallet asks the contractTo move 100 USDT from the sender's address to the receiver's 02Contract checksDoes the sender really have enough USDT? 03Balances changeThe sender's goes down and the receiver's goes up, in the contract's own records 04Network records itThe transfer gets a unique transaction ID and is added to a block 05More blocks followEach new block makes the payment harder to reverse Because a smart contract does the work, a TRC20 transfer needs energy, a TRON resource that pays for running contracts. If the sender has no energy, the network burns TRX to cover it. That is why sending USDT costs more than sending TRX, and why a wallet that has never held USDT costs more to send to. Our guide to USDT TRC20 payout fees explains energy and bandwidth in detail. #Why must the network be written next to the coin? USDT exists on many blockchains, not only TRON. The same name can mean a token on TRON (TRC20), on BNB Smart Chain (BEP20) or on another network. These are different tokens on different chains. They do not talk to each other. Now go back to your customer and that list of networks. If they send USDT on another network while your screen showed a TRON address, the payment does not arrive in the TRON wallet. Sometimes the funds can be recovered with effort. Often they cannot. This is why every good crypto product writes the network next to the coin: "USDT (TRC20)" or "USDT on TRON" — clear. "USDT" alone — confusing, and a source of lost funds. Cryptoinfra itself supports USDT on TRON, BNB Smart Chain, Solana and TON, with a separate permanent address for each customer on each network. The more networks you offer, the more that label matters. #How do you recognise a TRON address? You can check a TRON address with your eyes before any software does. It: starts with a capital T; uses letters and numbers, mixing upper and lower case; has a built-in checksum, so a single wrong character makes it invalid. An address that starts with 0x belongs to a different kind of network, such as BNB Smart Chain. If a user pastes one into a TRON payout form, your app should stop them right away. On Cryptoinfra, payout requests are checked before they are sent. An address that is not a valid TRON address is refused, so money never leaves on a typo. The payouts page shows how payouts work. #What does TRC20 change in your product? Three everyday jobs touch it. Receiving payments. Give each customer one permanent TRON address. It receives TRX and USDT. When a deposit lands and is confirmed, your system gets a signed webhook that names the token and the amount. Your code should credit every token you support, not only USDT. The wallets page shows how branded deposit addresses work, and how crypto deposits are confirmed on TRON follows one payment block by block. Sending payouts. Payouts go on-chain to any TRON address. The network fee is always charged in the token you send, so a USDT payout pays its fee in USDT. Each payout carries an idempotency key, so a retry after a timeout never pays twice. Live prices are on the pricing page. Moving between TRX and USDT. Some users hold TRX but need USDT, or the other way round. Swaps between the two happen on-chain, by API. See the swap page. #Before you go live: the TRC20 checklist Use this list before you open TRC20 payments to real customers. Every place a coin is shown also shows the network: "USDT (TRON)". Deposit screens show a QR code and the address in text, with a copy button. Payout forms reject addresses that are not valid TRON addresses. Your webhook handler credits USDT and TRX, and ignores tokens you do not support instead of crashing. Your webhook handler checks the signature before it trusts any event. Balances are shown per token, never added into one "dollar" figure. Your help page tells users which exchanges they can withdraw from on TRON, and warns them to pick TRON as the network. You have tested deposits and payouts of each token in the sandbox. #Which TRC20 mistakes cost real money? Each of these five has a simple fix. Writing "USDT" without the networkCustomers send on the wrong chain. Always write "USDT (TRON)" or "USDT TRC20". Treating TRX and USDT as the same thingUsers expect a token balance to pay network costs. Explain that fees are charged in the token you send. Accepting any address formatA payout to a non-TRON address fails or is lost. Validate the address before sending. Crediting deposits before confirmationA payment is shown as paid too early. Credit only on the confirmed webhook. Ignoring TRX depositsA real payment looks unpaid. Handle every token you support. #Questions people ask Is TRC20 the same as USDT? No. TRC20 is the token standard on TRON, and USDT is one token that follows it. "USDT TRC20" means USDT on the TRON network. Is TRC20 the same as TRX? No. TRX is TRON's own coin. TRC20 tokens such as USDT are created by smart contracts on TRON. One TRON address holds both. What happens if I send USDT on the wrong network? It does not arrive in the TRON wallet. Sometimes the funds can be recovered with effort, but often they cannot, so check the network before you send. How do I know if an address is a TRC20 address? A TRON address starts with a capital T and has a built-in checksum. An address that starts with 0x belongs to a different network. Why does sending USDT TRC20 cost more than sending TRX? A USDT transfer runs a smart contract, which needs energy as well as bandwidth. If the sender has no energy, the network burns TRX to cover it. #Try it Name the network everywhere, validate every address, and you have already avoided most lost payments. You can try TRC20 wallets, payouts and swaps under your own brand in the Cryptoinfra sandbox, with every token, and no TRON node to run. Start free. --- ## USDT vs USDC: Which Stablecoin to Accept, on TRON and Beyond URL: https://cryptoinfra.net/blog/usdt-vs-usdc-on-tron Published: 2026-10-27 A customer writes to your support desk: "Can I pay in USDC?" A second customer has already sent USDC to a TRON address, and nothing has appeared in their balance. Both messages have the same cause. Your app said which coins it takes. The real question is which coin on which network. USDT and USDC are both dollar stablecoins, and most businesses do not need to pick a winner. They need to know where each one works. This guide follows two customers, Dana with USDT and Omar with USDC, from the deposit screen to the payout. In shortUSDT and USDC both aim to stay worth one US dollar. For a business, the real difference is which networks carry each coin and which one your customers already hold. On Cryptoinfra, USDT is accepted on TRON, BNB Smart Chain, Solana and TON. USDC is accepted on BNB Smart Chain and Solana. USDC is not accepted on TRON. Its own issuer is winding it down there, and USDC sent to a TRON address is not credited. You can offer both coins. Keep their balances apart, and write the network next to the coin on every screen. #What do USDT and USDC have in common? A stablecoin is a token whose value is tied to a normal currency, usually the US dollar. USDT and USDC are the two you will be asked about most. People use them because they move like crypto, fast, at any hour and across borders, but do not swing in price like TRX or bitcoin. For your business, that means a customer who pays today is still paying the same value tomorrow. On this point Dana's USDT and Omar's USDC are alike. If price stability is all you need, either coin does the job. #So what is the real difference? Two things, and both are practical. They are different tokens. Each has its own issuer, and one cannot be sent or counted as the other. A balance of USDT is not a balance of USDC, even if both read as dollars. They live on different networks. No stablecoin exists "in general". It exists on a network, and an address on one network cannot receive a transfer made on another. Our guide to TRC20 explains why the network name matters as much as the coin name. So the useful question is not "USDT or USDC?". It is "which coin, on which network, do my customers already hold?" #Where is each coin accepted? Where each stablecoin works on CryptoinfraUSDTUSDCTRONYesNoBNB Smart ChainYesYesSolanaYesYesTONYesNoLoads a virtual cardYesNo Each customer gets one permanent deposit address on each network. Dana holds USDT on TRON. She is the easy case: USDT is the most used token on that network, and her permanent TRON address receives USDT and TRX. Omar holds USDC. He can pay too, on BNB Smart Chain or on Solana, where USDC sits beside USDT. One more line in the table matters if you plan to offer cards. A virtual card is loaded with USDT, from your card programme's wallet on TRON or BNB Smart Chain. #What about USDC on TRON? On TRON, accept USDT. USDC is not accepted there, and here is why. USDC on TRON is being wound down by its own issuer: no new coins are issued on that network. When an issuer stops supporting a coin on a network, exchanges follow. Fewer of them accept deposits, and a customer who holds the coin may struggle to cash out. That risk lands on whoever holds it last, and that is often the business. So USDC sent on TRON is not credited. This is what happened to the second customer in the opening. Say it on your deposit screen, "USDT (TRON) only", so nobody sends a coin you cannot accept. "USDT" or "USDC" alone is half an answer. Your customer needs the coin and the network together: USDT (TRON), USDC (Solana). #Which one should your business accept? Start from your customers, not from the coins. Your customers are on TRON. Accept USDT there. It is the stablecoin they already have. Your customers ask for USDC. Give them a network where USDC is at home: BNB Smart Chain or Solana. You plan to issue cards. Loads are paid in USDT, so that is the coin your card programme needs. You have both kinds of customer. Offer both. Nothing forces you to choose one. #What happens when Omar pays in USDC? Each customer has one permanent address on each network. Omar does not need a new one for every payment. He needs the right one for his coin. Omar pays in USDC, on a network that takes it01Omar opens your deposit screenIt offers "USDC (Solana)" and shows his Solana address 02He sends 250 USDCFrom his own wallet, on Solana The deposit is creditedTo his USDC balance, kept apart from USDT Your server is toldA signed webhook says which coin arrived and how much Dana's path is the same, with "USDT (TRON)" on the screen. The wallets page shows how addresses and webhooks work. For what happens between "sent" and "credited", read how crypto deposits are confirmed on TRON. #What changes when you pay out? A payout names one coin on one network. You can send USDT and TRX to any TRON address with one API call, and USDC goes out on the networks that carry it. The network fee is always charged in the coin you send. Live payout prices are on the pricing page, and USDT TRC20 payout fees explained shows why a new or empty wallet costs more to send to. Before you pay anyone, ask which coin and network they want. A coin their exchange does not take can leave the money stuck or delayed. And if a customer holds one coin but needs another, they do not have to leave your app. Supported coins can be swapped by API, for example TRX and USDT. #How do you show two stablecoins without confusing anyone? Most lost deposits start on a screen that named a coin and forgot the network. Check these five things before you go live. Before you offer both coinsEvery screen writes the coin and the network together: "USDT (TRON)", "USDC (Solana)". Never just "USDT" or "USDC". Each coin has its own balance. Nothing is added into one "dollar" figure. A screen lists only what that address accepts. No USDC option beside a TRON address. The payout form asks the receiver for a coin and a network. You simulated a test deposit of every coin and network you offer in the sandbox, and your webhook handler credited each one. #Which mistakes cause the most trouble? Telling customers to send USDC on TRONThe deposit is not credited. Offer USDC on BNB Smart Chain or Solana. Hiding the network nameCustomers send on the wrong network, and may lose access to the funds. Write the network next to the coin. Adding both coins into one numberA customer tries to pay out more of a coin than they hold. Show one balance for each coin. Paying out a coin the receiver cannot takeThe money is stuck or delayed. Ask the receiver which coin and network they want. #Questions people ask Is USDT or USDC better for a business? Neither is better everywhere. Accept the coin your customers already hold, on a network where it is supported. You can also offer both. Can I accept USDC on TRON? Not on Cryptoinfra. USDC on TRON is being wound down by its issuer, so USDC sent to a TRON address is not credited. Accept USDC on BNB Smart Chain or Solana. Which networks can I accept USDT on? On Cryptoinfra, USDT is accepted on TRON (TRC20), BNB Smart Chain (BEP20), Solana and TON. What happens if a customer sends a stablecoin on the wrong network? They may lose access to the funds. That is why every deposit screen should name the coin and the network together. Is TRX a stablecoin? No. TRX is the native coin of TRON, and its price moves. You can accept it and pay it out next to USDT, and users can swap between TRX and USDT when they need to. #Try it Ready to give your customers wallets under your own brand? Sign up free and simulate a deposit of each coin in the sandbox today. --- ## How to Add a Crypto Card to Apple Pay and Google Pay URL: https://cryptoinfra.net/blog/crypto-card-apple-pay-google-pay Published: 2026-10-26 Your user has a virtual card in your app. It works on every website. Then she walks into a shop, and there is nothing to tap. She does not carry a card number around on paper. She carries a phone. Once the card sits in Apple Pay or Google Pay, she taps the phone at the terminal and pays with the stablecoins she loaded. This guide follows one user, Ana, from "Add card" to her first tap. It also shows the one screen you must build so she never gets stuck halfway. In shortA virtual crypto card becomes a tap-to-pay card once it is added to Apple Pay, Google Pay or Samsung Pay. The phone wallet asks for a verification code. With Cryptoinfra that code is not sent by SMS or email. It appears in your app. Your side is small: one signed webhook, one endpoint and one clear screen. The code can be read only once, so fetch it when the user is looking and never store it. #Why put a crypto card in a phone wallet? Our crypto cards are virtual Visa cards. A virtual card has a number, an expiry date and a security code, but nothing to put in a card reader. Online, that is all you need. In a shop, it is not. A phone wallet closes that gap. It turns the virtual card into something Ana can tap. For most users this is the moment the card stops feeling like a "crypto thing" and starts feeling like a normal payment card. More on that in virtual vs physical crypto cards. There is a second benefit: safety. When Ana pays by phone, the shop never sees her real card number. The phone sends a separate device number and a one-time code for each payment. If the shop's system is ever breached, her card details are not in it. #What does the user need before they start? Five things must be true before Ana opens her phone wallet. Before Ana taps "Add card"The card is active. A frozen card cannot spend, so unfreeze it first. The phone supports the wallet. Apple Pay needs an iPhone or Apple Watch. Google Pay needs an Android phone with tap-to-pay. The phone has a screen lock. Without a passcode, fingerprint or face unlock, the wallet refuses the card. The card programme supports phone wallets. Cards on our current programme can be added to Apple Pay, Google Pay and Samsung Pay. She can open your app. The verification code arrives there, not by text message. Wallet support belongs to the card programme, so check the cards guide when a new programme is added. #How does adding the card work? Ana does two things: she types her card details into the wallet, and she types one code. Everything else happens between the wallet, the card programme and your server. From "Add card" to the first tap01Ana adds the cardShe types the number, expiry date and security code into her phone wallet 02The wallet asks for proofThe card programme creates a one-time code We hold the codeYour server gets a signed webhook saying a code is waiting 04Your app shows the codeFetched only when Ana opens the screen 05Ana taps to payThe card is now in her phone Here is the same flow from your side of the screen. What you buildShow the card detailsYour app shows our embedded card page inside your card screen. Ana reads the number, expiry date and security code there. Receive the webhookYour server gets a signed card.wallet_otp event. It says a code is waiting. It does not contain the code. Fetch the codeYour app calls GET /v1/cards/{id}/otp with the user's id. The response has kind: "wallet_provisioning" and the code. Show it to the userAna reads the code in your app and types it into the wallet screen. The card appears in the wallet, ready to tap. The same endpoint also returns 3-D Secure codes for online checkouts, and the kind field tells you which is which. How 3-D Secure works on a crypto debit card covers the checkout side. #Where does the code NOT come from? This is where most users get lost. With a bank card, the wallet usually says "We sent a code to your phone number", and the user waits for a text message. With our card programme, no text message is sent and no email is sent. The code only reaches your platform, through the API, and you show it to your user. The wallet's own screen may still say something generic like "verify your card". Ana will not know where to look unless you tell her. So the first job of your setup screen is one clear sentence: "Your code will appear here, in this app." #How do you build a setup screen that never gets stuck? A good setup flow feels like one smooth task, not a puzzle split across two apps. Add a guide on the card screen. A short "Add to Apple Pay / Google Pay" section with three or four steps. Many users do not know a virtual card can live in a phone wallet at all. Make the card details easy to find. Show the embedded card page, where the user taps the eye to see the number, behind the same unlock you use for any sensitive screen. Push, then pull. When the card.wallet_otp webhook arrives, send a push notification: "Your wallet code is ready." Fetch the code only when the user opens the screen. Offer a manual button. Some users switch back to your app before the webhook lands. A "Get my wallet code" button lets them fetch it themselves. Say what the code is for. Use kind to show "Code to add your card to your phone wallet" instead of a bare number. Keep the code on screen. It can be read only once. Show it clearly with a copy button, and leave it visible while the user switches apps. Never store it. No database, no logs, no analytics, no crash reports. Treat it like a password. #Which mistakes leave users stuck? Each one leaves a user staring at a wallet screen. The help page says "wait for an SMS"Users wait for a code that never comes. Point them to your app. A background job fetches the codeThe code is used up and the user sees nothing. Fetch it only when the user is looking. Full API responses are loggedA live code ends up on disk. Remove the code field before anything is logged. The webhook signature is not checkedAnyone could fake an event. Verify x-cryptoinfra-signature on the raw body. The user sets up a frozen cardTaps fail at the shop. Show the card status and unfreeze it first. The phone has no screen lockThe wallet will not accept any card. Mention it in your guide. The webhooks guide shows exactly how to check the signature header. #What happens after the card is in the wallet? The card in the wallet is the same card Ana holds in your app. Four things are worth explaining to users. The balance is shared. A tap in a shop spends the same balance that was loaded onto the card. There is no separate wallet balance to top up. Freezing works everywhere. If Ana loses her phone, she freezes the card in your app. Your server calls POST /v1/cards/{id}/freeze and spending stops, including taps from the phone. /unfreeze turns it back on. Card events still arrive. Every payment, tap or online, produces the usual card.* webhooks, so your transaction list stays complete. Closing the card ends it. A closed card can no longer pay, in the wallet or anywhere else. The remaining balance goes back to the card programme's wallet that paid for the card. Card fees for payments are listed with every other card fee on the pricing page. Show users real numbers from there instead of guessing. #Questions people ask Can you add a crypto card to Apple Pay or Google Pay? Yes, when the card programme supports it. Cryptoinfra's virtual Visa cards can be added to Apple Pay, Google Pay and Samsung Pay. Why is no SMS code arriving when I add my crypto card to a phone wallet? Because none is sent. The verification code is delivered to the app that gave you the card. Open that app and look on the card screen. Can a virtual card be used in a physical shop? Yes. Once it is in a phone wallet, the user taps the phone at the card terminal. No plastic card is needed. What should a user do if the phone is lost? Freeze the card in the app. Spending stops everywhere, including taps from the phone, until the card is unfrozen. #Try it A phone wallet is what turns a virtual crypto card into an everyday card. Your side is one webhook, one endpoint and one clear screen. Sign up and start building, or read the crypto card API page for the rest of the programme. --- ## How 3-D Secure Works on a Crypto Debit Card URL: https://cryptoinfra.net/blog/how-3d-secure-works-on-crypto-debit-cards Published: 2026-10-25 Your user, Daniel, is buying headphones online. He types in his crypto card number, presses Pay, and a new box appears: "Enter the code to confirm this payment." That box is 3-D Secure. If your app is ready for it, he finishes the payment in a few seconds. If it is not, he is stuck, the payment fails, and he blames your card. This guide follows that one payment. It shows where the code comes from, and how to put it in front of Daniel in time. In short3-D Secure is an extra check at an online checkout: the shop asks for a one-time code that only the real cardholder should have. On a Cryptoinfra card the code is not sent by SMS or email. It reaches you through the API, and your app shows it to the user. A signed webhook says a code is waiting. Your app then fetches the code once, when the user is looking. Never store or log the code, and tell users plainly that it appears in your app. #What is 3-D Secure? 3-D Secure is an extra check that some online payments go through. Before the payment is approved, the shop asks the card programme a simple question: "Is the real cardholder making this payment?" Sometimes the programme answers on its own, in the background, and the user sees nothing. Other times it asks for proof. That is the challenge: the shop shows a box, and the cardholder types a one-time code. The idea is simple. A thief may have a copy of the card number, the expiry date and the security code. They should not have the one-time code, because it only goes to the real cardholder. #Why will every cardholder meet it? A crypto card is a normal card once a payment leaves it. The shop does not know the money came from stablecoins. It follows the same rules as for any other card. Many shops ask for 3-D Secure on larger orders, on first purchases, or when something looks unusual. So this is not a rare edge case. Sooner or later, every active cardholder sees the box. For a business that offers crypto cards, a smooth challenge is part of the product, just like loading the card or showing its balance. #Where does the code come from? With a bank card, the code usually arrives by text message from the bank. A crypto card programme works differently, and this is the part many teams get wrong. On our platform the code does not go to the user by text message or email. It comes to you, the business, through the API. You show it to your user inside your own app. Here is Daniel's payment, step by step. One payment, one code01Daniel presses PayThe shop asks for a 3-D Secure challenge We receive the codeIt is held for a short time, for that card only Your server is toldA signed webhook says a code is waiting 04Your app fetches itOne call, made when Daniel opens the screen 05Daniel types the codeThe shop accepts it and the payment completes Two details matter for your developers. The webhook is a signed card.wallet_otp event. It tells you a code is waiting. It does not contain the code. To get the code, your app calls GET /v1/cards/{id}/otp with the user's id. The same flow is used when a user adds the card to a phone wallet. The response has a kind field, so you can tell a checkout code from a phone-wallet code and show the right message. That side is covered in adding a crypto card to Apple Pay and Google Pay. #Why is the code handled this way? It may look like extra work: a webhook first, then a separate call. Every rule in this flow exists to keep the code secret. Five rules that keep the code secretWhat happensWhy it helpsNo code in the webhookThe event only says a code is waitingWebhooks are stored and retried. A code inside one could leak laterFetched on demandThe code moves only when your app asks, over an authenticated callNothing travels until it is neededRead onceEach code can be fetched a single timeIf a response leaks, nobody can fetch the same code againShort-livedThe code expires quicklyA stolen code is useless after a short timeBound to its ownerThe code belongs to one card, and the request carries the user's idIt proves the right person is asking One more rule protects the endpoint itself. When no code is waiting, or it has expired, or the card belongs to someone else, the answer is the same simple "no code available". It never says which reason applied, so nobody can use the endpoint to guess card details. #How do you show the code in your app? The best flows feel like part of the checkout, not a puzzle. Five steps get you there. A challenge screen that worksPush, then pullWhen the card.wallet_otp webhook arrives, send a push notification or show a banner: "A payment needs your confirmation." Fetch the code only when the user opens the screen. Offer a manual buttonSome users open your app before the webhook lands. A "Get my payment code" button lets them fetch it themselves. The card details response also tells you whether a code is waiting. Say what it is forUse kind to say "Confirm your online payment" or "Add your card to your phone wallet". Users trust a code more when they know why they see it. Show it once, clearlyThe code is single-read. Display it with a copy button, and keep it on screen while the user is in the flow. Never store itDo not write the code to your database, logs, analytics or error reports. Treat it like a password. #Which mistakes break the checkout? Daniel will not report any of these as a bug. He will just say "my card does not work". Telling users to wait for a text messageNo text message comes. Update your help pages to point users to your app. Fetching the code in a background jobThe code is single-read. If a job fetches it and throws it away, the user has nothing left to see. Fetch it only when the user is looking. Logging the full API responseA debug line with the response body puts a live code on disk. Strip the code field before anything is logged. Skipping webhook verificationCheck the x-cryptoinfra-signature header over the raw body before you trust an event. Forgetting the feeA 3-D Secure check can carry a small card fee. It is taken inside the transaction amount, not added on top. Show the live figure from the pricing page. The webhooks guide shows how to check the signature, and our post on receiving webhooks safely explains why it matters. #What if the user did not start the payment? A code for a payment the user never made is a warning. Somebody else may have the card details. The one-time code did its job: without it, that payment cannot be confirmed. Your part is the next step. Make sure your support staff know how to freeze a card as soon as a user reports a payment they did not make. #Questions people ask What is 3-D Secure on a debit card? It is an extra check at an online checkout. The shop asks the card programme to confirm that the real cardholder is paying, and the cardholder may have to type a one-time code. Why am I not getting my 3-D Secure code by SMS? Some card programmes do not send it by SMS. On cards issued through Cryptoinfra, the code appears in the app that gave you the card, so open that app. Does every online payment ask for a 3-D Secure code? No. Sometimes the check passes in the background and the user sees nothing. Shops tend to ask on larger orders, on first purchases, or when something looks unusual. Is there a fee for a 3-D Secure check? It can carry a small card fee, taken inside the transaction amount and not added on top. The current schedule is on the pricing page. How long is a 3-D Secure code valid? Only for a short time, and it can be read only once. That is why an app should fetch it when the user is looking, not in advance. #Try it 3-D Secure is a small screen, but it decides whether a payment goes through. Build it once, and your cardholders will never think about it again. Sign up to start building your card programme. The full card API, with every field and event, is in the cards guide, and the crypto card API page shows the rest of the programme. New to the money behind a card? Start with how crypto debit cards work. --- ## What Is KYC for Crypto Cards, and Why Does It Matter? URL: https://cryptoinfra.net/blog/what-is-kyc-for-crypto-cards Published: 2026-10-24 You want to give your users a crypto card. Very early, you meet three letters: KYC. Now an identity check stands between your user and the card, and you wonder how many people will give up at that step. Fewer than you fear, if you build it well. KYC means Know Your Customer: the check a person passes before a card is issued in their name. A good one takes a few minutes and happens once. This guide shows what it asks for, why a card needs it, and where to put it so that users finish. In shortKYC is the identity check a person passes once, before a card is issued in their name. Card networks and card programmes require it. It also keeps fraud out and protects your users and your brand. With Cryptoinfra the check is a hosted flow: you send the user to a secure link and wait for the verdict. Ask for it when the user wants a card, not at signup, and say what is happening at every status. #What does a KYC check ask for? Before a card programme lets someone spend with a card, it confirms that the person is real and is who they say they are. Take one user, Omar. He taps "Get a card" in your app. A typical check asks him for three things: his legal name, date of birth and country; a photo of a government ID document; a live selfie, so his face can be matched to the ID. The check compares these pieces, looks for signs of fraud and returns a verdict. Omar is approved, declined, or sent to review for a closer look. #Why does a crypto card need KYC? A crypto card turns a crypto balance into money that can be spent wherever Visa is accepted. Once a payment leaves the card, it is in the normal card world, with the same rules as any bank card. So a card programme asks for verified cardholders, for four reasons. It is a rule. Card networks, and the programmes behind each card, require a verified holder. Without one, the card cannot be issued. It stops fraud early. Stolen identities, fake accounts and money mules are much harder to run through a programme that checks every holder. It protects your users. If someone steals a phone or an account, a card in the real owner's name is easier to freeze, investigate and recover. It protects your brand. Your name is on the card experience. A programme full of fake holders gets restricted, and your honest users pay the price. #How does the check run with Cryptoinfra? Cryptoinfra runs the identity check as a hosted flow. You do not have to build camera screens, store ID photos or judge documents yourself. First, read the card product: each one says whether it needs verification. If it does, this is Omar's path. Omar's identity check01Create the cardholderYour app sends his email, his name and whatever else you have 02Start the checkThe API returns a secure link, and your app opens it Omar is checkedOn the hosted page he shows his ID and takes a selfie 04Wait for the verdictAsk for the status, or listen for a signed webhook 05Issue the cardOnce the status is approved, you issue the virtual Visa card In the hosted flow your app never handles the ID photo or the selfie. It only learns the verdict. Four details make this smoother: Users are checked once. If Omar is already approved, starting the check again simply returns "approved". Nobody is sent through the flow twice. Issuing too early is refused. Try to issue a card that needs verification before Omar is approved, and the API refuses with a clear error and his current status. No half-made card appears. Some programmes use documents instead. A few card programmes take an uploaded set of documents in place of the hosted link. The card product tells you which one applies, so you never need both. Abuse is capped. Starting brand-new checks has a daily limit per business, so a bot cannot burn through verifications. Resuming a check that is already open never counts against it. Every endpoint and field is in the cards guide. #What should your app show at each status? A check has five statuses, and each one needs its own screen. The five statusesWhat it meansWhat your app should doNot startedOmar has not opened the checkShow a clear "Verify your identity" buttonPendingHe is in the flow, or the check is runningShow progress, and do not ask againApprovedHe is verifiedLet him pick and issue a cardDeclinedThe check did not passExplain kindly and offer a fresh attemptReviewThe check needs a closer lookTell him it is being reviewed Declined and review are final for that attempt. The user can start a new one. Review must never be a silent waiting screen. A blank spinner looks like a broken app, so tell Omar plainly that his check is being reviewed. Declined is rarely the end. Many declines come from a blurry photo or an expired ID. A clear "try again with a sharper photo" message saves real users. #When should you ask for KYC? Ask when the user wants a card, not at signup. If the check is your very first screen, many users leave before they see any value. If you wait until Omar taps "Get a card", he already knows why the check is needed, and he is far more likely to finish it. The order that keeps usersHe signs upOmar gets a USDT wallet in your app. He deposits and looks aroundHe sees what your product does before you ask for anything more. He taps "Get a card"Now the check has a reason he understands. Your app explains and opens the linkOne sentence on why the check is needed, then the hosted flow. The webhook says approvedThe app moves straight to choosing a card. The wallet side of this order is on the wallets page, and the card features are on the cards page. #How do you make the check easy to finish? Users drop out for small, fixable reasons. This list removes them. Before you ship the identity stepTell users why you need the check before they start. Say what they need: a valid ID and a phone camera, in good light. Pre-fill what you already know, so they type less. Listen for the webhook instead of making users refresh. Show a friendly screen for declined and for review, with next steps. Never store ID photos yourself when the hosted flow already does it. Show card prices before the check, so nobody verifies and then leaves at the price. A user who passes the check and only then sees the price feels tricked, so link to the live numbers on the pricing page early. And do not build your own ID capture. Handling passport photos means storing very sensitive data, and the hosted flow carries that load for you. #What comes after KYC? KYC is the first step of the card journey, not the whole journey. After it come issuing, loading with USDT on-chain, spending online or through Apple Pay and Google Pay, and closing the card. How crypto debit cards work walks through each step, and how to launch a crypto card programme turns them into a plan. When the identity step is short, clear and placed at the right moment, most users barely notice it. They just see a card that is ready to use. #Questions people ask What does KYC mean for a crypto card? KYC stands for Know Your Customer. It is the identity check a person passes before a card is issued in their name. What documents are needed for crypto card KYC? A typical check asks for a legal name, date of birth and country, a photo of a government ID, and a live selfie to match the face to the ID. How long does KYC take for a crypto card? A good flow takes the user a few minutes, and it happens once. A check that is sent to review gets a closer look first. Can you get a crypto card without KYC? Card networks and card programmes require a verified holder. On Cryptoinfra each card product says whether it needs the check, and when it does, no card is issued until the user is approved. What happens if a user fails KYC? A declined check is final for that attempt, but the user can start a new one. Many declines come from a blurry photo or an expired ID. #Try it Signing up takes a few minutes, and you can build your wallet and webhook handling in the sandbox while you plan the card flow. Sign up free and start building your card onboarding today. --- ## Virtual vs Physical Crypto Cards: Which Should Users Get? URL: https://cryptoinfra.net/blog/virtual-vs-physical-crypto-cards Published: 2026-10-23 You have decided to give your users a crypto card. The next question arrives at once: should it be a virtual card that lives in the phone, or a physical card they can hold? Both spend the same money. Both carry a card number, an expiry date and a security code. The difference shows up in launch time, cost, safety and support, and this guide compares them so you can pick the right first card. In shortA virtual card is ready the moment it is issued. A physical card has to be printed and posted first. With Apple Pay or Google Pay, a virtual card pays in shops too. The main thing it cannot do is ATM cash. Virtual cards cost less to run and are easier to keep safe: there is nothing to ship, lose or replace. For most crypto businesses, virtual is the right first card. Cryptoinfra issues virtual Visa cards today. #What is the difference, really? Take one user. Sara holds USDT in your app, and tonight she wants to book a flight. With a virtual card, the card exists only as data. Sara sees the card number, expiry date and security code inside your app. She types them into the airline's website, and the flight is booked. There is no plastic, and the card was ready the moment it was issued. With a physical card, Sara waits. This is the plastic (or metal) card most people already know, and it has to be printed, packed and posted to her home address. When it arrives, it works at shop terminals, in ATMs and anywhere a card must be inserted or swiped. It feels familiar. But tonight's flight is gone. Same money, same kind of card details, a very different first day. #How do they compare side by side? Here are the questions a business asks most often, answered for both kinds of card. Virtual or physicalVirtual cardPhysical cardHow fast the user can startRight after issueAfter printing and deliveryWorks onlineYesYesWorks in shopsYes, through Apple Pay or Google PayYes, by tap, chip or swipeWorks in ATMsUsually notYesShipping and address checksNoneNeeded for every cardLost or stolen cardFreeze it in the appFreeze it, then print and post a new oneCost to runLowerHigher, with production, postage and replacementsMany cards for one userEasyImpractical One row favours plastic, and it is ATMs. On every other row, virtual does the same job or a better one. #Can a virtual card really pay in a shop? Yes, and this is the point most people miss. The one thing users expect to lose without plastic is paying at a till. A phone wallet gives it back. From issue to a tap at the till01Sara asks for a cardIn your app, after a quick identity check The card is issuedA virtual Visa card, ready at once 03She adds it to her phoneApple Pay or Google Pay 04She paysOnline with the card details, in shops by tapping her phone No printing and no post. The whole path can happen in one session. Once the card is in Apple Pay or Google Pay, a phone tap works at most modern card terminals. For many users, that is all they need. Do not assume they know this. Many users have no idea a virtual card can go into Apple Pay or Google Pay. Our guide to using a crypto card with Apple Pay and Google Pay shows how to build that setup step. #Why does virtual suit most crypto users? Think about who holds crypto in your app. Most of them already live on their phones. They shop online, pay for software, book flights and order food. A virtual card covers almost all of it. Speed. A user who loads USDT and wants to buy something today will not wait for the post. A virtual card can be issued and used in the same session. That first good experience is often what turns a curious user into a regular one. Safety. A virtual card cannot be lost in a taxi or copied at a shop terminal. If anything looks wrong, the user or your support team can freeze the card at once and unfreeze it later. Online payments are also protected by 3-D Secure codes, which your app can show to the user directly. Reach. Posting cards across many countries brings customs delays, lost parcels and address problems. A virtual card reaches a user in any supported country the same way: through your app. #When is a physical card still the better choice? Plastic is not useless. It is the better choice when: your users often need cash from ATMs; your users live where phone wallets are not common; you sell to older customers who prefer something they can hold; a premium plastic or metal card is part of your brand promise. If these points describe your core users, be honest about the extra work. Address checks, delivery tracking, activation flows and replacement requests all land on your support team. #Which one should your users get? Ask three questions about your own users, not about cards in general. Start with virtual if these are trueMost of your users shop online or pay with their phone. They want to start spending on the same day. You serve users in many countries. Two answers point the other way: users who rely on ATM cash every week, and a brand built around a plastic card. If most of your ticks land on virtual, start there. Launch, watch how your users really spend, and let that decide what comes next. #What does Cryptoinfra issue today? Cryptoinfra issues virtual Visa cards under your brand. Physical cards are not offered today. The flow has five parts: Your user passes a quick identity check (KYC). You issue a virtual card through the API or your merchant dashboard. Each issue and each load is paid in USDT from your card programme's wallet, on TRON or BNB Smart Chain. The user spends online, or in shops through Apple Pay and Google Pay. You can freeze, unfreeze or close the card at any time. On close, the remaining balance goes back to the card programme's wallet. You set your own price for card actions and charge it to your users in your own app. Live numbers are always on the pricing page. The full feature list is on the cards page, and developers can start with the cards guide. #What mistakes do businesses make with a first card? Five mistakes are common. None of them is about the card itself. Waiting for plastic before launchingWhile you wait, users leave for apps that already let them spend. Launch virtual first and learn. Hiding the card detailsPut the card number, expiry date and security code one tap away, behind your app's normal security. Forgetting phone wallet setupMany users do not know a virtual card goes into Apple Pay or Google Pay. A short in-app guide makes it as useful as plastic. Not explaining fees up frontShow what each load and each close costs before the user confirms. Clear prices build trust. Ignoring the wallet behind the cardA card is only as good as the balance behind it. Keep your card programme's wallet funded, because an issue or load it cannot cover is refused. The kinds of fee a card carries are explained in how crypto debit cards work. #Questions people ask Can a virtual crypto card be used in physical stores? Yes. Once the card is added to Apple Pay or Google Pay, the user taps their phone at the terminal. This works at most modern card terminals. Can you withdraw cash from an ATM with a virtual card? Usually not. Regular ATM cash is the main reason a business chooses a physical card. Is a virtual card safer than a physical card? It removes two common problems: it cannot be lost like plastic, and it cannot be copied at a shop terminal. It can also be frozen in the app at once and unfrozen later. How fast can a user start spending with a virtual crypto card? Right after the card is issued. There is no printing and no delivery, so a card can be issued and used in the same session. Does Cryptoinfra offer physical crypto cards? Not today. Cryptoinfra issues virtual Visa cards under your brand, which work online and in shops through Apple Pay and Google Pay. #Try it For most crypto businesses the virtual card is the right first card: faster to launch, cheaper to run, safer to manage, and it works where your users already shop. Sign up free and start building, then follow how to launch a crypto card programme step by step. --- ## How Crypto Debit Cards Work (A Simple Guide) URL: https://cryptoinfra.net/blog/how-crypto-debit-cards-work Published: 2026-10-22 Your customer holds USDT. The coffee shop on the corner does not take USDT. A crypto debit card closes that gap: it is an ordinary Visa card whose money comes from a crypto balance instead of a bank account. This guide follows one card through its whole life — getting it, loading it, paying with it and closing it — and shows what each step means for the business that offers it. In shortA crypto debit card is a normal Visa card. Only the source of the money is different: a USDT balance, not a bank account. The card holds US dollars. Loading it turns USDT into a dollar balance any shop can accept. A virtual card works online at once, and in shops through Apple Pay, Google Pay or Samsung Pay. Every fee is shown before the user confirms, and unused money comes back when the card is closed. #The idea in one picture A shop never sees crypto. It sees a Visa card with dollars on it. Everything "crypto" happens one step earlier, when the card is loaded. From USDT to a paid coffee01User holds USDTIn the wallet inside your app 02Loads the cardUSDT leaves the wallet in one on-chain transfer Card is fundedThe load becomes a dollar balance on the card 04Pays by cardOnline, or by phone in a shop The shop is paid in its own currency. It never needs to know the money started as USDT. That is the whole trick. The rest of this guide is the detail behind each step. #Step 1: Getting a card Before a card exists, the cardholder passes a short identity check, known as KYC. The card network requires it, and it keeps a card programme clean. Our guide to KYC for crypto cards explains what is checked and why. When the check passes, the card is issued in seconds. A virtual card has a number, an expiry date and a security code, exactly like a plastic card. It simply lives in the phone, so there is nothing to print and nothing to post. Cryptoinfra issues virtual cards. If you are weighing them against plastic, read virtual vs physical crypto cards. #Step 2: Loading the card with USDT A card holds a balance in US dollars. To add money, the user loads it from a USDT balance. USDT is a dollar stablecoin, so one USDT becomes roughly one dollar on the card, less the load fee. With Cryptoinfra, every load is paid in USDT from your card programme's wallet, on TRON or BNB Smart Chain. That detail matters more than it looks: the money on a card can always be traced to a transfer that really happened on a blockchain. What the user sees when they loadThey type an amountThe app shows the fee, the network cost and exactly how much will reach the card. They confirmUSDT leaves the wallet in one on-chain transfer. The card is topped upThe dollar balance appears on the card, ready to spend. Nothing is hidden between the first screen and the last. The amount the user was shown is the amount that arrives. #Step 3: Paying A loaded card works in three places: Online, at any website that accepts Visa. In shops, once the card is added to Apple Pay, Google Pay or Samsung Pay. The user taps the phone. See how a crypto card works with Apple Pay and Google Pay. Abroad, wherever Visa is accepted. Some websites ask for one more proof that the buyer is the real cardholder. This is 3-D Secure: a one-time code sent for that single payment. With Cryptoinfra the code arrives in your app, so the user confirms inside the brand they already trust. A crypto card does not ask a shop to accept crypto. It turns crypto into the money the shop already accepts. #What does a crypto card cost? Almost every crypto card has the same three kinds of fee. Knowing them makes any provider's price list easy to read. The three fees on a crypto cardWhat it pays forWhen it is chargedCard feesIssuing the card, and each loadOnce at issue, then on every loadNetwork feeThe real cost of moving USDT on the blockchainOn every loadUsage feesExtras set by the card network, such as paying in a foreign currencyOnly when that happens A good provider shows all three before the user confirms. Cryptoinfra's current card prices are on the pricing page, read live from the same price sheet the API uses. If you run the programme, you can also add your own fee on top and keep it. #Step 4: Closing the card A user can close a card whenever they like. Whatever is left on it goes back to the card programme's wallet that paid for it, less the fees shown in advance. The refund is not instant, because the card network needs time to settle payments that are still in flight. With Cryptoinfra it usually arrives within 24–48 hours, and at the latest within the card network's settlement period of up to 45 days. The user sees the exact amount coming back before they confirm. #Mistakes to avoid These four cause most of the confused support messages a card programme receives. Treating the card as a crypto walletA card holds dollars. Crypto prices do not move its balance, and it cannot receive coins. Showing the fee after the loadShow the fee, the network cost and the amount that arrives before the user confirms, never after. Promising an instant refundSay at closing that money still settling comes back later, and show the amount. Going live without a trial runBuild your screens and webhook handling in the sandbox, then issue, load, spend and close one real card yourself before a customer does. #Why businesses add a card If your product already holds customers' crypto — an exchange, a wallet app, a payments company — a card is often the feature customers ask for next. Customers can spend what they hold, not only keep it. You set your own price on every card and every load. Customers stay inside your app instead of moving money elsewhere to spend it. With a white-label provider the card carries your brand, not the provider's. The steps are in how to launch a crypto card programme, and the product itself is on the cards page. #Questions people ask Is a crypto debit card a real Visa card? Yes. It is a Visa debit card and is accepted wherever Visa is. The only difference is that it is funded from a USDT balance instead of a bank account. Does the shop receive crypto? No. The shop is paid in its own currency, like any card payment. The crypto part ends when the card is loaded. Does the card balance move with crypto prices? No. The card holds US dollars. Once USDT is loaded, the balance stays in dollars until it is spent or refunded. Can it be used with Apple Pay or Google Pay? Yes. A virtual card can be added to Apple Pay, Google Pay or Samsung Pay and used by tapping the phone. What happens to the money when a card is closed? The remaining balance goes back to the card programme's wallet, less the fees shown before closing. It usually arrives within 24–48 hours. #Try it Build your side in the free Cryptoinfra sandbox first — wallets, payouts and webhook handling, with test money. Cards run on the live rail only, so issue your first card to yourself with a small load and follow it from issue to close. Start free, or read the cards guide first. --- ## How to Launch a Crypto Card Program in Five Steps URL: https://cryptoinfra.net/blog/how-to-launch-a-crypto-card-program Published: 2026-10-22 Your users hold USDT in your app. Sooner or later they all ask the same thing: how do I spend it? A card with your brand on it is the answer. Launching a crypto card programme used to mean months of contracts with banks, card issuers and processors. On a white-label platform that work is already done. What is left for you is five steps, and this guide takes them in order, from the first decision to the first paying customer. In shortA white-label platform replaces months of bank and issuer contracts with an API and a dashboard. Every card is paid for from one place: your card programme's wallet, which you fund with USDT. You earn the difference between the price you charge your users and the platform's fee. Your work is five steps: decide, build against the sandbox, build the card flow, set your price, then go live with your own card first. #Is a card programme right for your business? A card makes the most sense when you already have users who hold crypto. Four kinds of business fit best: a crypto wallet or exchange app; a payments or remittance business; a fintech app that wants to give its users spending in US dollars; an online platform where people earn or hold USDT. The test is simple. If your users hold USDT and want to spend it, a card is the natural next step. To keep things concrete, this guide follows one business: a wallet app whose users are paid in USDT. Its first cardholder is called Lina. #How does the money move? Settle this before anything else, because it shapes every later step. Lina does not pay the platform. You do, from one wallet. With Cryptoinfra, every card issue and every load is paid from your card programme's wallet. You fund that wallet with USDT, on TRON or BNB Smart Chain. What you charge Lina, and how, happens inside your own app. Who pays for Lina's card01You fund the walletUSDT on TRON or BNB Smart Chain goes to your card programme's wallet 02Lina asks for a cardShe sees your price in your app and confirms The card is issued and loadedPaid from your card programme's wallet 04Lina spendsOnline, or by phone in a shop, wherever Visa is accepted One wallet pays for every card. Keep it funded, because an issue or a load it cannot cover is refused. Two things follow from this picture. Your price and the platform's fee are separate numbers, and the gap between them is your revenue. And the wallet's balance is something to watch, like stock on a shelf. #Step 1: Decide what you will offer Before anyone writes code, answer three questions. Who are your cardholders? Your own users, each verified with a quick identity check. Our guide to KYC for crypto cards explains what the check asks for and the best moment to ask. How will cards be paid for? From your card programme's wallet, as the picture above shows. Decide now who on your team keeps it funded. What will you charge? You set your own price for issuing, loading and closing a card, and you charge it to your users in your own app. Write the three answers down. Everything you build next follows from them. #Step 2: Build against the sandbox Sign up and get a sandbox key. Nothing in the sandbox touches real money, so your team can try things safely: create test users, connect your webhook handler and get your screens talking to the API. Our guide to testing in the sandbox lists what the sandbox covers, and what it leaves for a careful first live run. The card itself gets its real test in step 5, on your own team. #Step 3: Build the card flow in your app Follow Lina from her first tap to her last. A complete card flow has six screens, and each one is one or two API calls. Lina's card, screen by screenIdentity checkLina completes KYC once. She is not sent through it again. Choose and issueShe picks a card and sees the issue price before she pays. LoadShe chooses an amount. Your app shows the full price, network cost included, and she confirms. UseThe app shows her card details securely, with the balance and recent transactions. Confirm paymentsWhen a website asks for a 3-D Secure code, the code the card receives appears in your app. CloseShe can close the card, and she sees exactly what comes back before she confirms. The cards guide shows every call in order. For the short version, see the crypto card API page. #Step 4: Set your price Your revenue from a card programme is the difference between the price you charge your customers and the platform's fee. You choose your price for every issue and every load. Take one load. The load, with the platform's fee, is paid from your card programme's wallet. Lina pays the price shown in your app. The gap between the two is yours. Keep your prices simple and show them clearly. Customers trust an app that shows the full price before they pay. The platform's current prices are on the pricing page, read live. #Step 5: Go live with your own card first When the flow is built, do not open the doors yet. Make your own team the first customers. Before you open cards to your usersSwitch your app to the live API key. Fund your card programme's wallet with USDT. Issue the first real card to someone on your own team. Load a small amount, pay for something, then close the card. Check that every number matches what your app showed. If a number on any screen differs from what really happened, fix that before a customer sees it. Then open cards to your users. #What goes wrong in a new card programme? Four mistakes come up again and again. Each one has a simple fix. Hiding feesShow the full price, network cost included, before a user confirms. Every time. Skipping the identity checkCards need verified cardholders. Build KYC into your onboarding, at the moment a user asks for a card. Letting the card wallet run dryEvery issue and load is paid from your card programme's wallet. One it cannot cover is refused, so watch the balance. Forgetting the close flowUsers will want to close cards. Show the amount coming back, and the timing, before they confirm. #What do your customers get? From Lina's side, the result is simple: a virtual Visa card in your brand; Apple Pay, Google Pay and Samsung Pay; spending online and in shops, wherever Visa is accepted; clear prices shown before every action. The cards page has the full feature list, and the white-label card provider page explains how the brand stays yours. If you need to explain the card to your users in simple words, send them how crypto debit cards work. #Questions people ask How long does it take to launch a crypto card? Building one from nothing means months of contracts with banks, card issuers and processors. On a white-label platform that part is already in place, so the time left is your own build: the card screens, the identity step and your prices. How does a business make money from crypto cards? You set your own price for issuing, loading and closing a card. Your revenue is the difference between that price and the platform's fee. Who pays for the cards, the business or the user? With Cryptoinfra, each issue and each load is paid from your card programme's wallet, which you fund with USDT on TRON or BNB Smart Chain. You then charge your users your own price inside your app. What do I have to build myself? The screens in your app: the identity step, choosing and issuing a card, loading it, showing its details and its 3-D Secure codes, and closing it. Each screen is one or two API calls. Can my users add the card to Apple Pay or Google Pay? Yes. The virtual Visa card works with Apple Pay, Google Pay and Samsung Pay, so users can tap a phone in a shop as well as pay online. #Try it Create a free account, get a sandbox key and start with step 1 today. When your flow is ready, make the first real card your own. --- ## How to Earn From Crypto Transactions: Set Your Own Fee URL: https://cryptoinfra.net/blog/set-your-own-fee-on-crypto-transactions Published: 2026-10-22 Your customers already move money through your app. They withdraw, they swap, they load a card. Each of those moments earns somebody a fee. With the right setup, that somebody is you. On Cryptoinfra a business earns in two ways at once. One needs no setup at all. The other is a fee you choose yourself. This guide follows one payout on a freelance marketplace to show where your income comes from, and how to price your fee so that customers accept it. In shortYou earn in two ways: a share of our platform fee, paid to you automatically, and your own fee on top, which is all yours. The share needs no setup. It is paid even if you never charge a fee of your own. Your own fee can be a percentage, a flat amount, or both, on payouts and swaps. On cards, you set your own price in your own app. Your customer sees one total before confirming, and what you earn reaches your balance as each operation settles. #Where does the money come from on one payout? Meet Lina. She is a designer on your freelance marketplace, and she wants to withdraw this month's earnings to her own wallet. To Lina it is one payout with one price. Behind that price sit three parts, and each does a different job. The three parts of one payout priceWhat it pays forWho keeps itNetwork feeThe real cost of moving coins on the blockchainThe network. Nobody earns on itOur platform feeRunning the platform that sends the payoutCryptoinfra, and a share of it goes to youYour feeWhatever you decide your service is worthYou. All of it Lina sees one total, before she confirms. Two of those three lines can pay you. The first cannot. A network fee is the real price of moving coins on a blockchain, so there is nothing in it to share. Why that cost moves from one send to the next is explained in USDT TRC20 payout fees explained. #Way 1: How do you earn with nothing to set up? Every time one of your customers makes a payout or a swap, or issues, loads or closes a card, Cryptoinfra charges a small platform fee. A share of that fee goes straight to you. There is nothing to set up. The share is paid into your balance the moment we earn it, and it works even if you never charge a fee of your own. The share is taken only from our platform fee, never from the network's cost. How large it is today is shown on the pricing page, read live. So when Lina's payout goes out, you have already earned once. #Way 2: How do you add your own fee? You can put your own fee on top of ours, on payouts and on swaps. You choose its shape: a percentage of the amount; a flat amount for each operation; or both together. Your fee is charged to your customer with everything else, and it is credited to your own balance in the same moment. All of it is yours. Here is Lina's payout again, this time with your fee on top. One payout, followed to your balance01Lina asks for a payoutShe wants 200 USDT sent to her own wallet 02She sees one totalThe network fee, our platform fee and your fee, together The payout is sentOne on-chain transfer to her address You are paidYour fee and your share of ours land in your balance Lina confirms once. You are paid twice: your own fee, and a share of ours. Now picture a thousand payouts like Lina's in one month. Your fee has been credited a thousand times, each one as its payout settled. You did not send a single invoice. A share of our fee reaches you whether you set a price or not. Your own fee is what you add on top, and you keep all of it. #How do you earn on cards? Cards work a little differently. Every card you issue and every load is paid from your card programme's wallet. What your users pay you for a card is your decision, and you set it in your own app. The difference between your price and ours is your margin. The automatic share applies here too. Issuing, loading and closing a card each carry our platform fee, and a share of it comes to you. If cards are new to you, how crypto debit cards work follows one card from issue to close. #Should your fee be flat, a percentage, or both? A flat fee is the same on every payout. A percentage is small on a small payout and larger on a large one. Used alone, each has a weak side: the percentage earns little on small payouts, and the flat fee earns no more on Lina's large withdrawal than on a tiny one. So many businesses use both. A small flat fee does the work on small payouts, and a percentage does the work on large ones. You can set both at the same time. You do not have to guess the result. The fee calculator shows one operation line by line, with your fee beside ours, so you see the total your customer will pay before you decide. Pricing your own fee, step by stepStart with one feeOne clear fee is easier for a customer to accept than several small ones. Look at what customers pay elsewhereYou do not need to be the cheapest, but your price should feel fair. Try it in the fee calculatorRead the total for a small payout and for a large one. Show the total before confirmingCustomers trust a price they can see. Review it after a monthYour Profit page shows which operations your customers use most. Price those first. #What is your fee never charged on? Your own fee is charged on your customers' operations. It is never charged on your own balance, so moving your own money does not cost you your own fee. Deposits are a separate case. There is no platform fee on deposits to the addresses we issue. On networks other than TRON and BNB Smart Chain, a deposit pays only the live network cost of moving it. Whether you take a fee of your own on a deposit is your choice. #Where do you see what you earned? Open the Profit page in your dashboard. It shows: every fee you charged, line by line; the total, for all time and for the last month; what is available to withdraw. You can withdraw it whenever you like. #What do businesses get wrong about fees? Counting the network fee as incomeIt is the real cost of the blockchain. Your share comes from our platform fee only. Waiting to earn until you set a feeThe share of our fee is paid from your first operation, with nothing to set up. Relying on a percentage aloneIt earns very little on small payouts. Put a small flat fee beside it. #Questions people ask How does a business make money from crypto payments? On each operation its customers make. On Cryptoinfra you receive a share of the platform fee on every payout, swap and card operation, and you can add your own fee on payouts and swaps. Can I charge my own fee on crypto payouts? Yes. Add a percentage, a flat amount, or both, on payouts and swaps. It is credited to your balance in the same moment, and all of it is yours. Do I earn anything if I do not charge a fee of my own? Yes. A share of our platform fee is paid into your balance automatically, with nothing to set up. The current share is on the pricing page. Is there a fee on crypto deposits? There is no platform fee on deposits to the addresses we issue. On networks other than TRON and BNB Smart Chain, a deposit pays only the live network cost of moving it. When can I withdraw what I earned? Whenever you like. The Profit page in your dashboard shows what is available to withdraw. #Try it Sign up free — there is no setup fee and no monthly fee. The live numbers are on the pricing page, and the fee calculator shows any operation with your fee beside ours before you set it. --- ## USDT TRC20 Payout Fees Explained: Why the Price Changes URL: https://cryptoinfra.net/blog/usdt-trc20-payout-fees-explained Published: 2026-10-22 Two freelancers withdraw from your platform on the same afternoon. Same coin, same network, same amount. One of them pays a higher fee than the other, and nobody touched a setting. Nothing is broken. On TRON, the price of sending USDT (USDT TRC20) depends on things the send screen does not show: who receives it, and how the network is paid. This guide uses those two payouts to explain the fee in plain words, and shows how a business keeps it low. In shortA USDT transfer on TRON pays for energy. How much it needs depends mostly on the receiving wallet, not on the amount. A wallet that holds no USDT — brand new, or emptied — needs roughly twice the energy of one that already holds some. Burning TRX is the most expensive way to pay for energy. Renting it costs much less, and Cryptoinfra rents it for every payout. Each payout is priced live, so your app can show the exact fee before the customer confirms. #Why did two equal payouts cost different amounts? The two freelancers are Amir and Bea. Amir gave the address of his exchange account. He uses it every week, and it already holds some USDT. Bea made a brand-new wallet for this job. It has never held a coin. The amounts are equal. But the network does not charge for the amount. It charges for the work a transfer makes it do, and sending to Bea is more work. To see why, you need two words: bandwidth and energy. #What does a USDT transfer on TRON pay for? Every transaction on TRON uses two resources. Bandwidth pays for the size of the transaction. Every account gets a small free amount each day, enough for a simple transfer or two. Energy pays for running a smart contract. USDT is a smart contract, a "TRC20 token", so every USDT transfer needs energy. Our plain guide to TRC20 explains the term. Energy is where the money goes. If a wallet does not have enough of it, the network burns TRX from that wallet to pay for the transfer. #Why does a new or empty wallet cost more? How much energy a USDT transfer needs depends mostly on the wallet that receives it. Amir's wallet already holds USDT, so the transfer only updates a balance that exists. Bea's wallet holds none. The network has to create a new balance entry for her first, and that needs roughly twice the energy. Same amount, two receiversAmirBeaAmount sent150 USDT150 USDTReceiving walletAn exchange account that already holds USDTA brand-new wallet that holds noneWhat the network doesUpdates a balance that existsCreates a new balance entryEnergy neededLessRoughly twice as much A wallet that was emptied counts like a new one. What matters is whether it holds USDT. The size of the payout matters very little. A small payout to an empty wallet can cost more than a large one to a wallet that already holds USDT. On TRON, the wallet that receives a USDT payout decides its price far more than the amount does. That is why Cryptoinfra shows two payout prices: one for a wallet that already has the coin, and one for a new or empty wallet. Before every send, the receiving wallet is checked and the right price is charged. Both prices are live on the pricing page. #Is the energy burned or rented? There are two ways to pay for the energy a transfer needs. The first is the one you met above: the wallet has no energy, so the network burns its TRX. It is the most expensive way to pay. The second is renting. Energy can be rented for a short time and delegated to the sending wallet just before the transfer. The transfer then uses the rented energy, and no TRX is burned. It is much cheaper. Cryptoinfra rents energy automatically for every payout. That is why the fee Amir and Bea pay is usually far below what the same send would cost a wallet that burns TRX. The pricing page shows both figures side by side, live. #What goes into the price of one payout? The cost of energy and the price of TRX change through the day. A fixed fee would overcharge your customers when costs are low, or lose money when costs are high. So each payout is priced live, at the moment it is asked for. How one payout gets its priceThe receiving wallet is checkedDoes it already hold USDT, like Amir's, or none, like Bea's? The energy is worked outHow much this exact transfer needs. Live prices are appliedThe energy price and the TRX price right now. A small cushion is addedIt covers price movement in the seconds before sending. The platform fee is addedA flat fee, the same for Amir and for Bea. The network fee is always charged in the coin you send. Bea's fee is higher than Amir's because of the first two steps, and for no other reason. #What does the customer see before confirming? Your app can ask for this exact price before every send. Show it, and only then let the customer confirm. Bea's payout, from request to chain01Bea asks for a payoutShe types 150 USDT and her new address The price is worked outLive, for her wallet, at this moment 03Bea sees the feeBefore any money moves 04She confirmsWith the full cost in front of her The payout is sentWith rented energy, so no TRX is burned Bea sees the exact fee before she confirms, never after. A fee that is shown is a fee that is accepted. A surprise fee becomes a support ticket. If you add your own fee on top of ours, show it in the same total. To see one payout line by line, open the fee calculator. #How do you keep payout fees low? You cannot change what the network charges. You can change how often you pay the higher price. Paying to a fresh wallet when an old one existsSuggest a wallet the receiver already uses, such as a regular exchange account. If it holds USDT, the send costs less. Splitting one payout into many small onesEach transfer has its own network cost. Send one. Showing the fee after the sendAsk for the live price first and show it. Customers accept a fee they can see. Burning TRX on every sendIt is the most expensive option. Use a provider that rents energy. Typing one fixed fee into your appCosts move through the day, so a fixed number is wrong in one direction or the other. #Is a TRX payout priced the same way? No. Sending TRX itself does not run a smart contract, so it needs no energy, only bandwidth. That makes a TRX payout simpler: it costs the same whether the receiving wallet is new or not. If Bea had asked for TRX, her new wallet would not have changed the price. #Questions people ask Why is the USDT TRC20 fee different every time? Two things move it. The receiving wallet may or may not hold USDT already, and the price of energy and of TRX changes through the day. That is why each payout is priced live. Why does sending USDT to a new wallet cost more? A wallet that holds no USDT has no balance entry yet. The network must create one, which needs roughly twice the energy of updating a balance that exists. An emptied wallet costs the same as a new one. Does the amount change the network fee for USDT on TRON? Very little. A small payout to an empty wallet can cost more than a large payout to a wallet that already holds USDT. What happens if a wallet has no energy? The network burns TRX from that wallet to pay for the transfer. It is the most expensive way to pay, which is why Cryptoinfra rents energy for every payout instead. Does a TRX payout cost the same as a USDT payout? No, it is priced differently. Sending TRX needs only bandwidth, no energy, and costs the same whether the receiving wallet is new or not. #Try it Want payouts that are priced live and paid with rented energy? Start free with Cryptoinfra, see how payouts work, or read the payouts guide first. --- ## What Is a White-Label Crypto Payment Gateway? (Founder's Guide) URL: https://cryptoinfra.net/blog/what-is-a-white-label-crypto-payment-gateway Published: 2026-10-22 Your online store sells running shoes. Every week a few customers ask the same thing: can I pay in USDT? You want to say yes. You do not want to turn a shoe shop into a blockchain company to do it. A white-label crypto payment gateway is how you say yes. The customer pays your store, under your name. A specialist does the crypto work behind it and stays out of sight. This guide follows one order, so you can see exactly who does what. In short"White label" means your customer deals with you — your name, your pages, your price — while a specialist runs the crypto behind it. The gateway does the slow, risky parts: addresses, watching the blockchain, payouts, network fees and the books. You keep the brand, the customer and the price, including your own fee on top. You can run a whole order with test money in a free sandbox first. #What does "white label" actually mean? Think of a supermarket's own-brand coffee. A specialist roasted it and put the supermarket's label on the bag. The shopper buys from the supermarket, and nobody asks who roasted the beans. A white-label crypto payment gateway is the same deal. You are the supermarket. The gateway is the roaster nobody sees. The half of the work that faces the customer stays yours. The half that faces the blockchain is done for you. Who does whatYouThe gatewayThe name the customer seesYesNoThe customer and their questionsYesNoYour prices and your own feeYesNoAddresses and the keys behind themNoYesWatching the blockchain for paymentsNoYesPaying each network's feesNoYesBooks that match the blockchainNoYes The top three rows are your business. The bottom four are infrastructure. #What happens when a customer pays? Maya is buying a pair of shoes from your store. Here is her order, start to finish. One order, paid in USDT01Maya checks outOn your store, she chooses to pay in USDT 02She sends the payment49.99 USDT from her own wallet, to the address shown The payment is confirmedWe watch the blockchain until the network confirms it Your balance goes upYour server gets a signed webhook 05You ship the shoesYour store marks the order paid, under your name The two marked steps are the gateway's. Maya sees only the other three. Look at what Maya saw: your store, an address and an amount, then your confirmation. Between her click and that confirmation, you did nothing. What told your store to ship? A webhook: a short, signed message the gateway sends your server once the money is credited. Your server checks the signature before it ships anything. Receiving webhooks safely shows how. #How do you add it to your checkout? There are two ways in. They differ in how much of the page is yours. Your own checkout page. Your server sends the API the order number, the price in US dollars and the coin Maya chose. The answer carries an address and the exact amount to pay. Your page shows them in your own design, and Maya never leaves your site. This is white label in the full sense. See the white-label gateway page. The hosted checkout. You send Maya to a ready-made payment page that shows your store's name and logo. There she picks the coin and the network she already uses. A store plugin, a payment link or a point-of-sale screen creates the same payment with little or no code. See the payment gateway page. Both routes price the order in US dollars and send the same webhooks. So you can start on the hosted page and move to your own page later. #What do you no longer have to build? Imagine Maya's order without a gateway. Before she could pay, your team would have to build five things: wallet keys, created and protected for every customer; a watcher that sees each deposit on the blockchain and confirms it; payouts that can never send the same payment twice; network fees, paid on every transaction; a ledger that always matches what is really on-chain. Each one takes months to build well, and a mistake can lose real money. A white-label gateway has already solved them, behind one API. Build it yourself, or use a white-label gatewayBuild it yourselfWhite-label gatewayTime to launchMany monthsDaysWallet key securityYour problemHandled for youBlockchain monitoringYour own serversIncludedNetwork feesYou manage energy and gasPriced and paid for youYour brand in frontYesYes Either way, the customer sees your brand. Only one route skips the months. Building it yourself can still be right when moving crypto is your product. When crypto is one more way to pay for shoes, renting the plumbing is faster and safer. One thing to know first: here the gateway holds the keys for you. Custodial vs non-custodial wallets explains what that means for a business. #What do you still own? White label does not mean hands off. Three things stay with you. The brand. On your own checkout, Maya sees your store's name from the first click to the receipt, and nobody else's. The customer. Maya has an account with you, not with the gateway. If she has a question about her payment, she writes to you. The gateway gives you the facts, and you give the answer. The price. You set the price of the shoes. The gateway publishes its fee, and you can add your own fee on top and keep it. Live numbers are on the pricing page. Everything your customer can see is yours. Everything they cannot see is done for you. #What else can you offer under your name? The same account does more than a checkout: Wallets — one API call gives each customer a permanent address on each network. Deposits are confirmed, credited and reported to your app by signed webhook, with no platform fee. See wallets and the wallet API guide. Payouts — send crypto to any address on the networks we support, priced live for each send. Your app asks for the exact fee, shows it, then sends. See payouts. Visa debit cards — virtual cards paid in USDT from your card programme's wallet, used anywhere Visa is accepted, including Apple Pay and Google Pay. See cards. Swaps — exchange any supported coin for another, by API. See swap. #Which network should your customers pay on? For stablecoin payments, TRON is one of the most popular networks. USDT on TRON, often written USDT TRC20, moves quickly and costs much less to send than on many other chains. That is why Cryptoinfra started there, with USDT and TRX. You do not have to choose. The platform also works on BNB Smart Chain, Solana, Bitcoin and TON, so Maya pays on the network she already uses. #What should you check before choosing a gateway? Not every gateway that says "white label" means it. Check these seven points first. Clear, live pricing. You can see what each deposit, payout and card costs before you sign up, with no hidden setup or monthly fee. Real white label. Your customers never see another company's name in emails, receipts or API responses. A free sandbox. You can run a whole order with test money first, and the provider says plainly what the sandbox does not cover. Safe payouts. Look for idempotency, which means a retried request can never pay twice. Signed webhooks. Every event your server receives carries a signature you can verify. Strong account security. Every change in the dashboard needs an authenticator code, not just a password. Your own fee. The gateway publishes its fee and lets you add your own on top. #Questions people ask What is a white-label crypto payment gateway? Crypto payment infrastructure that a business offers under its own brand. The customer deals with the business, and the gateway runs the addresses, the blockchain monitoring, the payouts and the books behind it. Will my customers see the gateway's name? Not when you build the payment step into your own checkout: the page, the design and the name are yours. The hosted checkout shows your store's name and logo, on a ready-made page that we host. Do I need blockchain developers to use one? No. A store plugin or a payment link needs little or no code. For your own checkout you need a developer who can call an API and receive a webhook. Which coins can my customers pay with? USDT on TRON, BNB Smart Chain, Solana and TON; USDC on BNB Smart Chain and Solana; and each network's own coin: TRX, BNB, SOL, BTC and TON. #Try it You can run Maya's whole order — checkout, payment, webhook — in the Cryptoinfra sandbox with test money. There is no setup fee and no monthly fee: you only pay when money moves. Sign up free, get a sandbox key and follow the quickstart guide. Go live when you are ready. --- ## White-Label Crypto Wallet API — Give Every User a Wallet URL: https://cryptoinfra.net/blog/white-label-crypto-wallet-api-guide Published: 2026-10-22 Your app helps freelancers get paid. One of them, Sam, has a client abroad who wants to pay in USDT. Sam asks you a simple question: where should they send it? The answer is a deposit address that belongs to Sam and lives inside your app. A white-label crypto wallet API gives you one for every user, under your brand, without you building or guarding a single wallet. This guide follows Sam from sign-up to his first withdrawal, one step at a time. In shortOne API call creates a user and gives them a permanent deposit address on each network. It never changes. Deposits are found, confirmed and credited for you, and your server is told by signed webhook. A withdrawal is a payout sent with an idempotency key, so a retried request can never pay twice. Your users see only your app. You keep the brand, the customer and your own fee, and you never handle a private key. #What does a white-label wallet API do for you? Sam thinks he has a wallet with your app. In every way that matters to him, he is right. Your name is on the screen, his balance is in your design, and he writes to your support when he has a question. Behind the screen, the API does the work Sam never sees. With one integration, each of your users gets: their own permanent address on each network; deposits that are detected, confirmed and credited automatically; a balance your app can read at any time; payouts to any address on those networks. Sam's first deposit01Sam signs upYour app creates him on the API with your own user ID 02He copies his addressShown inside your app, in your design 03His client pays250 USDT sent to that address The deposit is confirmedWe see it on the blockchain and wait until it is safe Sam's balance goes upYour server gets a signed webhook Sam sees your app from start to finish. The two marked steps happen behind it. That split is what "white label" means. The customer, the screens and the price are yours. The keys, the blockchain and the bookkeeping are done for you. The product itself is on the wallets page. #Should you build the wallets yourself? You could. Here is what each road asks of your team. Build it yourself, or use a wallet APIBuild it yourselfWallet APIKeys for every userYou create and guard themKept apart from the servers your app talks toSeeing a depositYou watch every network yourselfDetected for youKnowing it is safeYou count the confirmationsConfirmed, then creditedSending money outYou make sure nothing is paid twiceOne request, one paymentYour brand on the screenYesYes The last row is the same on both roads. Everything above it is work you can skip. Build it yourself when wallets are your product and you have a team to run them for years. When a wallet is one feature of a bigger product, an API is the shorter road. Here the provider holds the keys, which is called custodial. Custodial vs non-custodial wallets explains the trade. #Step 1: Get a sandbox key Start in the sandbox. It has the same API as the live platform, but runs on test money. You can create users, simulate deposits and send test payouts without risk. On a blockchain a wrong payment cannot be called back, so your first real payout should not be your first payout. How to test crypto payments in a sandbox has a full test plan. #Step 2: Create a user and show the address When Sam signs up in your app, create him on the wallet API with the ID he has in your own system: textCopyCopiedPress ⌘CPOST /v1/users { "external_user_id": "10482" } The answer includes Sam's wallet address. Show it in your app as his deposit address. It never changes, so he can save it and give it to every client. Asking again with the same ID returns the same address, so a retry never makes a second Sam. Sam gets one address on each network: TRON for USDT and TRX; BNB Smart Chain for USDT, USDC and BNB; Solana for USDT, USDC and SOL; Bitcoin for BTC; and TON for USDT and TON. Always show the network's name beside the address, because an address only takes payments on its own network. #Step 3: Receive the deposit Sam's client sends USDT to the address. From here the platform does four things without you: sees the transaction on the blockchain; waits for enough confirmations to be safe; credits Sam's balance; sends your app a webhook. There is no platform fee on a deposit. On TRON and BNB Smart Chain Sam receives the full amount. On the other networks only the live network cost of moving the deposit is taken. The wait matters: a transfer that has only just appeared is not final yet. How crypto deposits are confirmed on TRON explains why. #Step 4: Verify every webhook Anyone who learns your webhook URL can send it a message that says "Sam was paid". So every real webhook carries a signature in the x-cryptoinfra-signature header. It is an HMAC-SHA256 of the raw request body, made with your endpoint's secret. Always check it before trusting a webhook: textCopyCopiedPress ⌘Cexpected = HMAC_SHA256(secret, raw_body) if expected != header: reject This stops anyone from faking a deposit by sending your server a made-up request. Receiving crypto webhooks safely covers the rest. #Step 5: Send a payout A week later, Sam wants to move his money to his own wallet. What Sam sees when he withdrawsHe enters an amount and an addressYour app asks the API for the exact fee for that send. He sees the fee before he confirmsThe amount and the fee are on one screen. Nothing is added afterwards. He confirmsYour app sends the payout with an idempotency key, and the money leaves in one on-chain transfer. The idempotency key is the important part. It is a name you give the request; your own withdrawal ID works well. Suppose Sam taps Withdraw and your request times out. Did the payout go through? You cannot tell. So you send the same request again with the same key, and you get the first payout back instead of a second one. One request, one payment, always. More on sending is on the payouts page. #Step 6: Add your own fee You can add your own fee to payouts. It is charged on top and paid straight into your own balance. Our own prices are on the pricing page, and how to earn from every crypto transaction explains the rest. #What keeps the money safe behind the API? Sam will never ask this. You should. A good wallet API protects the money you cannot see: signing keys are kept apart from the servers your app talks to; every change in the dashboard needs an authenticator code; balances are checked against the blockchain regularly. Read more on our security page. #Mistakes to avoid Each of these is easy to make in a first integration. Trusting your own copy of a balanceStore the user's address, but read balances from the API, not from your own database. Acting on a webhook aloneCheck the signature, treat the webhook as a signal, then read the latest state from the API before acting on large amounts. Sending a payout without an idempotency keyAlways send one, and reuse the same key when you retry. Showing the fee after the sendAsk for the fee first and show it. Never let a customer discover a fee afterwards. Testing only what worksTest failure cases in the sandbox too, such as a payout to an invalid address. #Questions people ask What is a white-label crypto wallet API? An API that lets your app give each user a deposit address and a balance under your own brand. The provider creates the addresses, watches the blockchain and sends the payouts in the background. Does every user get their own wallet address? Yes. Each user gets one permanent address on each network. It never changes, and asking again with the same user ID returns the same address. Is there a fee to receive a crypto deposit? There is no platform fee on a deposit. On TRON and BNB Smart Chain the user receives the full amount; on the other networks only the live network cost of moving the deposit is taken. Do I have to store private keys? No. Your app never creates, stores or sees a key. Signing keys are kept apart from the servers your app talks to. #Try it Take Sam's journey yourself with test money. Sign up free, get a sandbox key and follow the quickstart. The developers page shows the rest of the API. For AI coding tools, the docs also include an MCP server and an llms.txt file, so your assistant can read the API too. Live prices: https://cryptoinfra.net/pricing.json