No results

Activation

When performing a Hosted 3DSecure or Server-To-Server 3DSecure payment , you can store card details in Nexi and you them via a token (walletid) for subsequent payments.

This feature is available only for merchants having an agreement with Intesa (tenantId = 10).

Tokenizations can be divided into 3 types:

  • MIT Scheduled: once the card has been tokenized, the merchant will execute the subsequent charges with a defined frequency (e.g. first day of each month).
  • MIT Unscheduled: once the card has been tokenized, the merchant will execute the subsequent charges with an undefined frequency.
  • CIT: the card is tokenized to allow the cardholder to make subsequent payments faster. Unlike the MIT transaction, the merchant will not be able to directly debit this tokenized card, as the subsequent CIT payment is subject to authentication (SCA) by the cardholder.

You simply need to populate the following fields in the additional parameters, as well as the standard parameters specified in the payment protocol:

NAME DESCRIPTION FORMAT
recurringAction Action to be performed on the contract. Possible values are:
  • C = contract creation (creation)
  • S = card substitution (substitution)
  • N = One shot payment without card/contract storing (none)
 AN
Max. length: 1
walletid Card token (unique - no value in case of one shot payment [recurringAction=N]) N
Max. length: 18
contractType Tokenization type. Possible values:
  • MIT_SCHEDULED
  • MIT_UNSCHEDULED
  • CIT
If not set, the default value set in the terminal configuration will be used. 		AN
expiryDate Tokenization Expiration.
This parameter can only be used in case of MIT Scheduled. 		DATA yyyy-mm-dd
frequency Frequency of the charge in number of days.
You can use this parameter only in case of MIT Scheduled. 		N

NOTES:

  • It is also possible to perform tokenization on card verification operations, but not on pre-authorizations.
  • It is not allowed to use walletIds created through MIT Scheduled to make MIT Unscheduled payment transactions and vice versa.
  • Subsequent CIT payments can be made using walletIds created from scheduled and unscheduled MIT transactions.
  • Storage of card detail depends on whether the authorisation request is successful. Storage the same card to different walletid is allowed. The walletid and the credit card are automatically disassociated after six years of disuse. The limits of the amounts coincide with those relating to the associated credit card plafond.