PaymentPage
Call this function to safely check the status of the transaction from your server, either after the payer was redirected back to your shop or your shop system received the server-to-server notification call.
Important:
Do not poll this function! Wait until the payer is redirected back to the shop or until the notification was called (we strongly recommend using the notification feature).
Depending on the payment provider, the resulting transaction may either be an authorization or may already be captured (meaning the financial flow was already triggered). This will be visible in the status of the transaction container returned in the response.
This function can be called up to 24 hours after the transaction was initialized. For pending transaction the token expiration is increased to 120 hours.
If the transaction failed (the payer was redirected to the Fail url or he manipulated the return url), an error response with an http status code 400 or higher containing an error message will be returned providing some information on the transaction failure.
post
Authorizations
AuthorizationstringRequired
Basic authentication with your Saferpay API user credentials.
Body
Responses
200Success
application/json
Responseone of | nullable
post
/Payment/v1/PaymentPage/Assert200Success
This method can be used to start a transaction with the Payment Page which may involve either DCC and / or 3d-secure
post
Authorizations
AuthorizationstringRequired
Basic authentication with your Saferpay API user credentials.
Body
Responses
200Success
application/json
Responseone of | nullable
post
/Payment/v1/PaymentPage/Initialize200Success
Last updated
Was this helpful?
