Maya Ph Maya API

Name: Maya API
Brand: Maya API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbasic11 EndpointsREST

For Agents

Process payments, tokenize cards, generate payment links, and run remittances and transfers on Maya's Philippines payment platform.

Install Jentic One Beta

Connect the Maya API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Maya API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Maya API.

Create hosted checkout sessions for one-time card and wallet payments

Charge a saved card token directly without a hosted page

Tokenize a card into the Maya vault for repeat charges

Generate shareable payment links with custom amounts and metadata

GET STARTED

Start building with Maya API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Maya API, keeping it validated and agent-ready. Maya is the Philippines' digital financial services platform, and its API exposes checkout, direct payments, vault tokenization, payment links, remittances, transfers, and bill payments. Agents can build full Filipino-market checkout flows, accept card and wallet payments, store payment instruments for recurring use, and move money across the Maya network. The 11 operations cover the end-to-end payment lifecycle from intent creation to refund.

Use Cases

Patterns agents use Maya API for, with concrete tasks.

★ Philippines E-Commerce Checkout

Accept card and Maya wallet payments on a Philippines storefront using Maya's hosted checkout. The /v1/checkout endpoint creates a session with the cart total, currency, and a redirect URL, and the buyer completes payment on a Maya-hosted page that handles 3D Secure and wallet selection. Settlement clears to the merchant's Maya merchant account in PHP, with webhooks confirming payment success.

Create a checkout session for PHP 1,499 with description 'Order #12345', a success URL of /thanks, and a failure URL of /retry, then return the redirect URL to the caller.

Card Vaulting for Subscriptions

Store a customer's card once via Maya's vault and charge it on each renewal cycle without re-prompting for card details. The /v1/vault/tokens endpoint creates a token bound to a payment instrument, and subsequent /v1/payments calls reference the token to execute the charge. This is the standard pattern for SaaS, telco, and streaming subscriptions targeting Filipino customers.

Create a vault token for the supplied card details, then immediately charge that token PHP 299 with description 'Monthly subscription — June'.

Payment Link Distribution Over Chat

Send shoppers a tokenised, single-use payment link via Viber, Messenger, or SMS so they can pay without leaving the conversation. The /v1/payment-links endpoint accepts amount, currency, and metadata and returns a short URL that opens the Maya hosted page. Conversational commerce teams use this pattern to convert chat enquiries into completed orders without building a full storefront.

Generate a payment link for PHP 750, expiring in 24 hours, with metadata.order_id=ORD-987, then return the short URL.

AI Agent for Payment Reconciliation

Build an agent that reconciles Maya payment status into an internal order ledger by polling /v1/payments/{paymentId} for pending records, marking matched orders as paid, and refunding stuck transactions when a duplicate is detected. The agent searches Jentic for the relevant Maya operations, loads schemas, and executes calls using vault credentials. This removes hours of manual reconciliation per day for high-volume merchants.

For each order in the 'pending' table older than 30 minutes, call GET /v1/payments/{paymentId}, update the order status to match, and refund duplicates by calling the refund operation with the original paymentId.

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for maya api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/checkout

Create a hosted checkout session

POST

/v1/payments

Create a direct payment

GET

/v1/payments/{paymentId}

Retrieve a payment by id

POST

/v1/vault/tokens

Create a vault token from card details

POST

/v1/payment-links

Generate a shareable payment link

POST

/v1/remittances

Initiate a remittance to a bank account

POST

/v1/transfers

Send a peer-to-peer or merchant transfer

POST

/v1/bills/payments

Pay a biller programmatically

POST

/v1/checkout

Create a hosted checkout session

POST

/v1/payments

Create a direct payment

GET

/v1/payments/{paymentId}

Retrieve a payment by id

POST

/v1/vault/tokens

Create a vault token from card details

POST

/v1/payment-links

Generate a shareable payment link

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Maya public and secret keys are stored encrypted in the Jentic vault (MAXsystem). The correct key is selected per operation (public for checkout, secret for vault and refunds) and converted into a Basic auth header at execution time, so the secret key never enters the agent's transcript.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a Maya payment link') and Jentic returns the matching Maya operation with its input schema, so the agent can call the right endpoint without browsing developers.maya.ph.

Time to first call

Direct Maya integration: 2-5 days for sandbox setup, public/secret key handling, webhook signature verification, and refund flows. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using Maya API through Jentic.

Why is there no official OpenAPI spec for Maya API?

Maya does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Maya API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.

Maya Ph Maya API

Connect the Maya API to your agent

Capabilities

Start building with Maya API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs