Scenario Examples

This section will highlight some of the scenarios that result in a change of transaction status. Your operations team can track and manage the payment history and payouts based on the messages from the callback URL, getCompletedPayment API endpoints or through the Aquapay web portal.

Table of Contents

1. User does not send cryptocurrency to the deposit address after initiating payment request

2. User sends cryptocurrency within the payment required time period

3. User sends cryptocurrency after the payment request is expired

4. User sends cryptocurrency with quantity larger than deposit limit

5. AML/Risk Check fails for the deposit transaction

6. Price moved beyond our volatility threshold

Scenario 1

User does not send cryptocurrency to the deposit address after initiating payment request

Condition End-user did not send the cryptocurrency to the corresponding deposit address. Result Since there is no transaction, no message is sent to the webook URL and the user balance does not change. Action Required None

Scenario 2

User Sends Cryptocurrency Within The Payment Required Time Period

Condition End-user's cryptocurrency transfer was broadcasted onto the blockchain to the corresponding deposit address within the required deposit time. Result Once the transaction reaches the required number of confirmations, Aquapay will accept the deposit and convert the cryptocurrency to fiat with the price associated with this deposit. Action Required Completed transaction message is sent through the webook URL and clients can use the message to update their systems accordingly.

Scenario 3

User Sends Cryptocurrency After The Payment Request Is Expired

Condition End-user's cryptocurrency transfer was broadcasted onto the blockchain to the corresponding deposit address after the required deposit time. Result Cryptocurrency deposit is accepted by Aquapay after required confirmation, but the cryptocurrency will be deposited to your balance without converting to fiat. Action Required Rejected transaction message is sent through the webook URL and clients can use the message to update their system accordingly.

Scenario 4

User Sends Cryptocurrency With Quantity Larger Than Deposit Limit

Condition End-user's cryptocurrency transfer was broadcasted onto the blockchain to the corresponding deposit address after the required deposit time with quantity larger than the deposit limit. Note that the deposit limit is configurable and there is no limit by default. Result Cryptocurrency deposit is accepted by Aquapay after required confirmation, but the cryptocurrency will be deposited to the user balance and will not be converted to fiat. Action Required Rejected transaction message is sent through the webook URL and clients can use the message to update their system accordingly.

Scenario 5

AML / Risk Check Fails for the Deposit Transaction

Condition We monitor any incoming deposit using our in-house risk check system and the transaction fails our risk measure. Result Cryptocurrency deposit is accepted by Aquapay after required confirmation, but the cryptocurrency will be deposited to the user balance and will not be converted to fiat. Action Required Rejected transaction message is sent through the webook URL and clients can use the message to update their system accordingly and we recommend to ask user to provide a refund address and send the cryptocurrency back.

Scenario 6

Price Moved Beyond Our Volatility Threshold

Condition While Aquapay locks the trading price to give user enough time to transfer the cryptocurrency, during the high volatility period if the price when the transaction is confirmed is 2.5% lower than the locked price, it will hit the volatility threshold. Result Cryptocurrency deposit is accepted by Aquapay after required confirmation, but the cryptocurrency will be deposited to the user balance and will not be converted to fiat. Action Required Rejected transaction message is sent through the webook URL and clients can use the message to update their system accordingly.