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. In production use your own unique URL and NOT example.comvalue_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. Those will be added after your existing unique GET parameters in the callback URL.pending: optional parameter for enabling pending (unconfirmed) blockchain transactions callback notifications.0pending=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).ok.confirmations: optional parameter to set the number of blockchain confirmations needed before sending a confirmed callback.11confrimations=2address_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.curl --location '/crypto/erc20/usdc/wallet.php?address=bc1qx9t2l3pyny2spqpqlye8svce70nppwtaxwdrp4&callback=https%3A%2F%2Fwww.example.com%2Fmyorder%3Finvoice_id%3D75478385547922074'{
"address_in": "3KCktixcBTWtvLSiUosrW4jTVS1e1wwSbU",
"callback_url": "https://www.example.com/myorder?invoice_id=75478385547922074",
"ipn_token": "ZEE2cW8zb1N0N2otZEc3eHh3MDNUU1lTMEExYmVvcDBVYTRMczVxS2JVWGJWUnVqaUwtNEtPdHZtNm5ORkdKTHZMQTRmUUxTZF9td1NjM0Q%3D"
}