Authorization

The Authorization steps for a Guest Payment are basically identical for all payment options.

1. Initiate Authorization
2. Collect Payment Option Details via the SDK
3. Complete Authorization

Nevertheless there can be minor differences and additional steps depending on the chosen payment option. For that reason, we provide a detailed description of the authorization process for each payment option group respectively.

Transaction Status Handling for Non-Successful Reponse Codes

The following guide provides details on handling non-successful response codes in authorization requests.

info

When a payment authorization request returns a responseCode other than 0000, the transaction status in the statusCode parameter should be evaluated to determine the appropriate next steps. Merchants must analyze the status code for additional details, which requires calling the 1.41 Get Payment Status API in case of guest payments. Based on this analysis, merchants should implement additional business logic accordingly.

The following transaction statuses can be used to implement in your own processing logic, as they are returned in the statusCode parameter of 1.41 API responses:

• Authorized: The merchant can proceed to 1.29 Capture.
• Captured: The payment has been fully processed, and no further action is required.
• Expired: The user did not complete the checkout flow. The merchant should prompt the customer to restart the payment process.
• Failed: Authorization failed at the provider's end. The merchant should inform the customer and possibly offer alternative payment methods.
• Received: The merchants should trigger 1.39 Complete Authorize again.
• Settled: The payment has been sucessfully processed and will be included in the next payout cycle.