Subsequent Payments

Any payments subsequent to the activation may be made through:

• a Hosted Transaction (CIT payments only); the wallet ID field is used to pre populate the payment page with the card data. The cardholder will be required to authenticate (SCA).
• through a Server to Server transaction: subsequent payments performed with walletIds created via MIT Scheduled or Unscheduled tokenizations must be processed without authentication (SCA) proceeding directly with the payment, the walletID field replaces the card data (card, cvv2, expiryMonth, expiryYear).

For all solutions, the following parameters must be sent:

Subsequent batch payments

In the event of recurring payments, any debit requests after the activation can be processed also via a file, according to the format "Detail record for Recurring Payments" described in the paragraph Triniz format - File structure.