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/subscriptions/one-off-payments.md
+25-22
Original file line number
Diff line number
Diff line change
@@ -169,28 +169,31 @@ Once the one-off payment status changes from *Requested* to *Reserved*, *Rejecte
169
169
|Expired |_1. One-off payment was neither accepted, nor rejected by user. 2. User didn't any action after the automatic reservation failed._| 1 day after you requested one-off payment |Expired|Expired by the system.| 50008 |
170
170
|Requested |_The automatic reservation of a one-off payment failed. User action is needed._| Right after the automatic reservation has failed |Requested|Automatic reservation failed. User action is needed.| 50013 |
171
171
172
-
### Callbacks about one-off and Agreement
173
-
174
-
You will get callbacks about the payment to your callback address. Moreover, you will get callbacks about the agreement to either success or failure URL, that you have set upon agreement creation. However, unless a one-off payment automatic reservation fails, you will not get callbacks for either, before their status changes. So you should expect a callback when the agreement is *accepted* / *rejected* / *expired* and a callback when the OneOff is either `accepted`/`rejected`/`expired`. If the one-off payment's automatic reservation fails, then the status of the one-off payment will not change, but a callback about the event will be sent.
175
-
176
-
The response for agreement creation, on the other hand, consists of both agreement and OneOff.
0 commit comments