canonical: https://jentic.com/apis/sandbox.volt.io/sandbox-volt

# Sandbox Volt Real-time payments, everywhere.

Join the real-time revolution! Give your customers a faster, easier and safer way to pay. Volt has developed a REST API for merchants, allowing you to offer the option to use Open Banking payments on your online checkout. NEW : API idempotency We have introduced support for idempotency on the POST endpoints in the Volt Connect endpoints of the API. The idea of idempotency is to avoid unwanted dupl. The API exposes 20 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically oauth2 password authentication, bank details. Covers 20 operations with oauth2 authentication.

## Scope

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

## Capabilities

- oAuth2 password authentication
- Bank details
- New payment request
- List payments
- Payment details
- Eligible beneficiaries list

## Use cases

### Payments Operations

Use the Real-time payments, everywhere. to perform payments operations programmatically. The API provides 20 endpoints covering core functionality including oauth2 password authentication, bank details, new payment request.

Example prompt: Call POST /oauth to oauth2 password authentication

### Automated Reporting Management

Automate reporting operations by combining multiple Real-time payments, everywhere. endpoints. Agents can bank details and then new payment request in a single workflow.

Example prompt: Call GET `/banks/{id}` to bank details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Real-time payments, everywhere. 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'oauth2 password authentication', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth` | oAuth2 password authentication |
| GET | `/banks/{id}` | Bank details |
| POST | `/v2/payments` | New payment request |
| POST | `/dropin` | New Embedded checkout |
| GET | `/payments` | List payments |
| GET | `/payments/{id}` | Payment details |
| GET | `/payouts/beneficiaries` | Eligible beneficiaries list |
| POST | `/payouts` | New payout request |

## Key resources

- **Reporting** — Operations related to Reporting
- **Payments** — Operations related to Payments
- **Payouts (Connect)** — Operations related to Payouts (Connect)
- **Refunds (Connect)** — Operations related to Refunds (Connect)
- **Authenticating with the API** — Operations related to Authenticating with the API

## Why Jentic

- **Setup:** Wiring the Volt API by hand means running its OAuth password flow, refreshing tokens against the sandbox or production volt.io host, and handling payment and payout retries yourself. Through Jentic you install once, import Volt from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** Volt puts the payment and bank ids in the URL path (`/payments/{id}`, `/banks/{id}`), so a rule can pin your agent to specific payments: it can read the ones you allow and nothing else. You choose the operations it may call, so writes like creating payments or payouts are not included unless you add them.
- **Credential handling:** Your Volt OAuth 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 'get a payment status' or 'list payout beneficiaries', and Jentic returns the matching Volt 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 Real-time payments, everywhere. use?

The Real-time payments, everywhere. uses OAuth 2.0 for authorization. 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 oauth2 password authentication with the Real-time payments, everywhere.?

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

### What are the rate limits for the Real-time payments, everywhere.?

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 oauth2 password authentication through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'oauth2 password authentication'. Jentic returns the matching Real-time payments, everywhere. operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Real-time payments, everywhere. have?

The Real-time payments, everywhere. exposes 20 endpoints covering reporting, payments, payouts (connect) operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Volt operations and credentials the agent may use. Since Volt puts payment and bank ids in the URL path, such as GET `/payments/{id}` and GET `/banks/{id}`, you can pin the agent to reading only the specific payments you allow. Write operations like POST `/v2/payments` or POST /payouts are not included unless you explicitly grant them.