The PXP Financial APIs support IPv6 formatted IP addresses. But there are certain limitations that need to be considered:
- Tokens which were created using an IPv6 address as
uip(using the GET /tokens call) can be used to register a new payment account via this call under the following condition: The Clients must have an IPv4 address as well (in the rare situation that the Client is IPv6 only, the register payment account call will fail).
- The merchants server needs to have an IPv4, otherwise all calls to the PXP Financial APIs will fail.
When a merchant uses the GET /tokens call to generate a token and then the register payment account call, the following rules apply.
One of the below must be true, otherwise the register payment account call will be rejected:
- The IP address sent in the GET /tokens request (using API parameter/field
uip) must match the IP address which was used to initiate the register payment account call
- The Browser User Agents which were sent in the GET /tokens (using API parameter/field
bua) and the subsequent register payment account call need to match
Browser User Agent must be sent in the GET /tokens request as separate parameter
The browser user agent has to be collected by the merchant system together with the IP address and sent as part of the GET /tokens request using API parameter/field
The PXP Financial Service cannot consider the http header information for that purpose, because in a real life scenario the token request will come from the merchant IP not from the client/device browser.
When a merchant uses GET /tokens call to generate a token and then the Update payment account call for the migration of a payment account to a new MID the following restriction applies or the call will be rejected: