Twint

With TWINT, you can make convenient and secure payments with your smartphone – at the cash register in a supermarket, in an online shop, when shopping at a farm shop, on public transport, when parking, or when transferring money to your friends. With more than four million registered users, TWINT is the leading payment app in Switzerland.

Source: https://www.twint.ch/en/company/about-us/

Features

Integration type

Redirection

Tokenization

No

Payment Flow

1-step payment flow : Capture (direct debit)

2-step payment flow : Authorization + Capture

3-step payment flow : Pending Authorization + Authorization + Capture (asynchrone workflow)

Additional features

Information request and CIT

MIT

Server-to-server

How to test?

info

Datatrans offers payment methods for Switzerland customers. Your Create Session call must be in CHF currency and contains an order.customer node valued with Switzerland customer data. You can download Twint test application by following these links: IOS | Android

Data Mapping & Mandatory Fields

Below is the mapping between your Create Session request and the fields expected by this payment method.

Purse Session field	Mandatory
amount	Yes
order.redirection	Yes
order.reference	Yes
order.currency_code	Yes
customer.reference	No
customer.type_code	No
customer.company_name	No
customer.gender_code	No
customer.first_name	No
customer.last_name	No
customer.birthdate	No
customer.ip	No
customer.locale_code	No
customer.billing_address.gender_code	No
customer.billing_address.first_name	No
customer.billing_address.middle_name	No
customer.billing_address.last_name	No
customer.billing_address.address_lines	No
customer.billing_address.city	No
customer.billing_address.postal_code	No
customer.billing_address.country_code	No
customer.billing_address.province_code	No
customer.billing_address.email	No
customer.billing_address.phone	No
customer.billing_address.mobile_phone	No
shipments.amount	No
shipments.tax_amount	No
shipments.shipping_address.gender_code	No
shipments.shipping_address.first_name	No
shipments.shipping_address.middle_name	No
shipments.shipping_address.last_name	No
shipments.shipping_address.address_lines	No
shipments.shipping_address.city	No
shipments.shipping_address.postal_code	No
shipments.shipping_address.country_code	No
shipments.shipping_address.province_code	No
shipments.shipping_address.email	No
shipments.shipping_address.phone	No
shipments.shipping_address.mobile_phone	No
shipments.item_lines.type_code	No
shipments.item_lines.sku_reference	No
shipments.item_lines.name	No
shipments.item_lines.price	No
shipments.item_lines.quantity	No
shipments.item_lines.amount	No
shipments.item_lines.tax_lines.rate	No
shipments.item_lines.tax_lines.amount	No

Payment Labels

Label	Method	Payment type
datatrans	twint	primary (mobile wallet)

Actions

Action	Mandatory fields	Optional fields
INIT	reference Test-1234 currency_code CHF success https://merchant.example.url/success failure https://merchant.example.url/failure	amount 1000
APPLY	reference Test-1234 currency_code CHF success https://merchant.example.url/success failure https://merchant.example.url/failure	amount 1000

Status

PSP status	State	Code	Description
SUCCESS	SUCCESS	SUCCEEDED	Successful operation
WAITING	WAITING	WAITING_PARTNER_RESPONSE	Waiting for transaction to be transmitted
ERROR	ERROR	BAD_REQUEST	Failed operation
SESSION_DATA_NOT_OK	SUCCESS	BAD_REQUEST	Session data doesn't meet the partner's requirements
UNKNOWN_ERROR	ERROR	FAILED	Unknown error
ABORTED	ERROR	ABORTED_BY_CUSTOMER	Customer has aborted the payment
initialized	SUCCESS	SUCCEEDED	Transaction was initialized. A transaction is initialized after a successful init request.
challenge_required	ERROR	BAD_REQUEST	Challenge required.
challenge_ongoing	ERROR	BAD_REQUEST	Challenge ongoing.
authorized	SUCCESS	SUCCEEDED	Transaction was authorized. A transaction is authorized after client payed using the redirect url.
settled	WAITING	WAITING_PARTNER_RESPONSE	Transaction was settled partially or fully.
canceled	SUCCESS	SUCCEEDED	Transaction was canceled by the user or automatically by the system after a time out occurred on datatrans payment forms
transmitted	SUCCESS	SUCCEEDED	Transaction was transmitted to the acquirer for processing. This is automatically set by datatrans system
failed	ERROR	FAILED	Transaction failed.
UNAUTHORIZED	ERROR	BAD_REQUEST	Unauthorized error
INVALID_JSON_PAYLOAD	ERROR	BAD_REQUEST	Invalid json payload
UNRECOGNIZED_PROPERTY	ERROR	BAD_REQUEST	Unrecognized property
INVALID_PROPERTY	ERROR	BAD_REQUEST	Invalid property
CLIENT_ERROR	ERROR	BAD_REQUEST	Client error
SERVER_ERROR	ERROR	BAD_REQUEST	Server error
INVALID_TRANSACTION_STATUS	ERROR	BAD_REQUEST	Invalid transaction status
TRANSACTION_NOT_FOUND	ERROR	BAD_REQUEST	Transaction not found
EXPIRED_CARD	ERROR	BAD_REQUEST	Expired card
INVALID_CARD	ERROR	BAD_REQUEST	Invalid card
BLOCKED_CARD	ERROR	BAD_REQUEST	Blocked card
UNSUPPORTED_CARD	ERROR	BAD_REQUEST	Unsupported card
INVALID_ALIAS	ERROR	BAD_REQUEST	Invalid alias
INVALID_CVV	ERROR	BAD_REQUEST	Invalid cvv
DUPLICATE_REFNO	ERROR	BAD_REQUEST	Duplicate Refno
DECLINED	ERROR	BAD_REQUEST	Declined
SOFT_DECLINED	ERROR	BAD_REQUEST	Soft declined
INVALID_HEADER	ERROR	BAD_REQUEST	Invalid header
INVALID_SIGN	ERROR	BAD_REQUEST	Invalid sign
BLOCKED_BY_VELOCITY_CHECKER	ERROR	BAD_REQUEST	Blocked by velocity checker
THIRD_PARTY_ERROR	ERROR	BAD_REQUEST	Third party error
REFERRAL	ERROR	BAD_REQUEST	Referral
INVALID_SETUP	ERROR	BAD_REQUEST	Invalid setup