We are contacting you with the below information, which we suggest to share with your technical integrator, developer or webmaster

Please be informed about an upcoming change to the payment ID (PAYID) format, which is necessary as we are approaching the 10 billionth payment in the Production environment.

In theory, this change should be transparent as PAYID was not designed as a fixed-length field. However, some integrations may have made assumptions about PAYID format (e.g., hard-coding logic that expects exactly 10 digits or reading only the first 10 digits). As a result , this may affect how PAYIDs appear in API responses and how you reconcile payments.

What will change?

• Ogone Legacy: PAYID length will increase from 10 to 11 digits
• Worldline Global Online Pay Direct: PAYID format 9999999999_0 will become 99999999999_0
• Worldline Global Online Pay Direct:PAYID format 9000009999999999000 will become
  9000099999999999000.

Note for PAYID19 users
The 19-digit format remains unchanged. The only exception applies to merchants who convert between PAYID19 and PAYIDLegacy — checksum calculations will need updating to reflect the new 11-digit length.

Structured Communication impact (reconciliation)
Currently, the structured communication value used for reconciliation is generated by taking the first ten digits of the PAYID and applying a modulo 97 checksum to produce a checksum, which is then appended to the PAYID inside a 12-character structure. For example, a ten-digit PAYID of 9999999999 yields a structured communication value of +++99999/9999/948+++.

With the PAYID length increasing to eleven digits, the existing 12-digit structured communication no longer fits. To accommodate this, we will change the generation rule: we will take the rightmost ten digits of the eleven-digit PAYID and apply the same modulo 97 checksum to those ten digits. For instance, if the PAYID is 10000000123, we will extract the ten rightmost digits 0000000123 and compute the checksum (123 mod 97) to produce a new structured communication like +++00000/0012/326+++.

To recover the original PAYID from the structured communication, you will need to add 10000000000 to the first ten digits embedded in the structured communication.

When will it change?
We will update payment IDs to 10000000000 in the PREPRODUCTION (TEST) environment on Tuesday, 05/05/2026.

Is there any action required for me?
We kindly ask you to review and test your reconciliation and integrations in the Preproduction (TEST) environment to identify any potential impact on your business. We recommend taking the below actions as of Wednesday, 06/05/2026:

• Identify places where PAYID was treated as a string of digits (and not as a numeric value);
• Verify assumptions about a fixed PAYID length to uncover validation logic issues;
• Investigate if treating PAYID as a string causes errors during database insertion.

What about the PRODUCTION environment?
At this stage, no update nor impact in the PRODUCTION environment will take place. We plan to perform the change in Production in the second half of 2026, and will inform you on the exact date well in advance.

We are informing you and performing the change in Preproduction (TEST) environment already now, so you have enough time to review and test your integrations before moving the change to Production in the second half of 2026

Any questions?
Our teams are here to support you in case of any questions. If you need assistance, please contact us via your usual endpoints putting “11-digit PAYID” in the subject of your message. By this, we will make
sure that your question is answered by our team as soon as possible.

Thank you for your understanding and cooperation.