Crypto payment processing API
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"15018241","collectionId":"edf51330-82ce-44ff-863c-c77377ab3e91","publishedId":"2sBXihosBP","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-03-17T09:46:13.000Z"},"item":[{"name":"Standard Integration","item":[{"name":"Create Wallet","id":"ed36ad1d-8a83-4b35-a560-59b6bf619d2f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://api.onramp-pay/crypto/btc/wallet.php?address=bc1qx9t2l3pyny2spqpqlye8svce70nppwtaxwdrp4&callback=https%3A%2F%2Fwww.example.com%2Fmyorder%3Finvoice_id%3D75478385547922074","description":"Creates a unique crypto receiving wallet and sends a payment notification to your callback URL after payment is received.
\n","urlObject":{"protocol":"https","path":["crypto","btc","wallet.php"],"host":["api","onramp-pay"],"query":[{"key":"address","value":"bc1qx9t2l3pyny2spqpqlye8svce70nppwtaxwdrp4"},{"key":"callback","value":"https%3A%2F%2Fwww.example.com%2Fmyorder%3Finvoice_id%3D75478385547922074"}],"variable":[]}},"response":[{"id":"a13fda4a-ccc6-469a-a092-26a7ef1cdf8b","name":"Example Response","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://api.onramp-pay.com/crypto/btc/wallet.php?address=bc1qx9t2l3pyny2spqpqlye8svce70nppwtaxwdrp4&callback=https%3A%2F%2Fwww.example.com%2Fmyorder%3Finvoice_id%3D75478385547922074","protocol":"https","host":["api","onramp-pay","com"],"path":["crypto","btc","wallet.php"],"query":[{"key":"address","value":"bc1qx9t2l3pyny2spqpqlye8svce70nppwtaxwdrp4"},{"key":"callback","value":"https%3A%2F%2Fwww.example.com%2Fmyorder%3Finvoice_id%3D75478385547922074"}]}},"status":"OK","code":200,"_postman_previewlanguage":"Text","header":[{"key":"Date","value":"Mon, 06 Oct 2025 16:10:05 GMT"},{"key":"Server","value":"Apache/2.4.65 (Debian)"},{"key":"Strict-Transport-Security","value":"max-age=31536000; includeSubDomains; preload"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Content-Length","value":"257"},{"key":"Keep-Alive","value":"timeout=5, max=100"},{"key":"Connection","value":"Keep-Alive"},{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":""}],"_postman_id":"ed36ad1d-8a83-4b35-a560-59b6bf619d2f"},{"name":"Estimate Blockchain Fees","id":"86dcc5f2-8db8-4f84-8a27-6935741d870a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://api.onramp-pay/crypto/btc/fees.php","description":"You can use this endpoint to get the estimated blockchain fees. You don't need to pass any GET parameters for this request. Only the ticker path is required.
https://api.onramp-pay/crypto/{ticker}/fees.php
status: If the value is not success then the request was a failure.
estimated_cost: Estimated blockchain fees shown in the main network currency value. For example if you are fetching the estimated blockchain fees for trc20/usdt the value will be displayed as Tron (TRX).
estimated_cost_currency: The estimated blockchain fees calculated in fiat currencies for easier conversion.
You can use this endpoint to get the coin name, minimum transaction value and fiat converted values. You don't need to pass any GET parameters for this request. Only the
ticker path is required.
https://api.onramp-pay/crypto/{ticker}/info.php
coin: The name of the coin
minimum: The minimum transaction value of the coin that can be sent to the generated wallet address. Any sent amount below the minimum will be stuck in the generated address forever as it is less than required fees to process your forwarding transaction.
prices: Fiat converted value prices of the coin in different currencies.
You don't need to pass any GET parameters with this endpoint. It will return all supported networks with nested coins in JSON format listing coin name, identifier (ticker), logo and minimum transaction value (minimum_transaction_coin).
The following API endpoints are for the standard integration of the crypto payment gateway system. It is for merchants who want to create automated receiving crypto wallet addresses with QR codes to be displayed for their customers convenience. Any cryptocurrency sent to those generated receiving addresses will be automatically forwarded to the merchant predefined wallet without any delays or holds.
Our payment bot will send a GET request to the merchant predefined callback URL once a payment is confirmed at the receiving wallet address. Merchant need to have the proper coding logic at their server side to catch those callback events and change order/invoice status within their own system.
Merchants integrating this crypto payment gateway system must be aware of the minimum order value per ticker. Any value sent by the customer below those minimums will be stuck at the receiving wallet forever as the value is less than the blockchain fees to forward them.
Merchants must also be aware that generating a unique receiving wallet address with a correct merchant payout wallet requires that callback links must be unique by using at least one GET parameter at those links with a unique value for those parameters in order to generate a unique receiving wallet. Once a crypto receiving address is generated it is tied to the specified callback link and the payout wallet can't be changed later unless a new unique parameter value is passed. The unique GET parameter can be any of the merchant choice like order numbers or invoice IDs.
This endpoint is optional and it must be used if you want to use the hosted payment page with multi-coin mode that allows your customer to select from multiple cryptocurrencies while you pass the amount to be paid in fiat value. This can be useful if you don't want to go through complicated coding integration on your own website as the hosted multi-coin page will automatically detect the customer selected coin minimum value, convert fiat to crypto and display the proper coin value to pay + QR code. However in case you want to enable each coin while indvidually hosting the payment within your own website pages then you must use the default https://api.onramp-pay/crypto/{ticker}/wallet.php
Send the mandatory JSON payload per the same format as the example below via POST method. The POST body should contain valid JSON data and it must be in the following format:
{\"evm\" : \"0x4D7a0Ac80Fd4D3D136220dde9cca3F87EbDcdf15\", \"btc\" : \"bc1q3fpa39wmztes85sxr4v7rjufd0eec7jpnxdmzl\", \"bitcoincash\" : \"qqrg9vnfyuagnrnlm87dvnl4tfm4lprg9cd3wlxcja\", \"ltc\" : \"LNBPTHaLpLpViUADL71E1p4g5w3HFTPcEp\", \"doge\" : \"DBaCiFUYwEnPFq1iYnfpeVeBEQUZVUVatU\", \"solana\" : \"74uvtyU24SDzTZNxNbmVgfJTMaQiTcVr8y9zvcLFVziA\", \"trc20\" : \"TXkAFu57udvWQpHvPmSAWS2tGvgYqbTYaz\", \"fiat_amount\" : 139.99, \"fiat_currency\" : \"USD\", \"callback\" : \"https://www.example.com/myorder?invoice_id=75478385547122078\"}
You must pass your merchant wallets where you would receive instant payouts for the desired networks. EVM wallet is the same for networks (ERC20 - BEP20 - ARBITRUM - AVAX-C - POLYGON - BASE - OPTIMISM - MONAD - LINEA).
fiat_amount and fiat_currency are mandatory for the multi-coin mode.
If you want to disable some blockchain network from the list available to your customer in the multi-coin mode then you just don't include its respective key or value merchant wallet in the POST request body. However at least one wallet is required otherwise no blockchain network can be enabled.
callback: Your website URL where you will receive GET notification after payment is received. You must have at least one unique GET parameter with each request. If you use the same parameter value again the same temporary receiving addresses will be provided in the response. In production use your own unique callback and NOT example.com
payment_token: This is the token to be passed in the next request to initialize the hosted multi-coin payment page https://api.onramp-pay/crypto/hosted.php?payment_token=
callback_url: The callback URL provided with your request for confirmation.
ipn_token: This token is useful when provided to our support team we will be able to track your payment and investigate failed callback events.
By using this endpoint customer will be redirected to a hosted crypto payment checkout page with multi-coin selection. Fiat amount will be converted to the customer selected cryptocurrency and a QR code of the address will be displayed. Optionally you can add the blockchain fees on the customer.
payment_token: You should have this token after passing your payment data in the previous request https://api.onramp-pay/crypto/multi-hosted-wallet.phpadd_fees: Optional parameter if set to 1 blockchain fees will be added to the total payment value so the customer will handle blockchain sending fees.
domain: This is an optional parameter to white-label (rebrand) the hosted multi-coin checkout page with your own custom domain name. You can set your own rebranded subdomain that will replace any instance of api.onramp-pay in the hosted payment page code. The format of this optional parameter value should be like api.example.com and it can be set to be hidden within your cloudflare worker code to prevent manipulation.
logo: urlencoded image URL to be used as the brand logo displayed on the multi-coin crypto checkout page. This is an optional value and it can be for example your own website/brand logo.
background: urlencoded HEX color code to optionally change the background color of the checkout page. Instead of HEX code you may pass direct CSS color naming like green, blue, orange, etc.
theme: urlencoded HEX color code to optionally change the theme color of the checkout page. Instead of HEX code you may pass direct CSS color naming like green, blue, orange, etc.
button: urlencoded HEX color code to optionally change the checkout page button color. Instead of HEX code you may pass direct CSS color naming like green, blue, orange, etc.
The hosted multi-coin mode is an optional integration setup designed for merchants seeking to redirect their customers to one hosted payment page with multi-cryptocurrency options enabled while passing fiat value and currency. End customer will have the ability to select the desired coin for payment, the amount to send + the QR code of the unique receiving wallet address will be displayed on the hosted page. The hosted page will keep checking every minute for confirmed transactions done to the receiving wallet and will compare them to the fiat amount specified by the merchant.
The hosted page is two way encrypted to prevent manipulation from the customer side and the callback links are encrypted so it can't be guessed by the end customer. It can be fully rebranded too by following the custom domain guide.
","_postman_id":"a9e4fc7e-0c2d-437a-b5aa-0c36123d51f5"},{"name":"Affiliate System","item":[{"name":"Affiliate Create Wallet (Default 0.5%)","id":"876aaee5-5851-4495-942a-b09ba86695ea","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://api.onramp-pay/crypto/erc20/usdc/affiliate.php?address=0xF977814e90dA44bFA03b6295A0616a897441aceC&callback=https%3A%2F%2Fwww.example.com%2Forder%3Fnumber%3D821764136280893435&affiliate=0x3c783c21a0383057D128bae431894a5C19F9Cf06","description":"Optionally if you want to white-label (rebrand) our payment
gateway then you can use this affiliate.php endpoint as the first step and pass your
affiliate wallet as an extra affiliate parameter to earn 0.5% commission on every sale. Merchant wallet and affiliate wallet must be different or the request will fail.
The minimum transaction value is higher when setting your affiliate wallet. You may also use the API to fetch minimum transaction values for each coin within the affiliate system.
Create a receiving crypto wallet with a payment notification feature to your website.
Review the ticker identifier for supported coins. (Example: For USDT TRC20 the URL will be https://api.onramp-pay/crypto/trc20/usdt/affiliate.php
Make a GET request to https://api.onramp-pay/crypto/{ticker}/affiliate.php?address={merchant-wallet-address}&callback={urlencoded-callback-url}&affiliate={affiliate-wallet-address}
address: Your merchant wallet address to receive payouts, it must be compatible with the network and coin selected.
callback: Your website URL where you will receive GET notification after payment is received. You must have at least one unique GET parameter with each request. If you use the same parameter value again the same temporary receiving address will be provided in the response. We will add multiple parameters to the request about transaction information: value_coin representing paid crypto value, coin parameter representing coin ticker with underscore format (example: erc20_usdc) and txid_in parameter representing TXID of the customer transaction to the receiving wallet.
affiliate: This wallet will receive 0.5% commission on every sale, it must be compatible with the network and coin selected.
pending: optional parameter for enabling pending (unconfirmed) blockchain transactions callback notifications.
Default value: 0
Set the parameter to pending=1 to enable this feature. When enabled you will be notified of pending transactions (were sent by the customer but not yet confirmed by the blockchain).
Notes: To avoid receiving multiple callback requests, please ensure that the response to the callback request is a plain text response with the message ok.
confirmations: optional parameter to set the number of blockchain confirmations needed before sending a confirmed callback.
Default value: 1
Minimum: 1
Example parameter: confrimations=2
address_in: Newly generated receiving wallet address assigned to the provided callback URL. Any crypto sent to this address will be forwarded instantly to the specified merhant wallet in the original request.
callback_url: The callback URL provided with your request for confirmation.
ipn_token: This token is useful when provided to our support team we will be able to track your payment and investigate failed callback events.
This optional endpoint is for advanced rebranding usage. If you want to rebrand (white-label) and set a custom redistribution of the payout or set a custom commssion fee to yourself as an affiliate then you can optionally use this endpoint to create wallets. This endpoint is similar to the Affiliate endpoint with two extra parameters affiliate_fee and merchant_fee. Those two parameters can be used to distribute percentage of the instant payout to address and affiliate wallets.
affiliate_fee is used to set percentage to the affiliate wallet, if it is set to 0.01 this wallet would receive 1% of the total final payout. merchant_fee is used to set percentage to the address wallet, if it is set to 0.98 then this wallet would receive 98% of the total final payout.
The sum of affiliate_fee and merchant_fee must always be 0.99 as our service fee is 1% of the total payout. If the total is not 0.99 the request would fail.
The minimum transaction value is higher when setting your affiliate wallet. You may also use the API to fetch minimum transaction values for each coin within the affiliate system.
pending: optional parameter for enabling pending (unconfirmed) blockchain transactions callback notifications.
Default value: 0
Set the parameter to pending=1 to enable this feature. When enabled you will be notified of pending transactions (were sent by the customer but not yet confirmed by the blockchain).
Notes: To avoid receiving multiple callback requests, please ensure that the response to the callback request is a plain text response with the message ok.
confirmations: optional parameter to set the number of blockchain confirmations needed before sending a confirmed callback.
Default value: 1
Minimum: 1
Example parameter: confrimations=2
Blockchain fees is higher for the white-label affiliate system because there are payouts to multiple wallets per transaction. You can use this endpoint to get updated blockchain fees when rebranding our gateway.
https://api.onramp-pay/crypto/{ticker}/aff-fees.php
status: If the value is not success then the request was a failure.
estimated_cost: Estimated blockchain fees shown in the main network currency value. For example if you are fetching the estimated blockchain fees for trc20/usdt the value will be displayed as Tron (TRX).
estimated_cost_currency: The estimated blockchain fees calculated in fiat currencies for easier conversion.
You can use this endpoint to get the coin name, minimum transaction value and fiat converted values for the affiliate system. You don't need to pass any GET parameters for this request. Only the
ticker path is required. The affiliate minimum is the coin minimum multiplied by 1.255 and by using this endpoint you will get the coin minimum transaction value already calculated per the affiliate system.
https://api.onramp-pay/crypto/{ticker}/aff-info.php
coin: The name of the coin
minimum: The minimum transaction value of the coin that can be sent to the generated wallet address. Any sent amount below the minimum will be stuck in the generated address forever as it is less than required fees to process your forwarding transaction.
prices: Fiat converted value prices of the coin in different currencies.
You don't need to pass any GET parameters with this endpoint. It will return all supported networks with nested coins in JSON format listing coin name, identifier (ticker), logo and minimum transaction value (minimum_transaction_coin) for the affiliate system.
The affiliate endpoints will allow you integrating the same crypto payment system while setting an extra affiliate wallet for earning. The default endpoint will set the commission to 0.5% per transaction while you can use the custom affiliate endpoint to set your own percentage commission on every transaction. The custom affiliate commission endpoint may have other use cases like integrating a crypto payment system with unique generated receiving wallets that would forward any received crypto automatically to two specified wallets with a preset percentage distribution.
Individuals and companies who would like to white-label or instantly rebrand and earn this crypto payment system while setting their own custom commission may follow the custom domain guide for a more simple and quick rebranding.
","_postman_id":"047a8fb5-09e5-401c-b904-484f9e84c7df"},{"name":"Convert Fiat Value to Crypto","id":"2ad6adb6-2a5f-4060-a530-1f90cad9d81e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://api.onramp-pay/crypto/btc/convert.php?from=usd&value=109.78","description":"Make this request to convert the fiat value for example (USD, EUR or GBP) to the desired crypto value to show your customer how much crypto they have to send.
To display crypto amount to be paid by your customer make a GET request to https://api.onramp-pay/crypto/{ticker}/convert.php?from={fiat-currency}&value={fiat-value}.
from: The fiat currency to convert from.
value: The value amount of fiat currency to convert.
status: If the value is not success then the fiat currency is unsupported for conversion. You can conctact support to add it for you.
value_coin: The crypto value after conversion.
exchange_rate: The fiat to crypto exchange rate.
Generate a QR image code for your payment wallet address.
address: Wallet address_in generated through initial create wallet request.
amount: Optional parameter to include the crypto amount to be paid in the generated QR code. The optional amount parameter might not be compatible with many exchanges and wallets. While it works with Trust Wallet and Exodus wallet, some user wallets or exchanges may only read the address and ignore the amount field. Hence, it is advised to use the amount parameter cautiously and be aware that it may not be recognized by all wallets and exchanges, causing some confusion to the end customer.
status: If the value is not success then the request was a failure.
qr_code: This is the base64 code for the image. Should be used in HTML like this: <img src=\"data:image/png;base64,{qr_code}\" alt=\"Payment QR Code\"/>
payment_uri: The wallet address provided with the request.
When a payment is made by the customer our bot will visit your callback URL using GET request method. All your original parameters will be included plus the following payment data parameters:
value_coin: Amount of crypto paid by the customer.
coin: Paid coin and network type in the format network_coin, for example btc or polygon_usdt or erc20_usdc and so on
txid_in: TXID of the payment made from the customer to the order assigned wallet.
txid_out: Instant payout TXID from the order assigned wallet to your merchant predefined wallet.
address_in: This should match the same address_in wallet generated at the first step.
value_forwarded_coin: Total crypto amount forwarded from the order assigned wallet to the merchant and affiliates.
pending: If the callback request is for a pending callback (unconfirmed blockchain transaction) the value will be pending=1 which is an optional feature that can be enabled during first step when creating the receiving wallet. Confirmed callback will have parameter value pending=0
Use this endpoint to check the payment status.
Warning: This endpoint is intended to be used on casual basis only to check the payment status and TXID info when needed. However you shouldn't rely on this endpoint to change order status on your own website/system to avoid getting rate limited. To change order status within your own website system you should rely on the Callback Event where our bot will hit your server when the payment is made.
ipn_token: You should have this already from the first request when creating the wallet.
ticker: urlencoded ticker so for example bep20/usdt should be bep20%2Fusdt.
status: This can be either paid or unpaid.
value_coin: crypto value sent by the customer to the generated receiving wallet address.
txid_in: The blockchain TXID of the transaction sent from the customer to the receiving address (temporary wallet).
txid_out: The blockchain TXID of the payout from the generated receiving wallet to the merchant wallet.
coin: The crypto coin type sent by the customer and payout.