:quality(75))
On December 10, 2024 Adobe released GraphQL endpoints that let a customer save a payment method without completing a purchase. A small change on paper. It removes a constraint that has shaped how subscription and B2B flows had to be built on the platform.
The constraint
Payment vaulting — storing a card or bank account securely for reuse — only worked as part of a purchase transaction in Adobe Commerce (Magento). A customer could vault a card while checking out, but could not add one proactively from their account, and a subscription could not be set up without an opening purchase to hang it on.
What changed
The new GraphQL endpoints separate vaulting from checkout. A customer can save a payment method in their account settings, sign up to recurring billing, or register a card for future purchases, with no transaction attached.
What it unlocks
Subscription services taking payment setup upfront, with no initial purchase
Gift card flows where a payment method is associated for later redemption
Flexible shipping or delayed billing, with the payment method vaulted before the charge
B2B accounts managing several payment methods across their buyers
Implementing it
If you are on Payment Services, start with the endpoint documentation. The endpoints follow standard GraphQL patterns and sit alongside your existing checkout logic rather than replacing it, and Adobe publishes code examples and migration guides.
The wider point is about what you can now sell. Recurring revenue models on Adobe Commerce previously needed either an awkward opening purchase or a workaround. Now they need neither. If subscriptions have been on your roadmap and off your build, this is the piece that was missing.