Openpay Mx Openpay API

Name: Openpay API
Brand: Openpay API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey4 EndpointsREST

For Agents

Process credit-card and alternative payment charges in Mexico and manage Openpay customer profiles for repeat billing.

Install Jentic One Beta

Connect the Openpay API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Openpay 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%2Fopenpay.mx%2Fopenpay-mx" | sh

Step 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%2Fopenpay.mx%2Fopenpay-mx" | 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 Openpay API.

Create a charge against a card or alternative payment method on a merchant account

Retrieve the status of an existing charge by its ID

Create a customer profile that stores cards and contact details for repeat billing

GET STARTED

Start building with Openpay API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Openpay API for, with concrete tasks.

★ Mexican-market e-commerce checkout

An online store serving Mexico routes card payments through Openpay so customers can pay with locally issued credit cards and alternative methods. The /charges endpoint accepts the order amount and payment source, and the merchant retrieves status before fulfilling the order. Setup typically takes a few days including risk and merchant onboarding.

POST to /charges with amount=499.00, currency=MXN, source_id=card_token, and verify the response status is completed.

Stored customer profiles for subscription billing

A SaaS business operating in Mexico creates an Openpay customer for each subscriber, attaches a card token, and reuses the profile for monthly charges. The /customers endpoint stores the profile and the /charges endpoint references the customer ID for each subsequent debit.

Create a customer via POST /customers with name and email, then create a charge referencing the customer_id for the monthly subscription amount.

Order fulfilment based on charge status

A back-office workflow polls the /charges/{chargeId} endpoint to confirm a payment landed before triggering shipment. This avoids fulfilling against pending or failed authorisations and makes the source of truth the charge record itself rather than a webhook race condition.

GET /charges/{chargeId} for the most recent order and only mark the order paid when status is completed.

Agent-driven Mexican payment flows through Jentic

An AI agent that handles checkout for a Mexican retailer calls Openpay via Jentic to create charges and manage customers without embedding API keys in the agent's prompts. Jentic handles credential isolation and exposes the four core operations as discoverable tools.

Search Jentic for 'process a credit card payment in Mexico', load the /charges operation, and execute a 250 MXN charge against a stored customer.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/charges

Create a new charge

GET

/charges/{chargeId}

Retrieve a charge by ID

POST

/customers

Create a new customer profile

GET

/customers/{customerId}

Retrieve a customer profile by ID

POST

/charges

Create a new charge

GET

/charges/{chargeId}

Retrieve a charge by ID

POST

/customers

Create a new customer profile

GET

/customers/{customerId}

Retrieve a customer profile by ID

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Openpay API by hand means sending your key in the Authorization header and shaping charge and customer request bodies with the right amount, currency, and source fields. Through Jentic you install once, import the Openpay API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Openpay puts the customer id in the URL path (/customers/{customerId}), so a rule can pin your agent to reads for one customer. You choose the operations it may call, so charge creation is not included unless you add it.

Credential isolation

Your Openpay API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header 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 card charge in Mexico' or 'look up a customer profile', and Jentic returns the matching Openpay operation with its request schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Openpay API through Jentic.

Why is there no official OpenAPI spec for Openpay API?

Openpay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Openpay API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Openpay API use?

Openpay uses an API key passed in the Authorization header. Through Jentic the key sits in the encrypted vault, and Jentic injects the header at execution time so the secret never appears in agent context.

Can I store cards for recurring billing with the Openpay API?

Yes. Create a customer profile with POST /customers and attach a tokenised card to it; subsequent /charges calls reference the customer_id so the agent does not have to handle raw card data on every billing cycle.

What are the rate limits for the Openpay API?

Openpay applies merchant-level rate limits that are not encoded in the OpenAPI spec. Treat sustained traffic above a few requests per second per merchant as the boundary worth checking with Openpay support before launch.

How do I create a charge through Jentic?

Run pip install jentic, search 'process a credit card payment in Mexico', load the /charges operation, and execute it with the amount, currency, and a card source_id. Jentic supplies the Authorization header and returns the structured charge response.

Does the Openpay API cover payouts or refunds?

The current spec exposes only charges and customers. Refund and payout flows are not part of this four-endpoint surface; for those, an agent would need additional Openpay endpoints not currently described in this spec.

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

Yes. Because you run Jentic One yourself, your own rules decide which Openpay operations and credentials the agent may use, so you can allow only the calls a task needs. For example, you can let the agent read a stored profile with GET /customers/{customerId} while withholding POST /charges, so it cannot create a payment unless you explicitly permit it. Since the customer id sits in the URL path, a rule can even pin the agent to reads for a single customer rather than the whole account.

Openpay Mx Openpay API

Connect the Openpay API to your agent

Capabilities

Start building with Openpay API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs