Install Jentic One Beta

Connect the Transaction Broker API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Transaction Broker 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbankofamerica.com%2Fbankofamerica" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbankofamerica.com%2Fbankofamerica" | 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 Transaction Broker API.

Process card, ACH, and cash transactions through dispatcher endpoints under /transactions/process/*

Refund, void, capture, reverse, or adjust an existing transaction by its ID

Store tokenised card or ACH contracts per merchant and customer for repeat billing

Generate hosted payment pages for browser-based payment collection

GET STARTED

Start building with Transaction Broker API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Transaction Broker API for, with concrete tasks.

★ In-Person Retail Checkout

Run in-person checkout at a Bank of America merchant terminal: create a transaction, send it to /transactions/process/card, then poll /transactions/{id} until processing finishes. The Transaction Broker dispatches the work to the named terminal and returns the result, including any cardholder prompts captured by the device. This replaces direct integration with each terminal model.

Create a transaction with POST /transactions, send it to /transactions/process/card with the target terminal, then GET /transactions/{id} until status is final.

Tokenised Recurring Billing

Store a customer's card or ACH instrument once via /merchants/{merchant_id}/contracts/card or /merchants/{merchant_id}/contracts/ach, then charge the contract on each billing cycle without re-collecting payment details. Contracts are scoped per merchant and per customer and can be retrieved, updated, or deleted as the customer's instruments change.

Create a card contract via POST /merchants/{merchant_id}/contracts/card with a token, then charge it on the next cycle by referencing the contract in POST /transactions.

Hosted Payment Pages and Receipts

Generate a hosted payment page (HPP) via POST /hpps and forward the link to the customer for browser-based payment. After processing, render and surface the receipt with GET /transactions/receipt/render or list receipts with GET /receipts. Print jobs can be queued to a connected receipt printer through POST /print_receipts.

Generate an HPP via POST /hpps for $129.99, send the link to the customer, then render the receipt with GET /transactions/receipt/render once payment is captured.

AI Agent Integration via Jentic

An agent built on Jentic can drive an in-person checkout: create the transaction, dispatch to a specific terminal, and watch the result without holding the api_id:api_token credentials. Jentic stores the ISVAuth and TerminalAuth credentials in your Jentic One instance so the agent never sees the encoded values.

Search Jentic for 'process a transaction broker card payment', load the schema for POST /transactions/process/card, and execute it with the transaction ID and target terminal serial.

Key Endpoints

32 endpoints — bank of america's transaction broker is the central system that manages ongoing payment transactions, dispatches them to point-of-sale terminals, returns results, and maintains the mapping between organisations, terminals, and customers.

METHOD

PATH

DESCRIPTION

POST

/transactions

Create a transaction

POST

/transactions/process/card

Send a card transaction to a terminal for processing

POST

/transactions/refund/card

Refund a card transaction

POST

/transactions/void

Void a transaction

POST

/merchants/{merchant_id}/contracts/card

Create a stored card contract for a customer

POST

/hpps

Generate a hosted payment page

GET

/terminals/status

Get a terminal's status by serial number or client ID

POST

/print_receipts

Create a print receipt job

POST

/transactions

Create a transaction

POST

/transactions/process/card

Send a card transaction to a terminal for processing

POST

/transactions/refund/card

Refund a card transaction

POST

/transactions/void

Void a transaction

POST

/merchants/{merchant_id}/contracts/card

Create a stored card contract for a customer

POST

/hpps

Generate a hosted payment page

GET

/terminals/status

Get a terminal's status by serial number or client ID

POST

/print_receipts

Create a print receipt job

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Transaction Broker API by hand means managing two HTTP auth pairs (ISVAuth and TerminalAuth), base64-encoding them, and choosing between the production, staging, and sandbox hosts yourself. Through Jentic you install once, import the Transaction Broker API from the API Directory, store both credential pairs once, and your agent calls it.

Permission scoping

Transaction Broker puts the merchant id in the URL path (/merchants/{merchant_id}/contracts/card), so a rule can pin contract operations to one merchant. You choose the operations the agent may call, so destructive ones like refund, void, or card processing are not included unless you add them.

Credential isolation

Your ISVAuth and TerminalAuth credential pairs 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.

Intent-based discovery

Agents search Jentic by intent such as 'process a card transaction' or 'refund a card payment', and Jentic returns the matching Transaction Broker operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Transaction Broker API through Jentic.

What authentication does the Transaction Broker API use?

The API uses two HTTP bearer schemes. ISVAuth carries 'Basic Base64(api_id:api_token)' for organisation-scoped calls and TerminalAuth carries 'Basic Base64(serial_number:registration_token)' for terminal-scoped calls. Both are sent in the Authorization header. Through Jentic, both credential pairs live in the encrypted vault and are injected at execution so the agent never holds them.

Can I process refunds for ACH and cash, not just card?

Yes. POST /transactions/refund/card refunds a card transaction, POST /transactions/refund/ach refunds an ACH transaction, and POST /transactions/refund/cash records a cash refund. Use the original transaction ID in the body and the broker dispatches the refund through the same flow.

What are the rate limits for the Transaction Broker API?

Rate limits are not declared in the OpenAPI spec. Bank of America enforces limits per organisation and terminal; consult https://developer.merchant-services.bankofamerica.com/ and your merchant agreement, and use the sandbox at tb-sandbox.paymentfusion.com for load testing.

How do I run a card payment on a specific terminal through Jentic?

Search Jentic for 'process a transaction broker card payment', load the schema for POST /transactions/process/card, then execute with the transaction ID from POST /transactions and the target terminal serial. Jentic injects ISVAuth and TerminalAuth at execution.

Does the Transaction Broker API support stored payment instruments?

Yes. Use POST /merchants/{merchant_id}/contracts/card to store a tokenised card and POST /merchants/{merchant_id}/contracts/ach to store an ACH instrument. Contracts are retrievable via GET /merchants/{merchant_id}/customers/{customer_id}/contracts and removable via the matching DELETE.

Can I check whether a terminal is online before sending a transaction?

Yes. GET /terminals/status accepts either a serial_number or a client_id and returns the current connectivity status, so the dispatcher can avoid sending a transaction to an offline device.

Can I limit what my agent is allowed to do with the Transaction Broker API?

Yes. Because Jentic One is self-hosted, your own rules decide which Transaction Broker operations the agent may call, so you can grant read-only actions like GET /terminals/status while withholding destructive ones such as POST /transactions/process/card, POST /transactions/refund/card, or POST /transactions/void. Since the merchant id sits in the URL path, for example /merchants/{merchant_id}/contracts/card, you can pin contract operations to a single merchant. Your ISVAuth and TerminalAuth credentials are stored by your own instance and injected only for the operations you have allowed, so the agent never sees them or reaches endpoints you did not approve.

Bankofamerica Transaction Broker API

Name: Transaction Broker API
Brand: Transaction Broker API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsPos Terminalbearer32 EndpointsREST

For Agents

Process card, ACH, and cash transactions, manage stored customer contracts, dispatch jobs to point-of-sale terminals, and reconcile receipts through Bank of America's Transaction Broker.

Use for: Process a card transaction on a Bank of America terminal, Refund a previous card transaction, Capture a previously authorised transaction, Create a stored ACH contract for a customer

Not supported: Does not handle banking, treasury, lending, or consumer banking products - use for merchant-side transaction dispatch, refunds, contracts, terminals, and receipts only.

Bank of America's Transaction Broker is the central system that manages ongoing payment transactions, dispatches them to point-of-sale terminals, returns results, and maintains the mapping between organisations, terminals, and customers. The 32 endpoints cover card, ACH, and cash transaction processing, refunds, voids, captures and reversals, plus contracts (tokenised customer payment instruments), hosted payment pages, scan codes, terminal status, and printable receipts. Three environments are available: production, staging, and sandbox at tb-sandbox.paymentfusion.com.

Jentic One on Github View OpenAPI Document

Connect the Transaction Broker API to your agent

Capabilities

Start building with Transaction Broker API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bankofamerica Transaction Broker API