What authentication does the Maya API use?

Maya uses HTTP Basic authentication where the merchant's API key is passed as the username. Public keys are used for client-side calls (checkout) and secret keys for server-side calls (vault, refunds). Through Jentic, both keys are stored in your Jentic One instance and selected per-operation, so the secret key never enters the agent's context.

Can I tokenize cards with the Maya API?

Yes. POST /v1/vault/tokens accepts card details and returns a token that can be charged via /v1/payments without re-entering card data. This is the basis for subscription and one-click checkout flows on the Maya platform.

What are the rate limits for the Maya API?

Maya enforces per-merchant rate limits documented at developers.maya.ph and varies by environment (sandbox is more permissive than production). Responses use 429 status codes with retry guidance when limits are hit; agents should implement exponential back-off for batch reconciliation jobs.

How do I create a checkout session with the Maya API through Jentic?

Search Jentic for 'create a Maya checkout session', load the schema for POST /v1/checkout, and execute with totalAmount, requestReferenceNumber, and redirectUrl. Jentic attaches the public-key Basic auth header automatically and returns the hosted checkout URL.

Does the Maya API support refunds?

Yes. Refunds are issued against an existing paymentId via the payments resource. Partial refunds are supported by specifying the refund amount; the API returns a refund record with its own status that can be polled for settlement confirmation.

Can I send remittances with the Maya API?

Yes. POST /v1/remittances initiates a transfer to a Philippine bank account or Maya wallet, and POST /v1/transfers handles peer-to-peer and merchant-to-customer payouts. Both require server-side secret-key authentication and are subject to KYC and AML checks on the Maya side.

Can I limit what my agent is allowed to do with the Maya API?

Yes. Because you run Jentic One yourself, your own rules decide which Maya operations and keys the agent may use, and it calls only the operations you allow. Since Maya's payment, transfer, and remittance targets travel in the request body rather than a resource id in the URL, you scope access at the operation level, for example allowing create-checkout and payment-link calls while excluding money movement like transfers and remittances. You can also keep the public key available for checkout while withholding the secret key that server-side operations require.