Skip to main content

Acquirer specifics

Some acquirers may have specific requirement in the technical interface that can cause adjustment of the request values - or other behaviors.

Nets​

Reference uniqueness​

  • The order id value is taken from the reference field
  • maximum 20 positions long - left most part used
  • value must be unique within 24 hours
    if already used, then a new one is generated using the 15 left most position, concatenated with - and a 4 digit zero prefix random number.

As an example - given a reference with value A7kP2mX9qL4vN8tR1yH6cZ3uB5dFsJ the order id will be A7kP2mX9qL4vN8tR1yH6
If e.g. the cardholder mistypes the card number and the transaction thereby is rejected and shortly after retried, the succeeding attempt will use another order id, e.g. A7kP2mX9qL4vN8t-0842

Worldline​

Reference is exactly 12 position​

  • retrieval reference number (RRN) value is taken from the reference field
  • Dash's (-) removed from value if any occurrences
  • use left most 12 positions
  • left padded with 0 until 12 positions long if too short

Multi capture - same amount - within same day​

Internal rejection due to duplicate transaction is set up by Worldline internally to avoid any transactions being processed, that should not be processed. This happens if the merchant is sending capture for the - same order - same amount - on the same day. Worldline will contact the merchant to check if the capture shall be processed or rejected.

We suggest that, the merchant does not capture the same amount twice - on the same day, but instead do one capture of the whole amount or capture the remaining the next day in case the amounts are identical.

Vipps / MobilePay​

For CIT (non-subscription) transactions, the reference value has a minimum length of 8 positions.

  • left padded with 0 until 8 positions long if too short