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

# Increase API

Increase is a programmatic banking platform that exposes the underlying U.S. financial network through a REST API, including the Federal Reserve, Visa, ACH, real-time payments, wires, and check rails. The API spans 199 endpoints covering accounts, account numbers, account transfers, ACH transfers, wire transfers, real-time payment transfers, check transfers, inbound check deposits, cards, card disputes, physical card profiles, digital wallet tokens, and entity onboarding for KYC. Webhook event subscriptions deliver settlement, return, and decline notifications, and the simulations endpoints let teams reproduce wire returns or ACH NSF events in sandbox before production.

## For AI agents

Open and operate U.S. bank accounts, move money over ACH, wire, RTP, and check rails, and issue cards programmatically. Covers entity onboarding, transfers, card disputes, and webhook events.

## Scope

Does not handle merchant card acceptance, subscriptions, or international wire corridors - use for U.S. programmatic banking, ACH/wire/RTP origination, and card issuing only.

## Capabilities

- Open Increase accounts and provision additional account numbers for routing-level reconciliation
- Send ACH credits and debits, schedule prefunded same-day ACH, and manage ACH return handling
- Originate wire transfers and real-time payments, with explicit approve and cancel endpoints for compliance hold flows
- Issue virtual and physical cards, push them to Apple Pay and Google Pay via digital wallet tokens, and file card disputes
- Onboard businesses and individuals through entity creation with structured beneficial-owner and KYC data
- Subscribe to event webhooks for transactions, declined transactions, and transfer status changes
- Reproduce return, reversal, and decline scenarios through the /simulations endpoints before going live

## Use cases

### Automated Vendor ACH Payouts

Schedule and originate ACH credits to vendors directly from a finance application without an SFTP NACHA file workflow. Increase exposes a single POST /ach_transfers call that handles batching, addenda records, and same-day windows, and returns granular state transitions (pending_submission, submitted, returned) via webhooks. Replaces a typical 6-12 week bank integration with a working transfer in under a day.

Example prompt: Create an ACH transfer of $4,250.00 from account_id account_in71c4amph0vgo2qllky to a vendor's routing and account number, then poll until status is 'submitted'.

### Embedded Card Issuing

Issue virtual cards to contractors or employees and tokenise them for Apple Pay and Google Pay without contracting directly with Visa or a card processor. The /cards endpoint creates the card, /digital_card_profiles configures the wallet artwork, and /digital_wallet_tokens completes provisioning. Disputes are filed via /card_disputes with full chargeback reason codes.

Example prompt: Create a virtual card on account_id account_in71c4amph0vgo2qllky with spending_limit of $500/month and provision a digital wallet token for Apple Pay.

### Real-Time Payment Treasury Operations

Send and receive real-time payments over the RTP and FedNow networks for instant settlement, useful for marketplace payouts, insurance claim disbursements, and treasury sweeps. POST /real_time_payments_transfers originates the payment with creditor name and address, and inbound RTPs arrive as inbound_real_time_payments_transfer events on a webhook subscription. Settlement finality is sub-second.

Example prompt: Originate a real-time payment of $250.00 from a source account to a creditor at routing 021000021 and confirm the transfer state is 'complete'.

### Compliance and KYC Onboarding

Onboard business customers with structured KYC data and Increase's identity verification layer before letting funds move on their behalf. POST /entities creates the corporation or LLC entity with beneficial owners; /accounts then opens the deposit account once the entity is approved. Status transitions and CIP review outcomes arrive on the entity.updated webhook event.

Example prompt: Create a corporation entity for 'Acme Inc.' with two beneficial owners and tax_id 12-3456789, then open a deposit account once status becomes 'active'.

### AI Agent Treasury Workflow

An AI agent reconciles incoming transactions, categorises them, and triggers vendor payouts or transfers between accounts based on rules. Through Jentic, the agent searches for an Increase operation by intent (e.g., 'list pending transactions'), loads the input schema, and executes the call without managing raw bearer tokens. Suitable for finance copilots and CFO automation tooling.

Example prompt: List pending_transactions for account_id account_in71c4amph0vgo2qllky, group by category, and originate an ACH transfer for any utility bill exceeding $1,000.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/accounts` | Open a new Increase account |
| POST | `/ach_transfers` | Originate an ACH credit or debit |
| POST | `/wire_transfers` | Send a domestic wire transfer |
| POST | `/real_time_payments_transfers` | Send an instant RTP or FedNow payment |
| POST | `/cards` | Issue a virtual or physical card |
| POST | `/entities` | Create a business or individual entity for KYC |
| POST | `/event_subscriptions` | Subscribe to webhook events |
| GET | `/transactions` | List posted transactions on an account |

## Key resources

- **Accounts** — Open, list, retrieve, update, and close Increase deposit accounts
- **Account Transfers** — Move funds between two Increase accounts, with approve and cancel actions for compliance review
- **ACH Transfers** — Originate and manage ACH credits and debits, including same-day windows
- **Wire Transfers** — Send domestic wires with approval workflows
- **Real-Time Payment Transfers** — Send and receive RTP and FedNow payments with sub-second settlement
- **Cards and Card Disputes** — Issue virtual and physical cards, manage spending limits, and file chargebacks
- **Entities** — Onboard corporations, LLCs, partnerships, and natural persons with KYC data
- **Events and Event Subscriptions** — Subscribe to webhook deliveries for transaction and transfer state changes

## Why Jentic

- **Setup:** Wiring Increase by hand means learning its bearer auth, choosing between the production api.increase.com host and the sandbox host, and mapping its money-movement operations yourself. Through Jentic you install once, import Increase from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Increase takes the transfer amount and destination in the request body rather than the URL path, so limit the agent to the operations it needs, such as reading transactions or creating an ACH transfer. You choose which operations are allowed, so wire and real-time payment origination are not included unless you add them.
- **Credential handling:** Your Increase 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.
- **Discovery method:** Agents search Jentic by intent such as 'send an ACH transfer' or 'issue a virtual card', and Jentic returns the matching Increase operation with its input schema so the agent calls the right endpoint without browsing the 199 documented paths.

## Related APIs

- **Stripe API** — Stripe Treasury and Issuing cover similar embedded banking and card issuing ground, with broader merchant payment processing on top.
- **Plaid API** — Plaid retrieves bank account and balance data from external accounts; Increase moves money on its own accounts.

## FAQ

### What authentication does the Increase API use?

The Increase API uses HTTP bearer tokens. You issue an API key from the Increase dashboard and pass it as 'Authorization: Bearer <key>' on every request. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and never reaches the agent's context - the agent calls operations through scoped Jentic credentials.

### Can I send same-day ACH and FedNow payments with the Increase API?

Yes. POST /ach_transfers accepts a same_day flag for same-day ACH windows, and POST /real_time_payments_transfers originates RTP and FedNow instant payments with sub-second settlement when the receiving bank participates.

### What are the rate limits for the Increase API?

Increase enforces per-API-key rate limits that vary by environment (sandbox vs production) and endpoint class. The spec does not encode them; consult https://increase.com/documentation/api for current limits and contact Increase support for production volume increases.

### How do I issue a virtual card through Jentic?

Search Jentic with the query 'issue a virtual card' to find the POST /cards operation. Load its input schema (account_id, description, optional spending_limit) and execute. To push the card to Apple Pay, follow up with POST /digital_wallet_tokens. Get started with Jentic One, the self-hosted execution layer.

### How does Increase handle KYC and beneficial-owner data?

POST /entities creates a corporation, LLC, partnership, joint, trust, or natural_person entity with structured beneficial owner objects, addresses, and tax IDs. Increase runs CIP review and emits an entity.updated event when status moves to 'active' or 'requires_attention'.

### Can I test ACH returns and wire reversals before going live?

Yes. Increase exposes /simulations endpoints (e.g., simulate an ACH return, simulate a check deposit, simulate an inbound wire) so reconciliation, dispute, and exception-handling code can be exercised end-to-end in sandbox without waiting on real network events.

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

Yes. Because you self-host Jentic One and set its rules, you decide exactly which Increase operations the agent may call, so you can allow it to read transactions and create an ACH transfer while withholding everything else. Since Increase takes the transfer amount and destination in the request body rather than the URL path, scoping is done at the operation level, and higher-risk operations like wire and real-time payment origination stay unavailable unless you explicitly add them. Your Increase bearer token stays with your own instance and is injected only for the operations you permit.