The server to sever callback url is not mandatory to generate a order. Anyway, our tip is to implement it, it is a very simple process.

When a payment is confirmed we will redirect back the user to your confirmation or error page. It may happen that the user closes the page before the redirect or that there are connections problem while redirecting.

The s2s callback resolves this problem. If you provide a valid s2sNotificationUrl while creating the order we will send you the up to 5 times in the range of 10 minutes a GET request with the last known state of the payment.

This way, even if something goes wrong with the redirect process you will always be informed about the outcome.

What if my server is offline during the s2s callback timeframe?

We will try to notify you up to 5 times in the range of 10 minutes.

We expect you to send us a 200 or 201 HTTP response. If for some reason we do not receive any response in the given time range we will send an email to you with the warning and the status of the payment.

Parameters of the s2s request

The S2S GET request will contain some parameters to indicate the current status of the payment

ParameterMeaning
paymentIdentifierThe identifier of the bank
merchantTransactionIdYour internal order reference
tokenThe credit card token, by default is null - if you need it ask during the integration
panThe credit card digits, by default is null - if you need it ask during the integration
currencyThe payment currency
totalThe total amount of the payment
statusStatus of the payment, it can be AUTHENTICATED, DECLINED, CANCELED, CAPUTRED*

* captured and authenticated are the same, it means that the payment is ok
successTrue or false, is true of the payment was success
operationIdentifierIn case of a order with multiple operations there will be the id of the current operation (generated by us or provided by you)
travelProtectionIn case of a order with travel protection enabled you will receive this parameter with the value of "true"