For Agents
Programmatically create a new payment order, query order status. Covers 4 operations with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ZaloPay 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzalopay.vn%2Fzalopay-vn" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzalopay.vn%2Fzalopay-vn" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with ZaloPay API.
Create a new payment order
Query order status
Integrate ZaloPay API into automated workflows
Query and filter ZaloPay API records by parameters
GET STARTED
Use for: I need to a new payment order, I want to query order status, Search for a refund, Find all query refund status
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
ZaloPay payment gateway API enabling merchants to create payment orders, process refunds, query order status, manage tokenization, and handle disbursements. Supports multiple payment channels in Vietnam. The API exposes 4 endpoints secured with apiKey authentication.
Monitor ZaloPay API operational status and events
Patterns agents use ZaloPay API for, with concrete tasks.
★ Payments Operations
Use the ZaloPay API to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including create a new payment order, query order status, create a refund.
Call POST /create to create a new payment order
Automated Orders Management
Automate orders operations by combining multiple ZaloPay API endpoints. Agents can query order status and then create a refund in a single workflow.
Call POST /query to query order status, then verify the result
AI Agent Integration via Jentic
AI agents discover and call ZaloPay API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create a new payment order', load the operation schema, and execute with Jentic-managed credentials
4 endpoints — zalopay payment gateway api enabling merchants to create payment orders, process refunds, query order status, manage tokenization, and handle disbursements.
METHOD
PATH
DESCRIPTION
/create
Create a new payment order
/query
Query order status
/refund
Create a refund
/query_refund
Query refund status
/create
Create a new payment order
/query
Query order status
/refund
Create a refund
/query_refund
Query refund status
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ZaloPay by hand means computing its HMAC signature over each request, passing the mac in the query string, and matching the openapi.zalopay.vn/v2 host yourself. Through Jentic you install once, import ZaloPay from the API Directory, store the key once, and your agent calls it.
Permission scoping
ZaloPay carries the order details in the request body rather than the URL path, so limit the agent to the operations it needs, such as creating an order or querying its status. You leave out refund and refund-query operations unless the agent is meant to issue money back.
Credential isolation
Your ZaloPay key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a payment order' or 'check refund status', and Jentic returns the matching ZaloPay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using ZaloPay API through Jentic.
What authentication does the ZaloPay API use?
The ZaloPay API uses an API key passed in the `mac` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a new payment order with the ZaloPay API?
Yes. Use the POST /create endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the ZaloPay API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new payment order through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new payment order'. Jentic returns the matching ZaloPay API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the ZaloPay API have?
The ZaloPay API exposes 4 endpoints covering orders, refunds operations.
Can I limit what my agent is allowed to do with the ZaloPay API?
Yes. Because you run Jentic One yourself, your own rules decide which ZaloPay operations and credentials the agent may use. You can allow it to create payment orders with POST /create and check status with POST /query while leaving out the refund and refund-query operations, so it cannot issue money back unless you explicitly permit it. Your ZaloPay key is stored encrypted in your own instance and injected only for the calls you allow.