1. About TWINT (via PPRO)

1.1 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:

Further information you will find also on the TWINT webpage (https://www.twint.ch/).

1.2 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

1.3 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.

1.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.

2. Create your Online shop from the home page of TWINT portal:

3. 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: 

4. After store has been created, provide store’s UUID to the First Cash Solution and ask to activate payment method TWINT:

1.4 Process flow chart

1.5 Use Cases

Supported use cases			Supported interfaces
Use case	Description	Simple process	S-2-S	Form-based	Batch	Analytics PayByLink	HPP	CTSF
Authorization + Capture	Merchant wants to authorize payment and capture on delivery	Merchant has to complete capture within 7 days after authorization
Sale	Merchant wants to collect money from customer	Merchant’s shop initiates payment requestCustomer gets redirected to get QR code displayedCustomer scans QR-Code and confirms paymentMerchant’s shop gets a notification about successful payment
full or partial Credit	Merchant wants to credit some money back to customer after a payment has been successfully completed	Merchant initiates credit requestComputop collects details from referred payment and initiates creditMerchant’s shop gets a notification about successful credit
full or partial Reversal	Merchant wants to cancel a payment which has not been completed	only supported for payment processes that have not been completedfor completed payment processes use Credit instead
CTSF	CTSF for reconcilliation	download settlement file from service providercreate CTSF for merchant						coming soon

2 1cs Online Paymentsystem-interface

2.1 Definitions

Data forms:

Abbrevations:

Notice: Please note that the names of parameters can be returned in upper or lower case.

2.2 Payment with TWINT over 1cs Online Paymentsystem

To make a TWINT payment over 1cs OPS form, please use the following URL:

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:

The following table gives the result parameters which 1cs OPS 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. MerchantId, RefNr) should not be checked case-sentive

2.3 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:

Notice: For security reasons, 1cs OPS 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:

The following table gives the result parameters which 1cs OPS 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. MerchantId, RefNr) should not be checked case-sentive

2.4 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:

Notice: For security reasons, 1cs OPS 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:

2.5 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:

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, 1cs OPS 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:

The following table describes the result parameters which 1cs OPS 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. MerchantId, RefNr) should not be checked case-sentive

3. 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: