Choose Your Test Path

Start with one base pack, then add only the layers that actually apply to your launch scope.

1. Which payment path are you using: Elements, Paylink, or API / server-led?
2. Are you taking ecommerce cardholder-initiated card payments? If yes, add 3DS.
3. Will you charge later without the customer present? If yes, add Stored credential & MIT.
4. Will charges be scheduled by you? If yes, add Scheduling.
5. Will your system retry failed payments automatically? If yes, add Retry & resilience.
6. Will your system consume asynchronous notifications? If yes, add Webhooks & postbacks.

Use case	Base	Required overlays	Current published pack
One-off ecommerce checkout with hosted fields	Elements	3DS	Elements + 3DS
One-off ecommerce hosted checkout	Paylink	3DS	Paylink + 3DS
One-off ecommerce server-led flow	API / server-led	3DS	API / server-led + 3DS
Stored credential setup for later charging	Elements or Paylink	3DS, Stored credential & MIT	Deferred
Merchant-managed recurring collection	any base	3DS, Stored credential & MIT, Scheduling, Retry & resilience	Deferred

The first published packs are:

• Elements + 3DS
• API / server-led + 3DS
• Paylink + 3DS

These packs intentionally focus on the core ecommerce path first. MIT, recurring setup, and recurring charge packs should follow only after the recurring-intent and recurring-authority model is fully documented.