8B World Payment API

Name: 8B World Payment API
Brand: 8B World Payment API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer16 EndpointsREST

For Agents

Provision and manage 8B World admin accounts, settlement accounts, settlement instruments, and contacts via a bearer-authenticated REST API. Use it to run back-office configuration tasks for a payment processing program.

Install Jentic One Beta

Connect the 8B World Payment API to your agent

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

Authenticate admin sessions and refresh tokens through the OAuth client-credentials endpoints

Create, retrieve, and update admin accounts that own settlement configuration

Toggle admin account status to activate, suspend, or close an operator

GET STARTED

Start building with 8B World Payment API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use 8B World Payment API for, with concrete tasks.

★ Merchant Onboarding for a Payment Program

When a payment program operator brings a new merchant onto 8B World, the back office must create the admin account, attach a settlement account with the correct bank details, register the settlement instrument, and add finance and operations contacts. The 8B World Payment API exposes each of these steps as discrete endpoints, so onboarding can be scripted end-to-end rather than entered through a portal. A complete onboarding sequence runs in under a minute once authentication is in place.

Create an admin account, then create a linked settlement account with merchant bank IBAN, then register a card settlement instrument, and verify status is active

Settlement Configuration Updates

Settlement details change frequently in payment operations: a merchant updates a bank account, a finance contact rotates, or a settlement instrument is replaced. The 8B World Payment API supports targeted PUT and PATCH operations on settlement accounts, settlement instruments, and contacts, so update flows can run without rebuilding the entire admin record. This keeps settlement reliable when underlying details change mid-cycle.

Update the bank account on settlement account ID 1234 and patch the admin account status to active

Operator Status Management

Compliance and risk teams need to suspend or restore admin accounts quickly when issues are detected. The 8B World Payment API offers a dedicated PATCH endpoint on the admin account status field, separating routine updates from sensitive status transitions. This lets reviewers act in near real time without exposing the rest of the admin record to mass updates.

Patch the status of admin account ID 7821 to suspended and confirm the change with a follow-up GET

Agent-Driven Back-Office Automation

AI agents can drive 8B World admin tasks through Jentic without browsing the portal or hand-rolling auth. A single Jentic search returns the right operation along with its input schema, and credentials stay isolated in your Jentic One instance. Agents handle ticket-driven onboarding and updates while humans review the resulting records.

Search Jentic for 'create an 8B World admin account', load the schema, and execute the call with the merchant's details

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for 8b world payment api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/admin-accounts/oauth/authorize

Obtain a client access token

POST

/api/v1/admin-accounts

Create an admin account

PATCH

/api/v1/admin-accounts/{id}/status

Modify admin account status

POST

/api/v1/admin-accounts/settlement-accounts

Create a settlement account

POST

/api/v1/admin-accounts/settlement-instruments

Create a settlement instrument

POST

/api/v1/admin-accounts/settlement-accounts-contacts/contacts

Create contacts on a settlement account

POST

/api/v1/admin-accounts/oauth/authorize

Obtain a client access token

POST

/api/v1/admin-accounts

Create an admin account

PATCH

/api/v1/admin-accounts/{id}/status

Modify admin account status

POST

/api/v1/admin-accounts/settlement-accounts

Create a settlement account

POST

/api/v1/admin-accounts/settlement-instruments

Create a settlement instrument

Why Jentic?

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

Credential isolation

Your 8B World bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a settlement account' or 'update an admin account status', and Jentic returns the matching 8B World operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using 8B World Payment API through Jentic.

Why is there no official OpenAPI spec for 8B World Payment API?

8B World does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 8B World Payment API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the 8B World Payment API use?

The API uses HTTP bearer authentication. Clients first call POST /api/v1/admin-accounts/oauth/authorize to obtain an access token, then send it as Authorization: Bearer <token> on every subsequent call. Through Jentic, the bearer token is held in your Jentic One instance and injected at execution time, so the raw token never reaches the agent's prompt.

Can I create and update settlement accounts with the 8B World Payment API?

Yes. POST /api/v1/admin-accounts/settlement-accounts creates a settlement account, GET /api/v1/admin-accounts/settlement-accounts/{id} retrieves it, and PUT on the same path updates it. Settlement instruments and contacts attached to the account each have their own endpoints under /api/v1/admin-accounts/settlement-instruments and /api/v1/admin-accounts/settlement-accounts-contacts.

How do I suspend an admin account through Jentic?

Search Jentic for 'change admin account status' to find PATCH /api/v1/admin-accounts/{id}/status, load the schema, and execute the call with the new status value. Jentic returns the structured response so an agent can verify the change with a follow-up GET on the same admin account ID.

What are the rate limits for the 8B World Payment API?

The OpenAPI spec does not document explicit rate limits. Treat the API as standard back-office tooling: serialize bursts of writes and add retry with backoff for any 429 or 5xx responses. Confirm production limits with 8B World support before high-volume use.

How do I terminate an 8B World session?

Call POST /api/v1/admin-accounts/oauth/logout with the active bearer token to invalidate the session. Through Jentic, this can be wired into an agent's cleanup step so credentials are not left active longer than necessary.

Can I limit what my agent is allowed to do with the 8B World Payment API?

Yes. Jentic One is self-hosted, so your own rules decide which 8B World operations and credentials the agent may use. Because the API puts the admin-account id in the URL path, such as PATCH /api/v1/admin-accounts/{id}/status, you can pin the agent to one admin account for a status change. You also choose the operations it may call, so creating settlement accounts or registering settlement instruments stays off limits unless you explicitly allow it.

8B World Payment API

Connect the 8B World Payment API to your agent

Capabilities

Start building with 8B World Payment API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs