Enhancements

Variable Base URL

By default, our multicore connects via connect.pay.nl. From there, we determine which server the transaction is routed to and processed on.

However, we recommend making the base URL configurable so that it can easily be changed from connect.pay.nl to, for example, domain.com. This can be useful in two scenarios:

• If connect.pay.nl is temporarily unavailable due to an outage.
• If we provide you with a dedicated server that you can connect to directly. This is particularly relevant for large events with peak traffic, where the standard server might hit rate limits.

This approach ensures greater flexibility and resilience in your integration.

Rate limiting

To ensure that all POS transactions can be processed successfully, we use rate limiting. This prevents our systems from becoming unavailable in case an excessive number of transactions are initiated.

However, in certain situations, such as peak moments, it is possible that a large number of transactions are started simultaneously. It is therefore important to be aware of the limits before hitting the rate limiter. The current limits are:

• 150 simultaneous calls
• 1500 calls per 10 seconds

Especially considering polling and the additional requests it generates, it is important to take these limits into account. If you expect to exceed these limits, please contact us so we can work together on a suitable solution.

Exchange URL

We recommend using an exchange call (also known as an IPN or webhook) in addition to polling. If, for any reason, the final status is not received via polling, the exchange call can serve as a fallback. The exchange URL can be provided when initiating the transaction on the payment terminal.

{
	"exchangeUrl": "https://demo.pay.nl/exchange.php"
}

Once you receive confirmation via the exchange call that the transaction has been completed, you can stop polling immediately. We also recommend using signing, so that no additional status API call is required when receiving the exchange call. This ensures that the request originates from our TGU servers

📘

Configure the 'sales location' in the Admin Panel to receive exchange calls only for successful transactions. This can be set by selecting ‘PAYMENT COMPLETE ONLY’ in the 'State communication' field. This reduces the number of exchange calls and therefore lowers the load on your servers.