Reference numbers

Settlement batch and reconciliation

For card payments, at the beginning of each new day, the settlement batches from the card payments captured and/or credited over one day through Netaxept are passed on to your chosen acquirer(s) for further processing. Acquirer(s) will then settle these transactions to your company's bank account according to the agreed settlement times. For direct bank payments, the bank will transfer the captured or credited amount between the customer's and your company's bank accounts in near real-time. On your company's bank statement you will see card payments settled as settlement batches and direct bank payments as individual transactions.

After the date changes, you can retrieve the information concerning transactions and settlement batches either manually via Netaxept Admin, automatically via Netaxept API, or by using Nets Merchant Portal or reporting service offered by your chosen acquirer or other payment method service provider. With this information, you can match transactions received via Netaxept with the information in your own systems.

• Netaxept Admin: The web-based Netaxept Admin shows all transactions received through Netaxept, regardless of payment method, and it can be used to retrieve reports concerning individual transactions and settlement batches with the desired search criteria. The settlement batch reports can be downloaded in Excel format for further processing. If necessary, settlement batch reports can be sent daily to the defined email addresses. Login to Netaxept Admin in test environment or production environment

• Search via Netaxept API: Netaxept API allows you to retrieve transaction and settlement batch information for your systems in XML format. The retrievals work in both REST and Web Services APIs.

• Nets Merchant Portal: The web-based Merchant Portal displays transactions that are captured and/or credited through Nets’ Nordic payment terminals or Netaxept, regardless of the chosen acquirer, and allows you to retrieve reports for further processing in Excel or XML format. Read more about Merchant Portal

• Reporting services offered by your chosen acquirer or similar: Most card acquirers and other payment method service providers offer their merchants own reporting services where they can retrieve the needed settlement data including transaction fees and commissions. Please contact your chosen payment method service provider for more information.

Batch reference number

The batch reference number identifies the individual settlement batch and can be seen on your company's bank statement for card payments. The batch reference number is not useful for direct bank payments, since these payments are settled to your company's bank account as individual transactions. Therefore, the batch reference number is not shown on your company's bank statement for direct bank payments. Format of the batch reference number will vary depending on the settings you have agreed with your chosen acquirer or other payment method service provider.

Transaction reference number

Transaction reference number is a unique end-to-end reference number for each transaction. This can be seen on your company's bank statement for direct bank payments, and through Netaxept Admin and Nets Merchant Portal for all transactions that support transaction-specific reference numbers.

If you want to specify a unique reference number for each transaction, you need to send the parameter TransactionReconRef and its value along the Register call to Netaxept. The same reference number will be then used on all subsequent financial operations (authorization, capture and credit) on the transaction, unless it is overridden when the financial transaction is sent in. Alternatively, you can send TransactionReconRef parameter to Netaxept along the Process call.

It should be noted that card payments are settled to your company's account as settlement batches, which means that you will see the reference number for the settlement batch on your company's bank statement, while the reference number for an individual transaction is not visible. Instead, if you have signed direct agreements with banks concerning the use of direct bank payments, direct bank payments are shown as individual transactions in your company's bank statement, and transaction reference numbers are visible there as well.

Allowed characters are a-z A-Z 0-9, and lenght must be between 1 and 25 characters.

Card payments

Since this is an end-to-end transaction reference (from merchant to Netaxept to payment method service provider to merchant), the actual support is bound by the limitation of the payment method service provider that you have an agreement with. The following table shows which transaction-specific reference fields are supported by the different card acquirers.

Please note that in Denmark, for the national card scheme Dankort, the support is depending on the configuration for your merchant in Netaxept. While older versions should use order number up to 11 characters, and avoid using TransactionReconRef, newer configurations should use TransactionReconRef.

Direct bank payments

TransactionReconRef is quite commonly used for direct bank payments. The structure of the transaction reference number must follow the specifications suitable for each bank you are using. We recommend you to find a pattern that fits all the direct banks you are connecting to. For example, for Swedish banks, a 10-digit number will be allowed by all the banks. For the time being transaction reference number is not supported for direct bank payments made via Paytrail.

Swedish banks

Finnish banks

Finnish reference numbers need to be formulated according to the Finnish reference number standard. Instructions on the structure are published on the website of the Federation of Finnish Financial Services at www.fkl.fi.

In Finnish: http://www.finanssiala.fi/maksujenvalitys/dokumentit/kotimaisen_viitteen_rakenneohje.pdf

In Swedish: http://www.finanssiala.fi/maksujenvalitys/dokumentit/Inhemska_referensnummers_uppbyggnad.pdf