Merchant-initiated payments

Under PSD2, it is permitted to charge a customer without him being present, provided that he has explicitly accepted it..

The process to make this type of collection is as follows:

• A secure first payment must be made, also indicating what type of payments will be made to the client later. To do this, the "trxType" parameter (REST integrations) or "DS_MERCHANT_TRX_TYPE" (GET integrations) must be included with one of the values indicated in this table:
  
  
  

  Value	Concept
  I	Deferred payment. Always refers to an INDIVIDUAL purchase, the amount of the different transactions being set, and with a defined time period
  R	Recurring payment. The amount of the transactions may be set or variable, and with a defined time period
  H	Normally due to partial deliveries. Also, when the client extends the hotel stay / vehicle rental or when there is an estimated authorisation, the final amount is requested (“conclusion”)
  E	Original rejected due to “balance”; only for certain activity sectors (for greater detail review the brand requirements) and with a maximum number of days since the purchase. Relevant example: “Transport”
  D	Those which occur following the operation for services provided / used, unknown at the beginning. (Minibar, vehicle damage, fines, etc.)
  M	When additional services are incurred during the contract period
  N	When the business charges for services which the holder committed to, but then did not comply with the agreed terms. Relevant example: no-show hotel reservations without cancellation.
  C	Other

  If the merchant is going to launch subsequent collections, MERCHANT_TRX_TYPE = "R" or "I", the duration of the recurrence and the collection period must also be indicated in the MERCHANT_DATA or DS_MERCHANT_DATA parameter:

  
  {
  	"recurringExpiry": "",
  	"recurringFrequency": "",
  }
              
          

  Element	Content	Description
  recurringExpiry	[0-9]{8}	Conditional. Mandatory for Recurring and Instalment operations (MERCHANT_TRX_TYPE = I or R). The date from which there will be no more authorisations. Accepted format: YYYYMMDD
  recurringFrequency	[A-Za-z0-9]{1,4}	Conditional. Mandatory for Recurring and Instalment operations (MERCHANT_TRX_TYPE = I or R). Indicates the minimum number of days between authorisations

• Subsequent payments in which the customer is not present must indicate the parameter "scaException" or "DS_MERCHANT_SCA_EXCEPTION", depending on the integration, with the value "MIT" and the field MERCHANT_TRX_TYPE with the value that was indicated in the first payment.
  If the initial payment was with MERCHANT_TRX_TYPE = "R" or "I", the fields "recurringExpiry" and "recurringFrecuency" must always be sent.