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] [BAMBORA] Payments Failing Due to Wrong Card Expiry Year #4534

Open
2 tasks done
deepanshu-iiitu opened this issue May 3, 2024 · 0 comments · Fixed by #4536 or #4552
Open
2 tasks done

[BUG] [BAMBORA] Payments Failing Due to Wrong Card Expiry Year #4534

deepanshu-iiitu opened this issue May 3, 2024 · 0 comments · Fixed by #4536 or #4552
Assignees
Labels
A-connector-integration Area: Connector integration C-bug Category: Bug

Comments

@deepanshu-iiitu
Copy link
Contributor

deepanshu-iiitu commented May 3, 2024

Bug Description

Payments are failing for connector Bambora due to wrong format of card expiry year.

Expected Behavior

Only 2 digit i.e. 25 for 2025 card expiry year should be passed in Bambora Payments Request.

Actual Behavior

The system is allowing both 2 digit and 4 digit card expiry year in Bambora Payments Request.

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'

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): ``
  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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment