Official headless payment compatibility matrix

[mdanilowicz]

Problem we must solve

Headless implementations of payments method are currently not consistently documented or validated across supported platforms and integrations. Developers building CF apps, do not have a clear reference showing:

• Which payment methods work in headless mode
• Which features are fully supported, partially supported, or unsupported
• What limitations or required workarounds exist

WHY we need to solve it

• Reduce Integration Friction
• Set Clear Expectations for Developers
• Improve Developer Experience
• Reduce Support and Internal Questions
• Align Product, Documentation, and Engineering

Solution to the problem

No response

WHO benefits

No response

WHERE will we do it

• Composable Frontends documentation

Out of scope

No response

Acceptance criteria

• A Headless Payment Compatibility Matrix is created and added to the official documentation.
• For each payment method, the matrix clearly indicates support status using consistent labels: [Supported, Partially supported, Not supported]
• The structure allows easy updates when new payment methods or capabilities are added.
• If there is a possibility, create tasks for payment that are not supported

[lasomethingsomething]

Would these payment methods make sense to include in rows?

• Invoice (Manual)
• Prepayment
• Cash on Delivery
• PayPal
• Stripe redirect-based)
• Stripe (embedded elements)
• Klarna
• Adyen
• Amazon Pay
• Mollie
• Any others?

Would these features make sense in columns? ([Supported/"yes", "Partially supported," Not supported/"no"]):

• Headless Checkout available
• Redirect Flow available
• Embedded/iFrame
• Webhooks required
• Saved Methods
• Subscriptions
• Status
• Notes/Limitations/Recommended Workarounds
• Anything else?