-
Notifications
You must be signed in to change notification settings - Fork 3.9k
feat(connector): [AUTHORIZEDOTNET] create connector customer flow added #8774
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
Merged
Conversation
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
Changed Files
|
7dcca38
to
9a775e9
Compare
deepanshu-iiitu
previously approved these changes
Jul 29, 2025
4277be9
to
e32c134
Compare
ShankarSinghC
previously approved these changes
Jul 30, 2025
deepanshu-iiitu
previously approved these changes
Jul 30, 2025
c4315c9
ShankarSinghC
previously approved these changes
Aug 1, 2025
d03f753
to
3fec9d4
Compare
likhinbopanna
previously approved these changes
Aug 5, 2025
6b3205d
to
16e0fd8
Compare
16e0fd8
to
8fa32b1
Compare
deepanshu-iiitu
approved these changes
Aug 5, 2025
ShankarSinghC
approved these changes
Aug 5, 2025
likhinbopanna
approved these changes
Aug 5, 2025
pixincreate
added a commit
that referenced
this pull request
Aug 6, 2025
…ordea-sepa * 'main' of github.com:juspay/hyperswitch: (89 commits) feat(router): [worldpayvantiv] add dispute list sync and implement dispute (#8830) feat(core): Add support for Void after Capture (#8839) fix(wasm): [FISERV] Added GooglePay Payment Method Type (#8832) feat(connector): [Barclaycard] Add Google Pay Payment Method (#8786) chore(version): 2025.08.06.0 feat(core): Added additional authentication fields for 3ds external authentication (#8758) refactor(core): propagate network_transaction_id in response of payment (#8829) fix(core): add fix for stopping multiple event locking idempotent logs (#8034) feat(connector): [AUTHORIZEDOTNET] create connector customer flow added (#8774) feat(core): Add L2_L3 Data Support (#8828) feat(connector): [NMI] Add mandates flow (#8652) fix(connector): [Wise] send uuid as connector_transaction_id (#8836) feat(core): populate UCS status_code in response headers (#8788) feat(external_services): Fixed Url for Unified Connector Service gRPC Client (#8587) chore: reorder v2 migrations folders (#8671) fix(router): Take merchant ID from headers in API Key - Revoke (v2) (#8808) fix(connector): (payload) currency auth key wasm changes (#8825) feat(payment-methods): add filtering logic for payment method list v2 (#8606) feat(router): add support for apple pay pre-decrypted token in the payments confirm call (#8815) chore(version): 2025.08.05.0 ...
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
Previously, the
setup_mandate
flow was responsible for creating a customer profile inAuthorize.Net
. This caused issues when the samecustomer_id
andcustomer_email
were used in subsequentsetup_mandate
calls (even with differentpayment_details
), resulting in an error:"A duplicate record with ID 932042699 already exists."
In this PR, segregated customer creation logic:
Creates the customer profile without payment details.
This logic was previously part of setup_mandate.
Now only creates a customerPaymentProfile (a separate Authorize.Net API call).
Allows passing billTo details, which were not permitted in createCustomerProfile API calls but are supported in createCustomerPaymentProfile.
Benefits
Additional Changes
Motivation and Context
How did you test it?
1. Setup mandate flow with new customer id and email (succeeded)
Response
2. Setup mandate flow with same customer id, email and payment details (failed, as expected)
3. Setup mandate flow with same customer id, email but different payment details (succeeded)
Response
4. Normal payment (succeeded)
Response:
5. Non zero CIT (succeeded)
Response:
6. Corresponding non zero MIT (succeeded)
Note: use different amount than the one used in CIT
Response:
7. Zero dollar MIT corresponding to setup-mandate CIT (succeeded)
Response:
Checklist
cargo +nightly fmt --all
cargo clippy