⚙️Using your own UI with Inqud processing
For more sophisticated and adaptable solutions
Last updated
For more sophisticated and adaptable solutions
Last updated
Your business account with Inqud is set up, complete with API tokens configured.
The Crypto Widget has been established and configured within the Inqud platform.
The Crypto Widget is active.
Request web-hook is configured.
Visit the Requests page to learn more about the various request statuses.
Get Deposit Options API Reference
Request Example:
GET https://api.inqud.com/v1/user/crypto-acquiring/{widgetId}/deposit-options
Header | Value |
---|---|
X-Token-API-Id | {tokenApiId} |
X-Token-API-Secret | {tokenApiSecret} |
Request Example:
projectId
is the ID of the widget
Header | Value |
---|---|
X-Token-API-Id | {tokenApiId} |
X-Token-API-Secret | {tokenApiSecret} |
Request Body Example:
Response Example:
The following fields in the response are the most important:
Column | Desciption |
---|---|
currency | Currency of payment |
blockchain | Blockchain of payment |
address | The address end user should pay to |
paymentWindowEndsAt | This timestamp is provided to the user to indicate the payment window's closure. However, Inqud makes a slight extension beyond this time to accommodate potential delays in the blockchain network. |
payAmount | This represents the amount the user is expected to pay. The user has the option to pay this exact amount or more. However, if the payment is less than the expected amount, the request will be flagged as CONFLICT/UNDERPAID. |
The response example provided is a shortened version and does not include the full set of fields. For the complete response body details, please refer to the full API specification.