About TWINT
General information about TWINT
TWINT is the leading and one of the most popular payment app in Switzerland. Ninety-seven percent of the Swiss population are aware of TWINT and half of the Swiss population uses it on a regular basis. Ninety percent of all bank account holders in Switzerland are able to connect their accounts directly to the TWINT app.
Please note: In order for a merchant to receive a TWINT account, he must be able to show that his company is based in Switzerland.
Logo |
|
|---|---|
Info | Pay easily and absolutely secure with the TWINT E-Wallet solution using the leading payment app in Switzerland. All you need to do is to scan a QR code and verify your identify using your smartphone. |
Type |
Further information you will find also on the TWINT webpage (https://www.twint.ch/).
How it works
When a user decides to pay with TWINT and taps corresponding payment button, either QR is presented for user to scan (Web payment) or TWINT app opens automatically to confirm payment (in-app payment or browsing on smartphone).
Please follow next link for overview how to pay online with TWINT:
https://www.twint.ch/en/private-customers/functions/onlineshop/?lang=en
Before you start
Once you have decided to support TWINT, there's a set of steps have to be completed:
Register your company within TWINT here: https://portal.twint.ch.
If you'd like to have a test merchant and perform TWINT transaction in test mode, you can also register you company and create a shop on TWINT's integration environment https://portal-int.twint.ch the same way as described below.
Create your Online shop from the home page of TWINT portal:
On the second step of the shop registration in the "Integration" section choose PSP (payment service provider) option and select Computop from the list of providers:Â
After store has been created, provide store's UUID to Computop Helpdesk and ask to activate payment method TWINT:
Process flow chart
Use Cases
Supported use cases | Supported interfaces | |||||||
|---|---|---|---|---|---|---|---|---|
Use case | Description | Simple process | S-2-S | Form-based | Batch | Analytics | HPP | CTSF |
PAYMENT_DEFERRED for physical goods Authorization + Capture | Merchant wants to authorize payment and capture on delivery |
|  | Â | | |||
PAYMENT_IMMEDIATE for digital goods Sale | Merchant wants to collect money from customer |
| | | ||||
full or partial Credit | Merchant wants to credit some money back to customer after a payment has been successfully completed |
|
|
| ||||
full or partial Reversal | Merchant wants to cancel a payment which has not been completed |
| | Â | ||||
| CTSF | CTSF for reconcilliation |
| coming soon | |||||
On this page
Paygate interface
Format Description a alphabetical as alphabetical with special characters n numeric an alphanumeric ans alphanumeric with special characters ns numeric with special characters bool boolean expression (true or false) 3 fixed length with 3 digits/characters ..3 variable length with maximum 3 digits/characters enum enumeration of allowed values dttm ISODateTime (YYYY-MM-DDThh:mm:ss) Abbreviation Description CND condition M mandatory O optional C conditional Notice: Please note that the names of parameters can be returned in upper or lower case.Definitions
Data formats
Abbreviations
Comment If a parameter is mandatory, then it must be present If a parameter is optional, then it can be present, but it is not required If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional
Payment with TWINT over Paygate form interface
To make a TWINT payment over Paygate form, please use the following URL:
https://www.computop-paygate.com/twint.aspx |
Â
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for TWINT
The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system: pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
 Please note that the final notification may be delayed by approx. 30-35 minutes or up to 60-65 minutes if the customer completes the payment and closes the browser immediately afterwards. The reason for this is that the payment status can only be read in via the browser callback and if this is not done, the status is requested downstream by our Paygate at the above-mentioned interval. Due to the missing callback, the redirect to the URLSuccess/URLFailure is also not processable.
Return parameters for URLSuccess, URLFailure and URLNotify with TWINT
Â
Capture
If your Computop MID isn't configured for Sale operation, every initial TWINT payment (call to twint.aspx) should be confirmed using capture.aspx endpoint or canceled via reverse.aspx.
Captures (or confirmations in terms of TWINT) are possible via a Server-to-Server connection. To carry out a Capture via a Server-to-Server connection, please use the following URL:
https://www.computop-paygate.com/capture.aspx |
Â
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for captures with TWINT via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Response parameters for captures with TWINT via socket connection
Reversal
Reversals are possible via a Server-to-Server connection. In order to cancel a payment via a server-to-server communication, please use the following URL:
https://www.computop-paygate.com/reverse.aspx |
Â
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for reversals with TWINT via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Response parameters for reversals with TWINT via socket connection
Credit with reference
Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture the amount of the Credit is limited to the amount of the previous capture. To carry out a credit with a reference transaction, please use the following URL:
https://www.computop-paygate.com/credit.aspx |
Â
Notice: Please note that TWINT limits refunds in the production environment as well as on the test system – production mode: 180 days / test mode: 7 days.
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for credit payments with TWINT via socket connection
Â
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Response parameters for credit payments with TWINT via socket connection
Â
Batch processing via the interface
Basic information about using Batch files and about their structure can be found in the Batch Manager manual. Within batch processing not alle functions are available which are usually available for the online interface.
This section describes the parameters which must be transferred within the data set (Record) for executing a Twint payment and information can be found within the response file about the payment status.
For Batch calls there must be considered batch versions, from which optional parameters depend. All version designations starting with „2.“ pertain calls for a group of enterprises. That means within a batch file for a particular MerchantID can be transferred transactions for other merchants with a separate Sub-MID
Following table gives an overview of all batch versions that are possible for a specific action an their specialities:
Description of the possible batch versions
The structure for a Twint payment within a Batch file to be submitted is as follows:
HEAD,<MerchantID>,<Date>,<Version> Twint,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> Twint,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> Twint,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> FOOT,<CountRecords>,<SumAmount>
Example for Master MID function:
HEAD,[Master]MerchantID,Date,2.x Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action) FOOT,CountRecords,SumAmount
The following table describes the individual fields and values used within the data set (record) in the batch file:
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
HEAD,<MerchantID>,<Date>,<Version> Twint,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> Twint,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> Twint,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> FOOT,<CountRecords>,<SumAmount>
Description of result parameters within the record for Batch files