My partner and I recently decided to go with a different solution that better fits our current development and business needs. That said, I still wanted to share some feedback on the technical documentation in the Maya Developer Hub.
Overall, I appreciate that you guys listen to my feedback (on GooglePay). But as someone who went through the guides, especially on Maya Vault, I couldn’t help but notice that the documentation feels inconsistent across solutions. It almost feels like Maya Checkout was the favorite child in terms of how it was written and structured.
Maya Checkout stands out compared to other solutions in the DevHub. It does a better job of guiding the developer through out the integration. There are still gaps and questions, but it’s much easier to follow.
For Maya Vault, I think the intent is clear, but the execution makes it harder than it needs to be for us developers:
It explains what Vault does, but not when it is the right choice compared to other payment flows.
It focuses on APIs (save card, pay using token), but not the full real-world lifecycle like retries, failures, expired cards, and recovery flows.
Key concepts like webhooks, statuses, and refunds feel disconnected and requires us developers to mentally determined which applies to Maya Vault
Vault enables recurring payments, but there’s no clear mental model of how subscription systems should be built on top of it.
Edge cases like soft declines, token invalidation, failed renewals, and reconciliation scenarios are not really surfaced, which are usually the things that hurt most in production.
Thank you for your detailed and thoughtful feedback. We appreciate you taking the time to share your experience with the Maya Developer Hub, especially regarding the documentation for Maya Vault. Your observations about the inconsistency in documentation quality — particularly when compared to Maya Checkout — are valuable and align with internal efforts to improve the developer experience across all solutions. We acknowledge that Maya Vault’s documentation currently lacks a cohesive narrative around real-world integration lifecycles, including retries, failures, token invalidation, recurring payment models, and reconciliation. These gaps can indeed make integration more challenging than necessary. Your point about disconnected concepts like webhooks, statuses, and refunds across solutions is well-taken; we are working to unify these patterns and provide clearer guidance on when to use Vault versus other payment flows. Your feedback will be directly shared with our documentation and product teams to prioritize improvements in structure, depth, and practical guidance for all solutions, not just Maya Checkout. We’re committed to ensuring every integration path in the Developer Hub is as clear, complete, and supportive as possible.
For any concerns regarding Production transactions, Maya Terminals, product inquiries,
or onboarding requests, please get in touch with us via:
I also noticed across the Maya Developer Hub is that the side navigation/table of contents can feel overwhelming, there are too many solutions and products surfaced within the same documentation portal.
Instead of feeling like a guided entry point per solution, it sometimes feels like a single long catalog of all possible integrations, which increases cognitive load during onboarding.
Don’t know how to resolve it but hoping for a more focused and dedicated learning path in the future DevHub.
Hey @Dina, thanks for appreciating the Maya Checkout documentation structure and for taking the time to share your detailed feedback on Maya Vault and the side navigation. We truly appreciate it.
We’ve taken note of your insights and have already shared them with both our documentation and development teams for review and consideration.
We look forward to seeing you again in the Maya Developer Hub and Forum. Please don’t hesitate to continue sharing your thoughts and insights. Feedback like yours is valuable in helping us improve the overall developer experience and the community.