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

refactor(core): Refactor fallback routing behaviour in payments for v2 #5642

Merged
merged 20 commits into from
Aug 22, 2024

Conversation

Aprabhat19
Copy link
Contributor

@Aprabhat19 Aprabhat19 commented Aug 19, 2024

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

This PR refactors the fallback routing behaviour in payments routing for v2. Update the function to accept business_profile as a parameter instead of profile_id.

Additional Changes

  • This PR modifies the API contract
  • This PR modifies the database schema
  • This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

For v2:

  • create a MA and add 2 MCAs, it will be added for default fallback in the order they were cretaed
  • make a payment , it should go through the mca that was added first based on default fallback

Checklist

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible

@Aprabhat19 Aprabhat19 self-assigned this Aug 19, 2024
@Aprabhat19 Aprabhat19 requested review from a team as code owners August 19, 2024 18:35
crates/router/src/core/admin.rs Outdated Show resolved Hide resolved
crates/router/src/core/admin.rs Outdated Show resolved Hide resolved
crates/router/src/core/admin.rs Outdated Show resolved Hide resolved
@Aprabhat19 Aprabhat19 requested review from jarnura and vspecky August 20, 2024 13:24
jarnura
jarnura previously approved these changes Aug 21, 2024
crates/router/src/core/payments.rs Show resolved Hide resolved
crates/router/src/core/payments.rs Outdated Show resolved Hide resolved
crates/router/src/core/payments.rs Outdated Show resolved Hide resolved
crates/router/src/core/payments.rs Outdated Show resolved Hide resolved
crates/router/src/core/admin.rs Show resolved Hide resolved
crates/router/src/core/admin.rs Outdated Show resolved Hide resolved
crates/router/src/core/payments/routing.rs Show resolved Hide resolved
@likhinbopanna likhinbopanna added this pull request to the merge queue Aug 22, 2024
Merged via the queue into main with commit 22743ac Aug 22, 2024
22 checks passed
@likhinbopanna likhinbopanna deleted the fallback-core branch August 22, 2024 10:50
pixincreate added a commit that referenced this pull request Aug 23, 2024
* 'main' of github.com:juspay/hyperswitch:
  feat(connector): [Adyen] add dispute flows for adyen connector (#5514)
  chore(version): 2024.08.23.0
  feat(router): [cybersource] add disable_avs and disable_cvn flag in connector metadata  (#5667)
  feat(customer_v2): add route for customer retrieve v2  (#5516)
  chore(version): 2024.08.22.1
  fix(router): [Adyen]  prevent partial submission of billing address and add required fields for all payment methods (#5660)
  docs(README): Adding Contributors guide (#5184)
  Docs: Adding redirect url details (#5507)
  feat(global_id): create a `GlobalId` domain type (#5644)
  feat(router): collect customer address details based on business profile config regardless of connector required fields (#5418)
  feat: add new routes for profile level list apis (#5589)
  refactor(core):  Refactor fallback routing behaviour in payments for v2 (#5642)
  refactor(router): add connector_transaction_id, send response body and use admin_api_auth_with_merchant_id for payments manual update flow (#5658)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[REFACTOR] Refactor Update and Retrieve Default Fallback behaviour in payments routing
6 participants