Is vault available in P3?
Maya Vault is not available within the Payments Processing Platform (P3). Vault is a separate service designed for tokenizing and storing card details, accessible via the /payments/v1/ endpoints (e.g., /payments/v1/customers, /payments/v1/payment-tokens). P3 handles transaction processing (e.g., payments, refunds, inquiries) but does not support card vaulting. To use vaulted cards, integrate with Maya Vault separately and then use the vaulted card tokens in P3 transactions via the ‘Create Customer Payment’ endpoint.
For Sandbox concerns and other technical implementation inquiries, please get in touch with us via:
- Sandbox Health Page: Check real-time service status updates.
- Maya Developer Hub Service Desk: File
a ticket in Sandbox.
To Know More:
We value your input and would love to hear your insights. Please submit you feedback here.
Are tokenized payments available in PWM?
Hello @Ralphkatipunan, ![]()
Just to clarify, are you looking for a solution for recurring or future payments? If so, here’s how each product supports that use case:
-
Payments Processing Platform (P3) supports recurring card payments through Merchant-Initiated Transactions (MIT). After a successful initial card payment, you can trigger future payments on behalf of the cardholder by setting
transaction.frequencyIndicatortoRECURRING.For more details, refer to: https://developers.maya.ph/docs/payments-processing-platform-recurring-transactions
-
Pay with Maya (PWM) is a wallet-based payment method, so card tokenization isn’t applicable. Instead, you can use Maya Account Linking to securely link a customer’s Maya account and perform future wallet payments without requiring them to log in again for every transaction.
More information is available here: https://developers.maya.ph/docs/maya-account-linking
If you’re specifically looking for card vaulting or card tokenization (storing a payment credential for future card payments across different payment flows), then the recommended product is Maya Vault.
Let us know if your use case is recurring payments, card tokenization, or something else, and we’d be happy to recommend the most suitable solution. ![]()