feat(router): [stripe connect] prevent creation of payment method for afterpay clearpay#11051
Merged
Conversation
Changed Files
|
deepanshu-iiitu
previously approved these changes
Jan 27, 2026
hrithikesh026
previously approved these changes
Jan 27, 2026
6a48be7
swangi-kumari
previously approved these changes
Jan 29, 2026
swangi-kumari
previously approved these changes
Jan 29, 2026
SanchithHegde
approved these changes
Jan 29, 2026
swangi-kumari
approved these changes
Jan 29, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #11051 +/- ##
=======================================
Coverage ? 0
=======================================
Files ? 0
Lines ? 0
Branches ? 0
=======================================
Hits ? 0
Misses ? 0
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
pixincreate
added a commit
that referenced
this pull request
Jan 30, 2026
* 'main' of github.com:juspay/hyperswitch: feat(payment-methods): add modular payment method update api (#11044) fix(ucs): Handling Unspecified Payment status from UCS (#11057) chore(payments_v2): external vault payment v2 flow fix (#10927) feat(router): [stripe connect] prevent creation of payment method for afterpay clearpay (#11051) feat(router): server configuration addition (#11029) chore(version): 2026.01.30.0 feat(payment-methods): add modular payment method create api (#11031) feat(platform): support save payment method for platform payments (#11056) ci(cypress): pause the optional connector runs, add delay to parallel jobs, run tests on both github and hyperswitch-runners, add retry config for cypress (#11036) chore: fix for setupmandate and complete authorize for granular flows (#11070)
srujanchikke
pushed a commit
that referenced
this pull request
Feb 2, 2026
… afterpay clearpay (#11051)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
Since Afterpay / Clearpay does not support recurring payments, we prevent sending the setup_future_usage flag to stripe when a recurring payment is requested for Afterpay / Clearpay . Additionally, this payment method has been added to the
save_payment_method_on_session.unsupported_payment_methodsconfiguration to ensure that a payment method is not created in Hyperswitch.Additional Changes
How did you test it?
AfterPay/Clearpay Test - Success Scenario without setup_future_usage
Response
Psync
AfterPay/Clearpay Test - Success Scenario with setup_future_usage
Response
Psync
Create and cancel afterpay/clearpay payment with setup_future_usage
Response
Psync
Sanity Testing
Response
MIT payment
Response
Create a normal card payment with stripe connect
Response
Checklist
cargo +nightly fmt --allcargo clippy