Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] connector's txn ID exceeding 512 characters are not being stored in DB #7018

Open
2 tasks done
kashif-m opened this issue Jan 10, 2025 · 0 comments · May be fixed by #7017
Open
2 tasks done

[BUG] connector's txn ID exceeding 512 characters are not being stored in DB #7018

kashif-m opened this issue Jan 10, 2025 · 0 comments · May be fixed by #7017
Assignees
Labels
C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet

Comments

@kashif-m
Copy link
Contributor

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:

  1. Operating System or Linux distribution:
  2. Rust version (output of rustc --version): rustc 1.80.1 (3f5fd8dd4 2024-08-06)
  3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@kashif-m kashif-m added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels Jan 10, 2025
@kashif-m kashif-m self-assigned this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet
Projects
None yet
1 participant