TWINT
Last updated
Was this helpful?
Last updated
Was this helpful?
This chapter will handle all specifics involved with the integration of the payment method TWINT.
A and thus a valid identification with a username and password for the Saferpay system.
At least one active Saferpay terminal via which payment can be carried out and the associated Saferpay TerminalId.
A valid TWINT contract
The general integration of TWINT can be done via the -However other features require a different path. See further down in this chapter- and requires the following things to be noted:
JSON API Version 1.7 or later.
Unlike normal credit card transactions, where a could be attempted after the normal reservation time, TWINT does only offer a maximum timeframe of 7 days! After that the transaction will be discarded and a will not initiate the money-transfer with the next batch-close, so make sure, to your transactions within this time limit!
In justified cases, this period can be extended to 30 days. Please inform our sales department and for more information.
Saferpay does support. However, one of the available options must be explicitly activated on our side. For more information about different "Pay later" options and their configuration, please contact our sales department.
The parameter OrderId
is limited to 50 characters.
Due to processing limitations, a refund can fail, if it is executed earlier than two hours after the initial transaction. The initial transaction needs to be processed first, until a refund can be executed, which happens within said two hours!
The notification URLs, inside theNotification
container are mandatory, in order to avoid missing payment successes. See the for further information.
Feature
Support
✅
Multipart Captures
❌
Secure Card Data
✅
✅
Recurring Payments
✅
3D Secure
❌
Dynamic Currency Conversion (DCC)
❌
Mail Phone Order
❌
✅
✅
The following requirements are to be met, if Twint User on File is to be used, aside the normal requirements:
JSON API Version 1.14 or later
The RedirectUrl then needs to be opened inside an iFrame, as a redirect, or lightbox. Saferpay will then present the following screen.
Once this process is done, the user gets redirected towards one of the previously defined ReturnUrls, depending on the outcome.
One speciality with Twint User on File is, the Twint.CertificateExpirationDate parameter. Each registered Twint payment mean, will have its own expiration date within the Twint system, which does not correspond with the Saferpay Alias Lifetime! The parameter will return the expiration date of this registration certificate. Once it has passed, the Twint alias becomes invalid.
Furthermore note, that using RANDOM_UNIQUE will always return the already existing alias, even if it is expired on Twint side. While it can serve as a mean to filter out already existing customers and thus help preventing double-registrations, you must keep this in mind. Should you get a rejection saying, that the alias has expired on Twint side, you must first delete the old alias, before your customer can re-register.
If you are integrating Twint inisde a web-view, you may have to specifically configure your view, in order for the Twint app to open.
Here is example-code on how this is achieved.
/
Twint User on File saves Twint payment means inside the , allowing you to execute subsequent/recurring transactions on a users Twint account.
A valid license with access to the .
One of the ways to register a Twint account into Secure Card Data, is via the . Simply follow the standard flow there.
A Twint user can reject the User On File registration during a payment. If that is the case, Saferpay will return a successful transaction, but a failed registration. Please make sure, that you are able to.
The Standalone Registration is done via the . Within the , you need to specify the parameter Type with the value TWINT, which signals, that you want to save Twint payment means.
The merchant system then needs to execute the , in order to gather the alias and other important payment mean details.
Once you have obtained the alias, you can go ahead and execute your recurring/subsequent transaction using the . The alias is set within the PaymentMeans.Alias
container, but remember, that this transaction, like all Twint transactions, also must be for the money to flow.
Please refer to , if you want to test TWINT.