2.2 Push event
Merchant needs to prepare the API to receive the push event from HyperCardAPI. After prepared the API, merchant need to register the API at the merchant platform.
In order to secure the data, merchant need to perform data signature validation for each push event. Merchant need to use same method as request signature to get the push event signature.
Business Category Guide
Push events are divided into the following categories based on business type. Please refer to the corresponding documentation based on your business needs:
| Business Type | Documentation Link | Description |
|---|---|---|
| Card Business | 2.2.4 Common (Card Business) | Includes card opening, recharge, card operation, card transaction, purchase crypto coin, cancel card, 3DS auth, verification code, card config change, card status change, transaction data change, correction charge notifications |
Retry Mechanism
If we not receive code=1, we will retry, Retry Interval: If there is no success after 24 hours, we will not try again to save resources.
| times | Time interval from last time |
|---|---|
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 30 minutes |
| 5 | 60 minutes |
| 6 | 2 hours |
| 7 | 4 hours |
| 8 | 12 hours |
| 9 | 24 hours |