You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Worldpay's payment flows generate a txn identifier which is quite long - as it's a JWE. This is stored in DB for querying or performing any other processor related operation on the payment. DB schema for storing such long identifiers has been 512 characters. Recently, we started to see a txn ID being returned exceeding 512 characters due to which the application started throwing errors on DB update operations.
Expected Behavior
DB should respect and store Worldpay IDs exceeding 512 characters.
Actual Behavior
DB is not storing Worldpay IDs.
Steps To Reproduce
Route a payment through Worldpay connector.
Context For The Bug
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.
If not (or if building/running locally), please provide the following details:
Operating System or Linux distribution:
Rust version (output of rustc --version): rustc 1.80.1 (3f5fd8dd4 2024-08-06)
App version (output of cargo r --features vergen -- --version): ``
Have you spent some time checking if this bug has been raised before?
Bug Description
Worldpay's payment flows generate a txn identifier which is quite long - as it's a JWE. This is stored in DB for querying or performing any other processor related operation on the payment. DB schema for storing such long identifiers has been 512 characters. Recently, we started to see a txn ID being returned exceeding 512 characters due to which the application started throwing errors on DB update operations.
Expected Behavior
DB should respect and store Worldpay IDs exceeding 512 characters.
Actual Behavior
DB is not storing Worldpay IDs.
Steps To Reproduce
Route a payment through Worldpay connector.
Context For The Bug
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the
x-request-id
response header to help us debug your issue.If not (or if building/running locally), please provide the following details:
rustc --version
):rustc 1.80.1 (3f5fd8dd4 2024-08-06)
cargo r --features vergen -- --version
): ``Have you spent some time checking if this bug has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: