GoPay REST API

Name: GoPay REST API
Brand: GoPay REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingoauth2,basic10 EndpointsREST

For Agents

Create payments, manage recurrences and preauthorizations, and pull account statements through the GoPay payment gateway with OAuth2 scoped tokens.

Connect the GoPay REST API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 GoPay REST API.

Create a payment with hosted redirect or inline checkout against a specific eshop GoID

Capture a preauthorized payment when an order is fulfilled

Issue a partial or full refund on any captured payment

Trigger an on-demand recurrence against a parent recurring payment

GET STARTED

Start building with GoPay REST API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for GoPay REST API, keeping it validated and agent-ready. The GoPay REST API processes online payments via the Czech and Slovak GoPay gateway, covering payment creation, status retrieval, refunds, captures, on-demand recurrences, and authorization voids. It exposes 10 endpoints under https://gate.gopay.cz/api with OAuth2 bearer tokens issued from a client_id and client_secret over HTTP Basic. The same spec also surfaces eshop payment instrument lookup and account statement download for reconciliation.

Use Cases

Patterns agents use GoPay REST API for, with concrete tasks.

★ Local Czech Checkout

Accept payments from Czech and Slovak shoppers using bank buttons, the GoPay wallet, and card schemes. The integration creates a payment, redirects the shopper to the hosted gateway, and exposes a status endpoint for the merchant backend to confirm settlement before fulfillment.

Create a GoPay payment for 2499 CZK against goid 8123456789, return the gateway redirect URL, and verify state transitions to PAID.

Recurring Subscription Billing

Run subscription products by creating a parent recurring payment and triggering each scheduled charge against it. Recurrences inherit the saved instrument, succeed without redirecting the shopper, and can be ended at any point with the void-recurrence endpoint when the customer cancels.

Trigger a 299 CZK monthly recurrence on parent payment id 3000222333 on the first of each month and stop the chain if a recurrence fails twice in a row.

Marketplace Authorization Hold

Hold funds at order placement using a preauthorization, then capture only the portion that ships. Authorization holds can be released entirely with void-authorization or settled with capture, matching marketplace and made-to-order patterns where the final billable amount is unknown at checkout.

Capture 1450 CZK on preauthorized payment id 3000777888 when the seller marks the order shipped, otherwise call void-authorization within seven days.

AI Agent Settlement Reconciliation

An automated finance agent pulls the GoPay account statement on a schedule, joins it against internal orders, and surfaces unmatched transactions. Through Jentic, the agent searches by intent, receives the right operation and schema, and uses scoped OAuth2 tokens issued from the encrypted vault.

Fetch /accounts/account-statement for the date range 2026-06-01 to 2026-06-09 and return any PAID payments missing from the orders database.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/oauth2/token

Issue an OAuth2 bearer token

POST

/payments/payment

Create a new payment

GET

/payments/payment/{id}

Retrieve a payment by id

POST

/payments/payment/{id}/refund

Refund a captured payment

POST

/payments/payment/{id}/create-recurrence

Trigger a recurrence on a parent payment

POST

/payments/payment/{id}/capture

Capture a preauthorized payment

POST

/payments/payment/{id}/void-authorization

Void an open authorization

GET

/accounts/account-statement

Download an eshop account statement

POST

/oauth2/token

Issue an OAuth2 bearer token

POST

/payments/payment

Create a new payment

GET

/payments/payment/{id}

Retrieve a payment by id

POST

/payments/payment/{id}/refund

Refund a captured payment

POST

/payments/payment/{id}/create-recurrence

Trigger a recurrence on a parent payment

Why Jentic?

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

Credential isolation

GoPay client_id and client_secret are encrypted in the Jentic vault (MAXsystem). Agents receive short-lived OAuth2 bearer tokens scoped to the requested permission and never see raw credentials.

Intent-based discovery

Agents search by intent (e.g., 'capture a preauthorization') and Jentic returns the matching GoPay operation with input schema, so the agent calls the right endpoint without reading vendor docs.

Time to first call

Direct GoPay integration: 3-5 days for OAuth2 wiring, recurrence handling, and reconciliation. Through Jentic: under 1 hour from search to execution.

FAQs

Specific to using GoPay REST API through Jentic.

Why is there no official OpenAPI spec for GoPay REST API?

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

OAuth2 client credentials over HTTP Basic. POST client_id and client_secret to /oauth2/token, request a scope of payment-create, payment-all, or account-statement, and use the returned bearer token in the Authorization header. Jentic stores the secret in its encrypted vault and rotates tokens automatically.

Can I issue partial refunds through the GoPay API?

Yes. POST /payments/payment/{id}/refund with an amount field smaller than the original payment to refund partially. Omitting the amount issues a full refund. The parent payment is updated so subsequent GETs reflect the remaining captured balance.

How do recurring payments work on GoPay?

Create the first payment with a recurrence object describing the cycle, then POST /payments/payment/{id}/create-recurrence against the parent payment id for each charge. POST /payments/payment/{id}/void-recurrence ends the chain when a customer cancels.

How do I integrate the GoPay API with an AI agent through Jentic?

Run pip install jentic, search 'create a gopay payment' to find POST /payments/payment, load the input schema, and execute. Jentic handles the OAuth2 token exchange so the agent never sees the client secret. Get started at https://app.jentic.com/sign-up.

GoPay REST API

Connect the GoPay REST API to your agent

Capabilities

Start building with GoPay REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs