-
Notifications
You must be signed in to change notification settings - Fork 4.1k
feat(core): implemented platform merchant account #6882
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ci looks good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The HeaderAuth
side of things look good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you make the same changes in the other config files as well: config/development.toml
and config/docker_compose.toml
?
@@ -724,12 +775,14 @@ where | |||
} | |||
|
|||
#[cfg(all(feature = "partial-auth", feature = "v1"))] | |||
#[allow(unused)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need this annotation?
@@ -1412,15 +1537,20 @@ pub struct MerchantIdAuth(pub id_type::MerchantId); | |||
|
|||
#[cfg(feature = "v1")] | |||
#[async_trait] | |||
#[allow(unused)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
724cf37
4049c6e
724cf37
to
4049c6e
Compare
…r-verifyurl-in-redirection-handler * 'main' of github.com:juspay/hyperswitch: (444 commits) ci: add tests that make use of locker (juspay#6735) chore(version): 2024.12.26.1 fix(router): populate `profile_id` in for the HeaderAuth of v1 (juspay#6936) docs(openapi): update /relay request example (juspay#6942) chore(version): 2024.12.26.0 fix(payments_list): handle same payment/attempt ids for different merchants (juspay#6917) refactor(core): remove merchant return url from `router_data` (juspay#6895) feat(router): add endpoint for listing connector features (juspay#6612) fix(wasm): remove chasenet from jpmorgan wasm as ChaseNet doesn’t exist in PMT (juspay#6927) fix(cors): expose all headers set by application in `access-control-expose-headers` header value (juspay#6877) chore(version): 2024.12.24.0 feat(cypress): valdiate `error_code` and `error_message` and make it visible in `reports` (juspay#6913) fix(wasm): remove extra space from wasm for payment_method_type of JPMorgan (juspay#6923) fix(wasm): fix feature dependencies in `connector_configs` crate for WASM builds (juspay#6832) feat(router): add /retrieve api for relay (juspay#6918) feat(core): implemented platform merchant account (juspay#6882) feat(payments_v2): add payment method list endpoint (juspay#6805) fix(connector): [Cybersource] fix the required fields for wallet mandate payments (juspay#6911) chore(version): 2024.12.23.0 feat(connector): [JPMORGAN] add Payment flows for cards (juspay#6668) ...
Type of Change
Description
About the feature
Enabling the platform account.
How it works
x-connected-merchant-id
.is_platform
true and the merchant account on behalf of which operation is performed belongs to the same organisation as platform then the operation is allowed.Payment Intent
x-connected-merchant-id
header.platform_merchant_id
column for the payment intent will be populated with platforms merchant id.Other operations
platform_merchant_id
in other operations as well.Additional Changes
Motivation and Context
#6883
How did you test it?
x-connected-merchant-id
with value as connected merchant account's merchant id.platform_merchant_id
is populated with platform's merchant id.Checklist
cargo +nightly fmt --all
cargo clippy