Context
Today one publishable key maps to exactly one merchant. Platforms and marketplaces that want to onboard many sub-merchants (each with isolated escrow settlement) have no way to integrate Connect without provisioning a separate key/gateway config per sub-merchant.
Scope
- A
merchantId (or sub-account) concept in the gateway's key model: one platform-level pk_/sk_ pair can create sessions scoped to a specific sub-merchant.
- Isolated escrow settlement and webhook delivery per sub-merchant — a platform never sees another sub-merchant's funds mixed in.
- Admin-facing listing of sub-merchants and their aggregate volume, exposed via the gateway API.
Acceptance criteria
- Creating a session with a
merchantId routes settlement to that sub-merchant only.
- Webhooks for one sub-merchant's escrow never reach another sub-merchant's configured endpoint.
- A platform can list its sub-merchants and per-sub-merchant volume via the gateway API.
Context
Today one publishable key maps to exactly one merchant. Platforms and marketplaces that want to onboard many sub-merchants (each with isolated escrow settlement) have no way to integrate Connect without provisioning a separate key/gateway config per sub-merchant.
Scope
merchantId(or sub-account) concept in the gateway's key model: one platform-levelpk_/sk_pair can create sessions scoped to a specific sub-merchant.Acceptance criteria
merchantIdroutes settlement to that sub-merchant only.