-
Notifications
You must be signed in to change notification settings - Fork 4.1k
feat(payment_methods): add support to pass apple pay recurring details to obtain apple pay merchant token #6770
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
…s to obtain apple pay merchant token
Changed Files
|
…le_pay/mpan/recurring-changes
jarnura
requested changes
Dec 10, 2024
sai-harsha-vardhan
approved these changes
Dec 17, 2024
jarnura
approved these changes
Dec 18, 2024
pixincreate
added a commit
that referenced
this pull request
Dec 20, 2024
…ete-pm * 'main' of github.com:juspay/hyperswitch: refactor(dynamic_routing): add col payment_method_type in dynamic_routing_stats (#6853) refactor(customers_v2): include minor fixes for customer v2 flows (#6876) fix: cypress reports generation (#6894) fix(connector): Paypal BankRedirects (Ideal/EPS) (#6864) chore(version): 2024.12.19.1 fix(connector): [UNIFIED_AUTHENTICATION_SERVICE] change url path to `pre_authentication_processing` in pre-auth flow (#6885) refactor(users): move roles schema to global interface (#6862) feat(payment_methods): add support to pass apple pay recurring details to obtain apple pay merchant token (#6770) feat(payments): [Payment links] Add config for changing button text for payment links (#6860) feat(core): added customer phone_number and email to session token response for click to pay (#6863) FEAT(klarna): Klarna Kustom Checkout Integration (#6839) feat(users): handle email url for users in different tenancies (#6809) chore(version): 2024.12.19.0 refactor(dynamic_routing): update the authentication for update config to include JWT type (#6785) chore(env): remove unified_authentication_service base_url from integ, sandbox and production toml (#6865)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-core
Area: Core flows
A-payment-methods
Area: Payment Methods
M-api-contract-changes
Metadata: This PR involves API contract changes
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
Whenever a customer makes an Applepay payment a unique network token called a DPAN (Device Primary Account Number) is created and stored securely on the customer’s Apple device. This token acts as the payment information for all purchases and keeps the raw card number safe from bad actors.
However, Apple Pay’s DPAN (Device Primary Account Number) may not be ideal for all subscription businesses, because it can result in involuntary churn.
Visa is making enhancements to network tokens to ensure their continued compatibility with follow-on transactions. Due to these changes, there is impact to a few use cases for Apple Pay recurring transactions. Beginning July 30th, 2025, the current device generated Apple Pay network tokens will no longer be applicable for Standing Instruction transactions. Standing Instruction use cases constitute recurring, installments, or unscheduled credential on file token usages.
In order to add support apple pay MPAN recurring object needs to be passed to apple pay in the /sessions call.
This adds supports to accept the
ApplePayRecurringPaymentRequest
in theFeatureMetadata
for the payment request. Based the request details passed the appropriate recurring details will be displayed in the apple pay modal during the customer authentication.Additional Changes
Motivation and Context
How did you test it?
-> Create a merchant connector account with applepay metadata to decrypt the apple pay token at hyperswitch
-> Create a payment by passing
apple_pay_recurring_details
-> session call
-> Confirm the payment with the token
Checklist
cargo +nightly fmt --all
cargo clippy