Reap Business Account Product Update - October 2026

October’s updates let you manage cards and spend controls by asking Claude Code or Codex, bring funding instructions and deposit tracking to the API, and give View Only members their own Cards page.

This period’s highlight: the Business Account MCP server. Connect Claude Code, Codex, or another MCP client to your account with your own API key, then ask in plain language, such as “What’s our available credit?” It’s in beta for every business with Business Account API access.

What’s New at a Glance

New

1. Manage Your Business Account by Asking Claude Code or Codex

The Business Account MCP server lets Claude Code or Codex use your account with your own API key, the same way an app uses the API. Instead of building an integration, you ask in plain language, for example:

• “Show me this month’s card spend by team member.”
• “Freeze the card ending 4821.”
• “Create 5 virtual cards for the marketing team with a $500 monthly limit.”

It can’t move money or show full card numbers, and creating or terminating cards always starts with a preview.

Who this helps: Finance and admin teams with Business Account API access who want answers and card changes without writing code.

How to use it:

1. An admin creates an API key in the dashboard under API › Create key. Start with read scopes (the key’s scopes set the hard limit on what the assistant can do) and add your computer’s IP to the allowlist.
2. Add the server to Claude Code or Codex with the command in the setup guide, and set it to ask before it makes changes.
3. Ask a question, such as “Show my card account balances.”

Setup takes about 5 minutes. The MCP server is in beta with no sandbox, so every action runs on your live account. It doesn’t work in the Claude or ChatGPT apps (yet!).

Official docs to use the MCP server →

2. Business Account API Now Returns Funding Instructions and Deposit History

The Business Account API can now give you the same funding details and deposit history as the Treasury page in your dashboard, with four new endpoints:

• GET /treasury/funding-options lists what you can fund and how: by network for stablecoins, by rail for bank transfers.
• GET /treasury/funding-instructions returns a wallet address or bank details, as on the Add funds screen, along with the minimum deposit (USDC 2 or USDT 2) and the expected time to credit.
• GET /treasury/transactions lists deposits, withdrawals, payments, repayments, and adjustments, newest first. Stablecoin rows carry the transaction hash and bank rows carry the Reference ID, so you can match each deposit to what you sent.

Who this helps: Teams that fund their account from their own exchange, wallet, or bank and want to check deposits from their own systems.

How to use it:

1. An admin opens API in your dashboard.
2. Create a new key or edit an existing one.
3. Add treasury_funding:read for funding instructions, treasury_funding:write to confirm bank transfers, and treasury_transactions:read for deposit history.

Bank transfers fund Reap Cards only, in HKD over FPS or USD over CHATS. Keys created before this release don’t get the new scopes automatically, so they need to be edited. There are no webhooks, so check a deposit’s status by polling. The API is in beta and available on request.

Learn more: Business Account API docs →

Enhancements

1. View Only Members Now Have Their Own Cards Page

View Only members now get a Cards page showing only the cards issued to them. On other members’ transactions, View Card and the receipt upload and delete buttons are hidden or greyed out.

2. Card Details Now Show the Billing Address

Revealing a card’s details on the dashboard or in the Reap Mobile App now shows its billing address, so it’s there when a merchant asks for it at checkout.

3. Replace Card Now Shows When a Replacement Is Already on Its Way

If a card already has a replacement ordered, the Replace card button is greyed out and a tooltip explains why, so you don’t fill in the form only to hit an error. The cardholder sees the Activate card banner, and the button returns once the new card is activated.

4. El Salvador Recipient Setup Now Takes an IBAN or Account Number

One field now accepts either an IBAN or a local account number when you add a recipient in El Salvador. Banks there pay on the account number, so an IBAN is no longer required.

Who this helps: Teams paying vendors or contractors in El Salvador through Reap Pay.

5. Deposit Instructions Now Show How Long Each Network Takes

Stablecoin deposit instructions in your dashboard now state how long a deposit takes to reach your balance on each network.

Fixes

1. Card Creation API Now Accepts Any Combination of Spend Limits

Creating a card through the API with only some limits set, such as a monthly limit alone, now works. Invalid limits are still rejected.

2. Payments CSV Now Includes the Sent Date

The Payments page CSV export now fills in the Sent Date column for completed payments.

3. Recipient Setup Now Accepts GB IBANs for the Isle of Man, Jersey, and Guernsey

Banks in all three places use GB IBANs, and the recipient form now accepts them.

4. Receipts Now Show on Transactions from Deleted Cards

Receipts uploaded to a card that was later deleted display on its transactions again. They were never removed from your records.

5. Cards Table Now Fits Long Nicknames

The cards table stays within your screen, even when a card has a long nickname.

Connect Claude Code or Codex in About 5 Minutes

Everything in this update is live in Reap Business Account now. If your business has API access, create an API key with read scopes, follow the setup guide, and ask your first question.

Learn how to set up on your preferred agents here:

• Claude Code
• Codex

Want to start managing and automating business expense easily? Sign up for a Business Account today!

‍

Coming Soon: Receive Payments

And there is more! We’re getting ready to launch Receive Payments, which lets your customers pay you straight to your Reap account, in USD or HKD, depending on the currency of your account. We’re opening it first to a small group of existing Business Account clients, who’ll get early access and help shape it before the full launch. Spots are limited, so join the waitlist now, and expect to hear from us at the end of November or the beginning of December 2026.

• Learn more: How Receive Payments works →‍
• Interested? Join the waitlist →