I'm Damilola from the Developer Relations team at Paystack. I'm reaching out to share details of an important change we made to how we store Transaction IDs in our database and what you need to do to reflect this update in your database as well.
What's a Transaction ID?
A Transaction ID is one of the unique identifiers assigned to every Paystack transaction and can be used to retrieve information regarding each transaction. It's a unique number that connects a transaction to your business.
What change did we make?
We migrated our database to increase the range of our Transaction IDs from the default unsigned 32-bit integer to an unsigned 64-bit integer. It was necessary for us to make this update because we're fast approaching the maximum limit for the default 32-bit integer and we want to ensure that we can continue to assign Transaction IDs to all new Paystack transactions.
What does this mean for your business?
Many Paystack businesses don't store Transaction IDs in their database and if this applies to you, then you don't need to do anything. Nothing changes.
However, if your business uses or stores Transactions IDs, you should update your integration before Thursday, September 8, to ensure that you're referencing unsigned 64-bit integer IDs in your database instead of the 32-bit integer. Without this change, your integration could break due to an integer out-of-range error which would impact your ability to validate payments from customers and make reconciliations.
We expect to hit the maximum 32-bit integer value in four weeks, so we strongly encourage you to make this change as soon as possible.
How can you make this update?
Programming languages and database management systems have different ways of representing an unsigned 64-bit integer. We've done a breakdown of the common ones here to help you know the specific update that you should make.
Do you have questions?
If you have any questions about the Transaction ID change, or would like more information on how it might impact your business, or need assistance in making the update, please feel free to reply to this email. We're more than happy to help ❤️
Warm regards,
I'm Damilola from the Developer Relations team at Paystack. I'm reaching out to share details of an important change we made to how we store Transaction IDs in our database and what you need to do to reflect this update in your database as well.
What's a Transaction ID? A Transaction ID is one of the unique identifiers assigned to every Paystack transaction and can be used to retrieve information regarding each transaction. It's a unique number that connects a transaction to your business.
What change did we make? We migrated our database to increase the range of our Transaction IDs from the default unsigned 32-bit integer to an unsigned 64-bit integer. It was necessary for us to make this update because we're fast approaching the maximum limit for the default 32-bit integer and we want to ensure that we can continue to assign Transaction IDs to all new Paystack transactions.
What does this mean for your business? Many Paystack businesses don't store Transaction IDs in their database and if this applies to you, then you don't need to do anything. Nothing changes.
However, if your business uses or stores Transactions IDs, you should update your integration before Thursday, September 8, to ensure that you're referencing unsigned 64-bit integer IDs in your database instead of the 32-bit integer. Without this change, your integration could break due to an integer out-of-range error which would impact your ability to validate payments from customers and make reconciliations.
We expect to hit the maximum 32-bit integer value in four weeks, so we strongly encourage you to make this change as soon as possible.
How can you make this update? Programming languages and database management systems have different ways of representing an unsigned 64-bit integer. We've done a breakdown of the common ones here to help you know the specific update that you should make.
Do you have questions? If you have any questions about the Transaction ID change, or would like more information on how it might impact your business, or need assistance in making the update, please feel free to reply to this email. We're more than happy to help ❤️ Warm regards,