-
Notifications
You must be signed in to change notification settings - Fork 4.2k
fix(router): [Cybersource] add flag to indicate final capture #7085
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
Conversation
Changed Files
|
3465713
15f9e0e
@AkshayaFoiger Where are we sending isFinal flag? |
I have added the capture call test case above. The change made in this PR will only affect CyberSource's capture call. CyberSource does not provide an explicit response for sending this flag. Instead, this flag is expected to be passed from CyberSource to the issuer bank. Hence the the responsibility of releasing remaining authorized amount is being delegated to the issuer bank. |
…-connectors * 'main' of github.com:juspay/hyperswitch: ci: disable stripe in cypress (#7183) fix(router): [Cybersource] add flag to indicate final capture (#7085) fix: invalidate surcharge cache during update (#6907) chore(version): 2025.02.04.0 fix(samsung_pay): populate `payment_method_data` in the payment response (#7095) feat(router): add core changes for external authentication flow through unified_authentication_service (#7063) fix(connector): [NETCETERA] add `sdk-type` and `default-sdk-type` in netcetera authentication request (#7156)
Type of Change
Description
Added flag to the CyberSource capture call to indicate the final capture in cases of manual capture.
This flag has been incorporated into the CyberSource capture request body to ensure the issuer bank is informed appropriately.
How did you test it?
Create a payment with cybersource
Response
Capture call
Response
Psync
Response
Checklist
cargo +nightly fmt --all
cargo clippy