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
{{ message }}
This repository was archived by the owner on Sep 13, 2022. It is now read-only.
The documentation should explain the recommended client behavior when the user wishes to retry a payment. E.g. should a new payment be always created (with a different stamp), or can the client store the original response so it can re-show the buttons later, or something else?
The legacy API contained the paymentURL field which allowed retries by directing the user there, but I do not see similar functionality in the new API. Unless it is the "href": "https://api.checkout.fi/pay/80621392" field in the example response which seems to not be documented?
(client = merchant server, user = merchant's customer)
The documentation should explain the recommended client behavior when the user wishes to retry a payment. E.g. should a new payment be always created (with a different stamp), or can the client store the original response so it can re-show the buttons later, or something else?
The legacy API contained the paymentURL field which allowed retries by directing the user there, but I do not see similar functionality in the new API. Unless it is the
"href": "https://api.checkout.fi/pay/80621392"field in the example response which seems to not be documented?(client = merchant server, user = merchant's customer)