canonical: https://jentic.com/apis/satispay.com/satispay

# Satispay Business API

Satispay API for payment processing, meal vouchers, fringe benefits, and pre-authorized payments. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically create payment, get list of payments. Covers 11 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Create payment
- Get list of payments
- Update payment
- Query and filter Satispay Business API records by parameters
- Monitor Satispay Business API operational status and events

## Use cases

### Payments Operations

Use the Satispay Business API to perform payments operations programmatically. The API provides 11 endpoints covering core functionality including create payment, get list of payments, get payment details.

Example prompt: Call POST `/g_business/v1/payments` to create payment

### Automated Payments Management

Automate payments operations by combining multiple Satispay Business API endpoints. Agents can get list of payments and then get payment details in a single workflow.

Example prompt: Call GET `/g_business/v1/payments` to get list of payments, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Satispay Business 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 bearer tokens manually.

Example prompt: Search Jentic for 'create payment', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/g_business/v1/payments` | Create payment |
| GET | `/g_business/v1/payments` | Get list of payments |
| GET | `/g_business/v1/payments/{id}` | Get payment details |
| PUT | `/g_business/v1/payments/{id}` | Update payment |
| POST | `/g_business/v1/meal_voucher/payments` | Create meal voucher payment |
| GET | `/g_business/v1/meal_voucher/payments/{id}` | Get meal voucher payment details |
| POST | `/g_business/v1/pre_authorized_payment_tokens` | Create authorization |
| GET | `/g_business/v1/pre_authorized_payment_tokens/{token}` | Get authorization |

## Key resources

- **Payments** — Payment operations
- **Meal Vouchers** — Meal voucher payment operations
- **Pre-Authorized Payments** — Pre-authorized payment authorization operations
- **Reports** — Merchant report operations

## Why Jentic

- **Setup:** Wiring the Satispay Business API by hand means building its RSA signature authentication with a public and private key pair, targeting the authservices host, and tracking payment state yourself. Through Jentic you install once, import the Satispay Business API from the API Directory, store the key credentials once, and your agent calls it.
- **Permission scoping:** Satispay puts the payment id in the URL path (`/g_business/v1/payments/{id}`), so a rule can pin your agent to one payment. You choose the operations it may call, so a state-changing one like updating a payment is not included unless you add it alongside the read.
- **Credential handling:** Your Satispay Business API key credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment' or 'check a payment status', and Jentic returns the matching Satispay Business API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Satispay Business API use?

The Satispay Business API uses a Bearer token in the Authorization header. 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 payment with the Satispay Business API?

Yes. Use the POST `/g_business/v1/payments` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Satispay Business 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 payment through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create payment'. Jentic returns the matching Satispay Business API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Satispay Business API have?

The Satispay Business API exposes 11 endpoints covering payments, meal vouchers, pre-authorized payments operations.

### Can I limit what my agent is allowed to do with the Satispay Business API?

Yes. Because you run Jentic One yourself, your own rules decide which Satispay operations and credentials the agent may use. Satispay puts the payment id in the URL path (`/g_business/v1/payments/{id}`), so a rule can pin your agent to a single payment, and you choose the operations it may call. A read like GET `/g_business/v1/payments/{id}` can be allowed while a state-changing operation such as PUT `/g_business/v1/payments/{id}` stays excluded unless you add it.