TWINT (via PPRO)
1.1 General information about TWINT
2 1cs Online Paymentsystem interface
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:
| Info | Type |
| 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. | Payments by Wallet |
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:
| 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) |
Abbrevations:
| Abbreviations | Description | Comment |
|---|---|---|
| CND | condition | |
| M | mandatory | If a parameter is mandatory, then it must be present |
| O | optional | If a parameter is optional, then it can be present, but it is not required |
| C | conditional | If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional |
Notice: Please note that the names of parameters can be returned in upper or lower case.
2.2 Payment with TWINT via PPRO
To make a TWINT payment via PPRO over 1cs OPS form, please use the following URL:
| https://www.computop-paygate.com/TWINTPP.aspx |
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:
| Key | Format | CND | Description |
|---|---|---|---|
| MerchantID | ans..30 | M | MerchantID, assigned by First Cash Solution. Additionally this parameter has to be passed in plain language too. |
| TransID | ans..64 | M | TransactionID provided by you which should be unique for each payment |
| RefNr | ans..40 | O | Merchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed. |
| Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent). Please contact the 1cs Support if you want to capture amounts <100 (smallest currency unit). |
| Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only CHF allowed. Please find an overview here: Currency table |
| MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify) |
| OrderDesc | ans..768 | M | Description of delivered products, services etc. |
| URLSuccess | ans..256 | M | Complete URL which calls up 1cs OPS if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between 1cs OPS and shop, please use the parameter UserData. Common notes: We recommend to use parameter “response=encrypt” to get an encrypted response by 1cs OPS However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the “code”-value which indicates success/failure of the action. Only a result of “code=00000000” should be considered successful. |
| URLFailure | ans..256 | M | Complete URL which calls up 1cs OPS if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between 1cs OPS and shop, please use the parameter UserData. Common notes: We recommend to use parameter “response=encrypt” to get an encrypted response by 1cs OPS However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the “code”-value which indicates success/failure of the action. Only a result of “code=00000000” should be considered successful. |
| Response | a7 | O | Status response sent by 1cs OPS to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter. |
| URLNotify | ans..256 | M | Complete URL which calls up 1cs OPS if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between 1cs OPS and shop, please use the parameter UserData. Common notes: We recommend to use parameter “response=encrypt” to get an encrypted response by 1cs OPS However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess. Therefore ensure to check the “code”-value which indicates success/failure of the action. Only a result of “code=00000000” should be considered successful. |
| UserData | ans..1024 | O | If specified at request, 1cs OPS forwards the parameter with the payment result to the shop. |
| ReqId | ans..32 | O | To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, 1cs OPS will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the 1cs OPS must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on 1cs OPS does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the 1cs OPS. |
| SellingPoint | ans..50 | O | Selling Point |
| Service | ans..50 | O | products or service sold |
| Channel | ans..64 | O | Configuration channel of the PPRO contract (account and ContractID are stored in the system). If it exists, it may overwrite channels stored in the system. |
| AccOwner | ans..50 | M | Name of account holder |
| Plain | ans..50 | O | A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID. “Plain”-parameter is part of encrypted “Data” in 1cs OPS and therefore protected against manipulation. |
| Custom | ans..1024 | O | “Custom”-parameter is added to the request data before encryption and is part of encrypted “Data” in 1cs OPS request. By this they are protected against manipulation by a consumer. The Custom-value is added to the 1cs OPS response in plain text and the “|” is replaced by a “&”. By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. Please find a samples here: Custom |
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:
Notice: pls. be prepared to receive additional parameters at any time and do not check the order of parameters
Notice: the key (e.g. MerchantId, RefNr) should not be checked case-sensitive
| Key | Format | CND | Description |
| mid | ans..30 | M | MerchantID, assigned by First Cash Solution |
| PayID | an32 | M | ID assigned by 1cs OPS for the payment, e.g. for referencing in batch files as well as for capture or credit request. |
| XID | ns..40 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by 1cs OPS |
| TransID | ans…64 | M | TransactionID provided by you which should be unique for each payment |
| RefNr | ans..40 | O | Merchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed. |
| Status | a..50 | M | OK or AUTHORIZE_REQUEST (URLSuccess) as well as FAILED (URLFailure) |
| Description | ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! |
| Code | n8 | M | Error code according to 1cs OPS Error Codes (Error codes) |
| MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify) |
| UserData | ans..1024 | O | If specified at request, 1cs OPS forwards the parameter with the payment result to the shop. |
| PaymentPurpose | ans..26 | O | Purpose of payment |
| PaymentGuarantee | a..12 | C | NONE=no payment guarantee, VALIDATED=customer account valid, but no payment guarantee, FULL=payment guarantee Notice: This parameter is only returned if the Status=OK |
| ErrorText | ans..128 | C | Detailed PPRO error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with 1cs Support |
| TransactionID | an..20 | O | Unique transaction number with PPRO |
| Plain | ans..50 | O | A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID. “Plain”-parameter is part of encrypted “Data” in 1cs OPS and therefore protected against manipulation. |
| Custom | ans.. 1024 | O | “Custom”-parameter is added to the request data before encryption and is part of encrypted “Data” in 1cs OPS request. By this they are protected against manipulation by a consumer. The Custom-value is added to the 1cs OPS response in plain text and the “|” is replaced by a “&”. By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. Please find a samples here: Custom |
2.3 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: 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:
| Key | Format | CND | Description |
|---|---|---|---|
| MerchantID | ans..30 | M | MerchantID, assigned by First Cash Solution. Additionally this parameter has to be passed in plain language too. |
| PayID | an32 | M | ID assigned by 1cs OPS for the payment to be credited |
| TransID | ans..64 | M | TransactionID provided by you which should be unique for each payment |
| MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify) |
| Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent). Please contact the 1cs Support if you want to capture amounts <100 (smallest currency unit). |
| Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only CHF allowed. Please find an overview here: Currency table |
| ReqId | ans..32 | O | To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, 1cs OPS will not carry out the payment or new action, but will just return the status of the original transaction or action. Please note that the 1cs OPS must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on 1cs OPS does not take effect. Submissions with identical ReqID for an open status will be processed regularly. Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the 1cs OPS. |
The following table describes the result parameters which 1cs OPS responds to your system:
Notice: pls. be prepared to receive additional parameters at any time and do not check the order of parameters
Notice: the key (e.g. MerchantId, RefNr) should not be checked case-sensitive
| Key | Format | CND | Description |
| mid | ans..30 | M | MerchantID, assigned by First Cash Solution |
| PayID | an32 | M | ID assigned by 1cs OPS for the payment, e.g. for referencing in batch files as well as for capture or credit request. |
| XID | ns..40 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by 1cs OPS |
| TransID | ans…64 | M | TransactionID provided by you which should be unique for each payment |
| Status | a..50 | M | OOK (URLSuccess) or FAILED (URLFailure) |
| Description | ans..1024 | M | Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis! |
| Code | n8 | M | Error code according to 1cs OPS Error Codes (Error codes) |
| ErrorTtext | ans..128 | C | Detailed PPRO error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with 1cs Support |
| RefNr | ans..40 | O | Merchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed. |
