Move from PAYID to payment.id
Whenever you create a transaction, our platform generates a unique reference to it. You need to use this unique reference to follow-up on the transaction (i.e. to perform a maintenance operation like a capture/refund it or simply get the transaction status).
Legacy distinguishes between the
- PAYID (10-digit unique identifier that will never change over the course of a transaction life cycle)
- PAYIDSUB (an incremental digit for each maintenance operation)
formatted as PAYID_PAYIDSUB.
However, Direct follows a different approach by implementing the payment.id: For both every new transaction request and maintenance operations our platform issues a unique value. Read our dedicated chapter in our Webhooks guide to learn how to implement the payment.id into your business logic to properly follow-up on transactions.