Omise API

Name: Omise API
Brand: Omise API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbasic44 EndpointsREST

For Agents

Process card and APM payments across Southeast Asia with Omise — create charges, manage saved cards, issue refunds, and transfer settled funds to merchant accounts.

Install Jentic One Beta

Connect the Omise API to your agent

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

Create authorised or captured card charges in THB, JPY, and other supported currencies

Capture, reverse, or expire pending charges via dedicated action endpoints

Issue full or partial refunds against any captured charge

GET STARTED

Start building with Omise API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Omise API, keeping it validated and agent-ready. The Omise API is a payment gateway widely used in Thailand, Japan, and across Southeast Asia for accepting card and alternative-payment-method charges, managing customers and saved cards, issuing refunds, and orchestrating transfers to merchant bank accounts. It exposes 44 endpoints covering charges (with capture/reverse/expire actions), customers and stored cards, tokens, refunds, transfers, recipients, sources for alternative payment methods, and account balance reads. Authentication uses HTTP Basic with a secret key on api.omise.co and a public key on vault.omise.co.

Use Cases

Patterns agents use Omise API for, with concrete tasks.

★ Card Payments for Thai E-Commerce

An e-commerce checkout collects card details client-side using vault.omise.co (public key) to mint a token, then calls POST /charges server-side with the token and amount in THB to capture the payment. Authorise-then-capture flows use POST /charges/{id}/capture so funds are only captured once goods ship.

Create a charge for 1500 THB on a token via POST /charges with capture=false, then call POST /charges/{id}/capture once the order ships.

Refund and Reversal Workflow

When a customer disputes an order, POST /charges/{id}/refunds issues a full or partial refund against a captured charge, while POST /charges/{id}/reverse cancels an uncaptured authorisation cleanly. GET /refunds and GET /charges/{id}/refunds/{refund_id} support reconciliation against the merchant ledger.

POST a refund of 500 THB to /charges/{id}/refunds for a damaged-goods complaint and verify status by reading /charges/{id}/refunds/{refund_id}.

Stored Card and Recurring Charges

POST /customers stores a customer record, then POST /charges with the customer ID re-uses the linked card for follow-up purchases — useful for subscription billing and one-click checkout. PATCH /customers/{id}/cards/{card_id} updates expiry data when banks reissue cards.

POST /customers with email and a token, then POST /charges with the customer ID to charge the saved card 299 THB for a monthly subscription.

AI Agent Payment Operations

An AI agent integrated through Jentic can take a request like 'refund order #4521' and resolve it to the correct charge ID, call POST /charges/{id}/refunds, and surface the refund status — without ever holding the Omise secret key. Jentic encrypts and injects the credential at execution time.

Search Jentic for 'refund an omise charge', load POST /charges/{id}/refunds, look up the charge ID by order, and execute the refund.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/charges

Create a charge

POST

/charges/{id}/capture

Capture an authorised charge

POST

/charges/{id}/refunds

Refund a charge

POST

/customers

Create a customer

POST

/tokens

Create a card token

POST

/transfers

Transfer balance to a recipient

POST

/charges

Create a charge

POST

/charges/{id}/capture

Capture an authorised charge

POST

/charges/{id}/refunds

Refund a charge

POST

/customers

Create a customer

POST

/tokens

Create a card token

POST

Why Jentic?

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

Credential isolation

Omise uses HTTP Basic with separate secret and public keys for server and vault hosts. Jentic stores both keys encrypted in MAXsystem and routes each call to the correct host with the correct key — agents never see either key.

Intent-based discovery

Agents search Jentic for 'create an omise charge' or 'refund an omise payment' and Jentic returns the precise operation (POST /charges, POST /charges/{id}/refunds) with its input schema ready to fill.

Time to first call

Direct integration: 3-5 days for tokenisation, charge, capture, refund, and webhook reconciliation. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using Omise API through Jentic.

Why is there no official OpenAPI spec for Omise API?

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

Omise uses HTTP Basic authentication. Server-side calls to api.omise.co use the secret key as the username (no password); tokenisation calls to vault.omise.co use the public key. Jentic stores both keys in the encrypted vault and selects the right one per endpoint.

Can I issue partial refunds with the Omise API?

Yes. POST /charges/{id}/refunds accepts an amount smaller than the original charge to issue a partial refund. Multiple partial refunds are allowed up to the captured total.

What are the rate limits for the Omise API?

Rate limits are not formally declared in the OpenAPI spec. In practice Omise applies per-account throttles; design clients to back off on HTTP 429 and avoid hammering /charges with the same idempotency context.

How do I save a card for future one-click checkout through Jentic?

Search Jentic for 'save card on omise', and the SDK returns POST /customers and POST /charges. Create the customer with the token, then charge by customer ID for repeat purchases without re-tokenising.

Does the Omise API include disputes and chargebacks?

The OpenAPI spec exposes refunds and reversals but not chargeback adjudication, which Omise handles operationally rather than through this API. Use refund endpoints for merchant-initiated returns.

Omise API

Connect the Omise API to your agent

Capabilities

Start building with Omise API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs