Clip Mx Clip Payments API

Name: Clip Payments API
Brand: Clip Payments API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbasic15 EndpointsREST

For Agents

Process card payments in Mexico with Clip — create payment links, tokenise cards for transparent checkout, manage transactions, refunds, deposits, and PinPad device payments.

Install Jentic One Beta

Connect the Clip Payments API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clip Payments 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 Clip Payments API.

Create hosted payment links and retrieve them by ID via /payment-links and /payment-links/{id}

Tokenise cards for transparent checkout via POST /tokens

Create and inspect card transactions via POST /charges and /transactions

GET STARTED

Start building with Clip Payments API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Clip Payments API for, with concrete tasks.

★ Online Checkout with Tokenised Cards

Accept online card payments in Mexico without storing PAN data by tokenising the card via /tokens and then charging the token via /charges. The transparent checkout flow keeps the merchant out of PCI scope while still supporting custom checkout UX.

Tokenise a card via POST /tokens, then charge the token via POST /charges with the amount in MXN and the order reference.

Hosted Payment Links for Invoicing

Generate Clip payment links and send them to customers when an in-app checkout is not available — useful for invoices, deposits, and one-off charges. Once paid, the merchant retrieves the link state via /payment-links/{id} to confirm settlement.

Create a payment link via POST /payment-links for 1500 MXN and send the returned URL to the customer, then poll /payment-links/{id} until the link is paid.

In-Person PinPad Card-Present Payments

Drive Clip PinPad terminals from a back-office or kiosk app by initiating a payment, polling the device, and confirming completion. The /f2f/pinpad/v1/payment, /f2f/pinpad/v1/devices/status, and /f2f/pinpad/v1/payment/serial-number/{serialNumber} endpoints together support card-present sales without closing on-screen flows.

Trigger a PinPad payment via POST /f2f/pinpad/v1/payment for the device serial, then poll /f2f/pinpad/v1/payment/{paymentId} until the result is final.

Settlement and Refund Reconciliation

Reconcile Clip activity against bank deposits and accounting entries by pulling transactions, refunds, settlements, and deposit records on a daily basis. The /transactions, /refunds, /settlements, and /deposits endpoints provide the underlying records for finance teams.

Pull /settlements and /deposits for the previous day, join the records to /transactions, and emit a reconciliation report against the merchant bank statement.

AI Agent Payments for Mexican Merchants via Jentic

An AI agent that handles billing for a Mexican merchant can create payment links, charge tokenised cards, issue refunds, or trigger PinPad terminals by searching Jentic for the matching Clip operation. Jentic vaults the Basic auth credentials so the agent never holds them directly.

Use the Jentic search query 'create a payment link' to find POST /payment-links and execute with the amount and order reference.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/payment-links

Create a hosted payment link

POST

/tokens

Tokenise a card for transparent checkout

POST

/charges

Charge a tokenised card

POST

/refunds

Issue a refund

GET

/transactions

List transactions

GET

/settlements

List settlement records

POST

/f2f/pinpad/v1/payment

Trigger a card-present payment on a PinPad device

GET

/f2f/pinpad/v1/devices/status

Check PinPad device status

POST

/payment-links

Create a hosted payment link

POST

/tokens

Tokenise a card for transparent checkout

POST

/charges

Charge a tokenised card

POST

/refunds

Issue a refund

GET

/transactions

List transactions

GET

Why Jentic?

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

Credential isolation

The Clip HTTP Basic credentials are stored encrypted in the Jentic vault. Agents receive scoped execution rights and never hold the raw username and password.

Intent-based discovery

Agents search Jentic by intent such as 'create a payment link' or 'issue a refund' and Jentic returns the matching Clip operation with its input schema.

Time to first call

Direct Clip integration: 2-3 days to wire up checkout, refunds, settlements, and PinPad. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Global card processing with broad currency and method coverage

Choose Stripe when the merchant needs multi-country, multi-currency processing rather than a Mexico-focused acquirer.

Alternative

Conekta

Mexico-focused payments processor with cards and OXXO support

Choose Conekta when the workflow needs OXXO cash payments or SPEI bank transfers alongside cards in Mexico.

Complementary

Stripe

Global processing for cross-border revenue alongside local Mexican acquirer

Pair Stripe with Clip when the merchant has both Mexican domestic and international customers and wants the local acquirer for MXN.

FAQs

Specific to using Clip Payments API through Jentic.

Why is there no official OpenAPI spec for Clip Payments API?

Clip does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clip Payments 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 Clip Payments API use?

The API uses HTTP Basic authentication for server-side calls. Through Jentic the Basic credentials are stored encrypted in the vault and the agent only ever holds a scoped execution context.

Can I tokenise a card and charge it with the Clip API?

Yes. POST a card payload to /tokens to receive a token, then POST that token to /charges with the amount and currency to authorise the charge. This keeps the merchant out of PCI scope on the card data path.

How do PinPad payments work?

Trigger a payment on a registered device via POST /f2f/pinpad/v1/payment with the device serial, then poll /f2f/pinpad/v1/payment/{paymentId} until the cardholder taps or inserts and the payment finalises. Device readiness can be checked via /f2f/pinpad/v1/devices/status.

How do I issue a refund through Jentic?

Search Jentic for 'issue a refund', load the schema for POST /refunds, and execute with the original transaction ID and the refund amount. The Python SDK uses await client.search, await client.load, await client.execute.

Does Clip support multiple currencies?

Clip is focused on Mexican peso (MXN) processing for Mexican merchants. The /charges and /payment-links endpoints accept MXN amounts; cross-border or multi-currency flows are not in scope of this API.