You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/events/crypto-offramp.mdx
+105Lines changed: 105 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ import TabItem from '@theme/TabItem';
13
13
|[`order:crypto-offramp:funds-sent`](#ordercrypto-offrampfunds-sent)| User has sent funds for their order. |
14
14
|[`order:crypto-offramp:funds-received`](#ordercrypto-offrampfunds-received)| User has sent funds for their order and we have received them. |
15
15
|[`order:crypto-offramp:completed`](#ordercrypto-offrampcompleted)| User's order has completed. |
16
+
|[`order:crypto-offramp:expired`](#ordercrypto-offrampexpired)| Transaction was abandoned actively or passively by the user. |
16
17
|[`order:crypto-offramp:failed`](#ordercrypto-offrampfailed)| User's order has failed. |
17
18
|[`order:crypto-offramp:refund:completed`](#ordercrypto-offramprefundcompleted)| User's order has been successfully refunded. |
18
19
@@ -428,6 +429,110 @@ The values for `destination.paymentMethod.type` can be found using our [REST API
428
429
</TabItem>
429
430
</Tabs>
430
431
432
+
## `order:crypto-offramp:expired`
433
+
434
+
Triggered when a transaction status is `expired`. This means the transaction was abandoned actively or passively by the user (`cancelled`, `expired`, `abandoned` or `pending`).
435
+
436
+
<Tabs>
437
+
<TabItemlabel="Schema"value="schema"default>
438
+
439
+
-`id`: UUID of the order.
440
+
-`status`: Status of the order (`expired`).
441
+
-`createdAt`: Timestamp at which the order was created.
442
+
-`updatedAt`: Timestamp at which the order was last updated.
443
+
-`origin`: Object containing information about what the user would have sent.
444
+
-`amount`: Amount the user would have sent.
445
+
-`rate`: Rate used to calculate the amount.
446
+
-`asset`: Cryptoasset the user would have sent.
447
+
-`network`: Network of the sending asset.
448
+
-`depositAddress`: Object containing information related to the deposit.
449
+
-`expiresAt`: Timestamp at which the deposit expires.
450
+
-`remindAt`: Timestamp at which the user is reminded.
451
+
-`tag`: Tag of the crypto transaction, used to complement the address.
452
+
-`type`: Tag type.
453
+
-`value`: Tag value.
454
+
-`value`: Address to which the user sends the funds.
455
+
-`destination`: Object containing information about what the user would have received.
456
+
-`amount`: Amount the user would have received.
457
+
-`rate`: Rate used to calculate the amount.
458
+
-`asset`: Currency code in the [ISO 4217](https://www.iso.org/iso-4217-currency-codes.html) format used to receive the funds.
459
+
-`paymentMethod`: Object containing information about the payment method used.
460
+
-`type`: Type of payment method.
461
+
-`fees`: Array containing fees associated with the order.
462
+
-`amount`: Amount user was charged for this fee.
463
+
-`asset`: Asset used to charge the fee.
464
+
-`normalized`: Amount in USD that the user was charged for this fee.
465
+
-`type`: Type of fee (`network`, `deposit` or `partner`).
466
+
-`widget`: Widget associated with the session.
467
+
-`id` UUID of the widget.
468
+
-`name`: Name of the widget.
469
+
-`flow`: Flow associated with the widget.
470
+
471
+
:::note
472
+
The values for `destination.paymentMethod.type` can be found using our [REST API](../rest-api.md), via the [payment methods endpoint](https://api.topperpay.com/payment-methods/crypto-offramp).
Copy file name to clipboardExpand all lines: docs/events/crypto-onramp.mdx
+104Lines changed: 104 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ import TabItem from '@theme/TabItem';
13
13
|[`order:crypto-onramp:charged`](#ordercrypto-onrampcharged)| User has been charged for their order. |
14
14
|[`order:crypto-onramp:crypto-sent`](#ordercrypto-onrampcrypto-sent)| User's crypto delivery has started. |
15
15
|[`order:crypto-onramp:completed`](#ordercrypto-onrampcompleted)| User's order has completed. |
16
+
|[`order:crypto-onramp:expired`](#ordercrypto-onrampexpired)| Transaction was abandoned actively or passively by the user. |
16
17
|[`order:crypto-onramp:failed`](#ordercrypto-onrampfailed)| User's order has failed. |
17
18
|[`order:crypto-onramp:refund:completed`](#ordercrypto-onramprefundcompleted)| User's order has been successfully refunded. |
18
19
@@ -443,6 +444,109 @@ The values for `origin.paymentMethod.type` can be found using our [REST API](../
443
444
</TabItem>
444
445
</Tabs>
445
446
447
+
## `order:crypto-onramp:expired`
448
+
449
+
Triggered when a transaction status is `expired`. This means the transaction was abandoned actively or passively by the user (`cancelled`, `expired`, `abandoned` or `pending`).
450
+
451
+
<Tabs>
452
+
<TabItemlabel="Schema"value="schema"default>
453
+
454
+
-`id`: UUID of the order.
455
+
-`status`: Status of the order (`expired`).
456
+
-`createdAt`: Timestamp at which the order was created.
457
+
-`updatedAt`: Timestamp at which the order was last updated.
458
+
-`origin`: Object containing information about how the user would have paid.
459
+
-`amount`: Amount the user would have paid.
460
+
-`rate`: Rate used to calculate the amount.
461
+
-`asset`: Currency code in the [ISO 4217](https://www.iso.org/iso-4217-currency-codes.html) format used to make the payment.
462
+
-`paymentMethod`: Object containing information about the payment method used.
463
+
-`type`: Type of payment method.
464
+
-`destination`: Object containing information about what the user would have received.
465
+
-`amount`: Amount the user would have received.
466
+
-`rate`: Rate used to calculate the amount.
467
+
-`asset`: Cryptoasset the user would have received.
468
+
-`network`: Network of the receiving asset.
469
+
-`address`: Recipient wallet address.
470
+
-`tag` (_optional_): Tag of the crypto transaction, used to complement the `address`.
471
+
-`type`: Tag type (e.g.: `memo` or `destination-tag`).
472
+
-`value`: Tag value.
473
+
-`priority` (_optional_): Priority of the crypto transaction.
474
+
-`fees`: Array containing fees associated with the order.
475
+
-`amount`: Amount user was charged for this fee.
476
+
-`asset`: Asset used to charge the fee.
477
+
-`normalized`: Amount in USD that the user was charged for this fee.
478
+
-`type`: Type of fee (`network`, `deposit` or `partner`).
479
+
-`widget`: Widget associated with the session.
480
+
-`id` UUID of the widget.
481
+
-`name`: Name of the widget.
482
+
-`flow`: Flow associated with the widget.
483
+
484
+
:::note
485
+
The values for `origin.paymentMethod.type` can be found using our [REST API](../rest-api.md), via the [payment methods endpoint](https://api.topperpay.com/payment-methods/crypto-onramp).
Copy file name to clipboardExpand all lines: docs/webhooks.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,7 @@ Full information about the available events and their associated payloads can be
32
32
|[`order:crypto-onramp:charged`](./events/crypto-onramp.mdx#ordercrypto-onrampcharged)| User has been charged for their order. |
33
33
|[`order:crypto-onramp:crypto-sent`](./events/crypto-onramp.mdx#ordercrypto-onrampcrypto-sent)| User's crypto delivery has started. |
34
34
|[`order:crypto-onramp:completed`](./events/crypto-onramp.mdx#ordercrypto-onrampcompleted)| User's order has completed. |
35
+
|[`order:crypto-onramp:expired`](./events/crypto-onramp.mdx#ordercrypto-onrampexpired)| Transaction was abandoned actively or passively by the user. |
35
36
|[`order:crypto-onramp:failed`](./events/crypto-onramp.mdx#ordercrypto-onrampfailed)| User's order has failed. |
36
37
|[`order:crypto-onramp:refund:completed`](./events/crypto-onramp.mdx#ordercrypto-onramprefundcompleted)| User's order has been successfully refunded. |
37
38
@@ -43,6 +44,7 @@ Full information about the available events and their associated payloads can be
43
44
|[`order:crypto-offramp:funds-sent`](./events/crypto-offramp.mdx#ordercrypto-offrampfunds-sent)| User has sent funds for their order. |
44
45
|[`order:crypto-offramp:funds-received`](./events/crypto-offramp.mdx#ordercrypto-offrampfunds-received)| User has sent funds for their order and we have received them. |
45
46
|[`order:crypto-offramp:completed`](./events/crypto-offramp.mdx#ordercrypto-offrampcompleted)| User's order has completed. |
47
+
|[`order:crypto-offramp:expired`](./events/crypto-offramp.mdx#ordercrypto-offrampexpired)| Transaction was abandoned actively or passively by the user. |
46
48
|[`order:crypto-offramp:failed`](./events/crypto-offramp.mdx#ordercrypto-offrampfailed)| User's order has failed. |
47
49
|[`order:crypto-offramp:refund:completed`](./events/crypto-offramp.mdx#ordercrypto-offramprefundcompleted)| User's order has been successfully refunded. |
0 commit comments