Custara

Privacy first AI finance ops for businesses and fintechs.

Invoice verification, approvals, and payments, with control you can embed.

[Custara @Custarafinance]

Custara is live on mainnet.

Bills and invoices come in by API, PDF, email, and now Odoo.

The agent checks each one against your policy, vendor allowlist and risk rules. Then it's paid in USDC on Arc and settled onchain.

Nothing moves without sign off.

https://t.co/zbZhdiEDl8

[Custara @Custarafinance]

𝗬𝗼𝘂 𝗰𝗮𝗻'𝘁 𝘀𝗰𝗮𝗹𝗲 𝗮 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗼𝗻 𝗮 𝗳𝗶𝗻𝗮𝗻𝗰𝗲 𝘁𝗲𝗮𝗺 𝘁𝗵𝗮𝘁 𝘀𝘁𝗶𝗹𝗹 𝗰𝗵𝗲𝗰𝗸𝘀 𝗲𝘃𝗲𝗿𝘆 𝗯𝗶𝗹𝗹 𝗯𝘆 𝗵𝗮𝗻𝗱.

At 50 vendors, that works. At 500, something slips: a duplicate invoice, a new bank account nobody checked, a payment that never makes it back into the ERP.

Custara is the layer that lets AP keep up as you grow.

Bills come in from Odoo, ERPNext, email, PDF, CSV, or your API. Each one is checked before money moves: new vendors, duplicates, changed payout details, PO mismatches. Your policies decide what can be paid automatically, what needs one approval, and what needs two, with MFA on large payments.

Settlement is USDC on Circle's Arc, only to allowlisted addresses, in seconds. Then the payment is written back to your ERP, so reconciliation doesn't become a second bottleneck.

The same controls apply at ten vendors and at a thousand. A changed payout is still held. Money still only goes where you've allowed. Every decision is still on a record you can prove.

Growth shouldn't force a choice between speed and control.

𝘗𝘢𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘯𝘺𝘸𝘩𝘦𝘳𝘦. 𝘕𝘦𝘷𝘦𝘳 𝘱𝘢𝘺 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘰𝘯𝘦.

https://t.co/pe9fqb0t5I

[Custara @Custarafinance]

𝗬𝗼𝘂 𝗰𝗮𝗻'𝘁 𝘀𝗰𝗮𝗹𝗲 𝗮 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗼𝗻 𝗮 𝗳𝗶𝗻𝗮��𝗰𝗲 𝘁𝗲𝗮𝗺 𝘁𝗵𝗮𝘁 𝘀𝘁𝗶𝗹𝗹 𝗰𝗵𝗲𝗰𝗸𝘀 𝗲𝘃𝗲𝗿𝘆 𝗯𝗶𝗹𝗹 𝗯𝘆 𝗵𝗮𝗻𝗱.

At 50 vendors, that works. At 500, something slips: a duplicate invoice, a new bank account nobody checked, a payment that never makes it back into the ERP.

Custara is the layer that lets AP keep up as you grow.

Bills come in from Odoo, ERPNext, email, PDF, CSV, or your API. Each one is checked before money moves: new vendors, duplicates, changed payout details, PO mismatches. Your policies decide what can be paid automatically, what needs one approval, and what needs two, with MFA on large payments.

Settlement is USDC on Circle's Arc, only to allowlisted addresses, in seconds. Then the payment is written back to your ERP, so reconciliation doesn't become a second bottleneck.

The same controls apply at ten vendors and at a thousand. A changed payout is still held. Money still only goes where you've allowed. Every decision is still on a record you can prove.

Growth shouldn't force a choice between speed and control.

𝘗𝘢𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘯𝘺𝘸𝘩𝘦𝘳𝘦. 𝘕𝘦𝘷𝘦𝘳 𝘱𝘢𝘺 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘰𝘯𝘦.

https://t.co/pe9fqb0t5I

[Arc @arc]

Arc 🤝 @BVNKFinance

BVNK is live on Arc.

Through Circle Onramp Kit, builders can give users a bank-transfer path to fund wallets and receive USDC on Arc without managing separate payment processor integrations.

A more complete first-mile funding experience for apps built on Arc.

[Custara @Custarafinance]

Agentic economy is here!

[USDC @USDC]

Agents are already paying with USDC.

Over the last 90 days, agents sent more than 52.5M transactions in USDC. That’s 99.99% of agentic transactions.

USDC is issued by regulated affiliates of Circle. See Circle’s list of regulatory authorizations at https://t.co/6EKu6yx6YO. USDC is a dollar referenced virtual asset, backed by reserve assets, that allows you to transact with a value designed to track the U.S. dollar.

[Custara @Custarafinance]

𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝗲𝘅𝗽𝗲𝗻𝘀𝗶𝘃𝗲 𝗲𝗺𝗮𝗶𝗹 𝘆𝗼𝘂𝗿 𝗔𝗣 𝘁𝗲𝗮𝗺 𝘄𝗶𝗹𝗹 𝗲𝘃𝗲𝗿 𝗴𝗲𝘁:

"Hi, we've changed banks. Please send future payments to the account below."

It looks routine, and it's one of the most common ways vendor payments get stolen.

On Custara, a new or changed bank or wallet destination never goes through quietly:

→ The bill is held automatically
→ Someone on your team has to verify and clear it
→ Payments only settle to allowlisted addresses
→ Every decision is written to a tamper-evident audit trail

Your vendors can change their details. Your money only moves once you've confirmed it.

𝘗𝘢𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘯𝘺𝘸𝘩𝘦𝘳𝘦. 𝘕𝘦𝘷𝘦𝘳 𝘱𝘢𝘺 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘰𝘯𝘦.

https://t.co/pe9fqb0t5I

[Custara @Custarafinance]

𝗬𝗼𝘂𝗿 𝗘𝗥𝗣 𝗸𝗲𝗲𝗽𝘀 𝘁𝗵𝗲 𝗯𝗼𝗼𝗸𝘀.
𝗖𝘂𝘀𝘁𝗮𝗿𝗮 𝗺𝗼𝘃𝗲𝘀 𝘁𝗵𝗲 𝗺𝗼𝗻𝗲𝘆, 𝘀𝗮𝗳𝗲𝗹𝘆.

Paying vendors and contractors across borders is still slow and expensive. But the real risk isn't the fee. 𝘐𝘵'𝘴 𝘱𝘢𝘺𝘪𝘯𝘨 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘪𝘯𝘷𝘰𝘪𝘤𝘦.

𝗕𝗶𝗹𝗹𝘀 𝗰𝗼𝗺𝗲 𝗶𝗻 𝗳𝗿𝗼𝗺 𝘄𝗵𝗲𝗿𝗲 𝘆𝗼𝘂 𝗮𝗹𝗿𝗲𝗮𝗱𝘆 𝘄𝗼𝗿𝗸
Odoo, ERPNext, PDF, CSV, API, email, SFTP and the command line. Everything lands in one inbox, read into structured fields with a confidence score.

𝗘𝘃𝗲𝗿𝘆 𝗯𝗶𝗹𝗹 𝗶𝘀 𝗰𝗵𝗲𝗰𝗸𝗲𝗱 𝗯𝗲𝗳𝗼𝗿𝗲 𝗺𝗼𝗻𝗲𝘆 𝗺𝗼𝘃𝗲𝘀
New vendors, duplicates, changed bank or wallet details, purchase order mismatches and low-confidence reads are held until your team clears them. These checks are fixed rules, 𝘯𝘰𝘵 𝘢 𝘮𝘰𝘥𝘦𝘭'𝘴 𝘫𝘶𝘥𝘨𝘦𝘮𝘦𝘯𝘵.

𝗬𝗼𝘂𝗿 𝗽𝗼𝗹𝗶𝗰𝗶𝗲𝘀 𝗱𝗲𝗰𝗶𝗱𝗲 𝘄𝗵𝗮𝘁 𝗴𝗲𝘁𝘀 𝗽𝗮𝗶𝗱
Auto-approve small, routine bills. Require one or two approvers above that, plus MFA on high-value payments. Every policy is versioned.

𝗢𝗱𝗼𝗼 𝗮𝗻𝗱 𝗘𝗥𝗣𝗡𝗲𝘅𝘁 𝘀𝘁𝗮𝘆 𝘆𝗼𝘂𝗿 𝗹𝗲𝗱𝗴𝗲𝗿
Install Custara from the Odoo Apps store, or connect ERPNext once with an API key. Your team keeps entering bills as usual, and suppliers, purchase orders and submitted invoices flow into Custara automatically. To pay in USDC, save the vendor's Arc address in Custara.

𝗦𝗲𝘁𝘁𝗹𝗲𝗺𝗲𝗻𝘁 𝗶𝗻 𝘀𝗲𝗰𝗼𝗻𝗱𝘀
Approved bills are paid in USDC on Arc, to allowlisted addresses only. Fund and withdraw in NGN, GHS, KES, TZS and ZAR through Paj.

𝗕𝗼𝗼𝗸𝘀 𝘁𝗵𝗮𝘁 𝗰𝗹𝗼𝘀𝗲 𝘁𝗵𝗲𝗺𝘀𝗲𝗹𝘃𝗲𝘀
When a transfer completes, Custara writes the payment back to Odoo or ERPNext and the invoice shows Paid. 𝘈 𝘧𝘢𝘪𝘭𝘦𝘥 𝘱𝘢𝘺𝘮𝘦𝘯𝘵 𝘯𝘦𝘷𝘦𝘳 𝘮𝘢𝘳��𝘴 𝘢𝘯𝘺𝘵𝘩𝘪𝘯𝘨 𝘱𝘢𝘪𝘥.

𝗔 𝗿𝗲𝗰𝗼𝗿𝗱 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗽𝗿𝗼𝘃𝗲
Every step is written to a hash-chained audit trail you can export and verify.

𝘗𝘢𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘯𝘺𝘸𝘩𝘦𝘳𝘦. 𝘕𝘦𝘷𝘦𝘳 𝘱𝘢𝘺 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘰𝘯𝘦.

[Nam @SeattleNam]

@Custarafinance @arc @thecanteenapp @BuildOnCircle a held bill costs a day. a paid wrong address costs the month.

[Custara @Custarafinance]

𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝗲𝘅𝗽𝗲𝗻𝘀𝗶𝘃𝗲 𝗲𝗺𝗮𝗶𝗹 𝘆𝗼𝘂𝗿 𝗔𝗣 𝘁𝗲𝗮𝗺 𝘄𝗶𝗹�� 𝗲𝘃𝗲𝗿 𝗴𝗲𝘁:

"Hi, we've changed banks. Please send future payments to the account below."

It looks routine, and it's one of the most common ways vendor payments get stolen.

On Custara, a new or changed bank or wallet destination never goes through quietly:

→ The bill is held automatically
→ Someone on your team has to verify and clear it
→ Payments only settle to allowlisted addresses
→ Every decision is written to a tamper-evident audit trail

Your vendors can change their details. Your money only moves once you've confirmed it.

𝘗𝘢𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘯𝘺𝘸𝘩𝘦𝘳𝘦. 𝘕𝘦𝘷𝘦𝘳 𝘱𝘢𝘺 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘰𝘯𝘦.

https://t.co/pe9fqb0t5I

[Custara @Custarafinance]

@SeattleNam @arc @thecanteenapp @BuildOnCircle Agreed. That's why Custara holds any bill whose bank or wallet details changed until your team verifies it. Payments only go to allowlisted addresses, never to a new destination nobody checked.

[Custara @Custarafinance]

𝗬𝗼𝘂𝗿 𝗘𝗥𝗣 𝗸𝗲𝗲𝗽𝘀 𝘁𝗵𝗲 𝗯𝗼𝗼𝗸𝘀.
𝗖𝘂𝘀𝘁𝗮𝗿𝗮 𝗺𝗼𝘃𝗲𝘀 𝘁𝗵𝗲 𝗺𝗼𝗻𝗲𝘆, 𝘀𝗮𝗳𝗲𝗹𝘆.

Paying vendors and contractors across borders is still slow and expensive. But the real risk isn't the fee. 𝘐𝘵'𝘴 𝘱𝘢𝘺𝘪𝘯𝘨 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘪𝘯𝘷𝘰𝘪𝘤𝘦.

𝗕𝗶𝗹𝗹𝘀 𝗰𝗼𝗺𝗲 𝗶𝗻 𝗳𝗿𝗼𝗺 𝘄𝗵𝗲𝗿𝗲 𝘆𝗼𝘂 𝗮𝗹𝗿𝗲𝗮𝗱𝘆 𝘄𝗼𝗿𝗸
Odoo, ERPNext, PDF, CSV, API, email, SFTP and the command line. Everything lands in one inbox, read into structured fields with a confidence score.

𝗘𝘃𝗲𝗿𝘆 𝗯𝗶𝗹𝗹 𝗶𝘀 𝗰𝗵𝗲𝗰𝗸𝗲𝗱 𝗯𝗲𝗳𝗼𝗿𝗲 𝗺𝗼𝗻𝗲𝘆 𝗺𝗼𝘃𝗲𝘀
New vendors, duplicates, changed bank or wallet details, purchase order mismatches and low-confidence reads are held until your team clears them. These checks are fixed rules, 𝘯𝘰𝘵 𝘢 𝘮𝘰𝘥𝘦𝘭'𝘴 𝘫𝘶𝘥𝘨𝘦𝘮𝘦𝘯𝘵.

𝗬𝗼𝘂𝗿 𝗽𝗼𝗹𝗶𝗰𝗶𝗲𝘀 𝗱𝗲𝗰𝗶𝗱𝗲 𝘄𝗵𝗮𝘁 𝗴𝗲𝘁𝘀 𝗽𝗮𝗶𝗱
Auto-approve small, routine bills. Require one or two approvers above that, plus MFA on high-value payments. Every policy is versioned.

𝗢𝗱𝗼𝗼 𝗮𝗻𝗱 𝗘𝗥𝗣𝗡𝗲𝘅𝘁 𝘀𝘁𝗮𝘆 𝘆𝗼𝘂𝗿 𝗹𝗲𝗱𝗴𝗲𝗿
Install Custara from the Odoo Apps store, or connect ERPNext once with an API key. Your team keeps entering bills as usual, and suppliers, purchase orders and submitted invoices flow into Custara automatically. To pay in USDC, save the vendor's Arc address in Custara.

𝗦𝗲𝘁𝘁𝗹𝗲𝗺𝗲𝗻𝘁 𝗶𝗻 𝘀𝗲𝗰𝗼𝗻𝗱𝘀
Approved bills are paid in USDC on Arc, to allowlisted addresses only. Fund and withdraw in NGN, GHS, KES, TZS and ZAR through Paj.

𝗕𝗼𝗼𝗸𝘀 𝘁𝗵𝗮𝘁 𝗰𝗹𝗼𝘀𝗲 𝘁𝗵𝗲𝗺𝘀𝗲𝗹𝘃𝗲𝘀
When a transfer completes, Custara writes the payment back to Odoo or ERPNext and the invoice shows Paid. 𝘈 𝘧𝘢𝘪𝘭𝘦𝘥 𝘱𝘢𝘺𝘮𝘦𝘯𝘵 𝘯𝘦𝘷𝘦𝘳 𝘮𝘢𝘳𝘬𝘴 𝘢𝘯𝘺𝘵𝘩𝘪𝘯𝘨 𝘱𝘢𝘪𝘥.

𝗔 𝗿𝗲𝗰𝗼𝗿𝗱 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗽𝗿𝗼𝘃𝗲
Every step is written to a hash-chained audit trail you can export and verify.

𝘗𝘢𝘺 𝘷𝘦𝘯𝘥𝘰𝘳𝘴 𝘢𝘯𝘺𝘸𝘩𝘦𝘳𝘦. 𝘕𝘦𝘷𝘦𝘳 𝘱𝘢𝘺 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘰𝘯𝘦.

[phos @eddy_phos]

Odoo and Erpnext integration live on Custara.

We help businesses pay their invoices secure and fast.

Try it today

[phos @eddy_phos]

@Custarafinance @arc @thecanteenapp @BuildOnCircle Frappe businesses are welcome on arc

[Custara @Custarafinance]

ERPNext connector live on Custara

How it works:

Users keep entering bills in ERPNext as they already do.

They connect once with an ERPNext API key. Custara then indexes submitted suppliers, purchase orders, and purchase invoices on a short pull (about 15 seconds).

[Custara @Custarafinance]

and a clean write-back so paid status is not a manual journal. Nothing is marked paid in ERPNext unless the transfer actually completes.

[Custara @Custarafinance]

ERPNext connector live on Custara

How it works:

Users keep entering bills in ERPNext as they already do.

They connect once with an ERPNext API key. Custara then indexes submitted suppliers, purchase orders, and purchase invoices on a short pull (about 15 seconds).

[Custara @Custarafinance]

ERPNext connector is now live on Custara.

ERPNext stays the ledger. Custara handles approvals, risk, and USDC settlement on Arc.

Connect your site and submitted purchase invoices flow in. Mark a bill for crypto in Remarks, pay in USDC on Arc

Here’s how it works:

[Custara @Custarafinance]

Why the integration helps:

Businesses keeps ERPNext as the system of record, so audit and accounting stay familiar. Custara adds the payment layer: risk and policy checks before money moves, USDC on Arc for contractors and vendors,

[phos @eddy_phos]

ERPNext connector is live on Custara.

Custara adds the payment layer: risk and policy checks before money moves, USDC on Arc for contractors and vendors, and a write-back so paid status is not a manual journal.

Nothing is marked paid in ERPNext unless the transfer completes.

[Custara @Custarafinance]

ERPNext connector is now live on Custara.

ERPNext stays the ledger. Custara handles approvals, risk, and USDC settlement on Arc.

Connect your site and submitted purchase invoices flow in. Mark a bill for crypto in Remarks, pay in USDC on Arc

Here’s how it works:

[Custara @Custarafinance]

After the transfer completes, Custara creates and submits a Payment Entry in ERPNext allocated against that invoice, in your books’ currency, with a Custara reference.

The original invoice and its Remarks are left as they were. ERPNext shows Paid because of that allocation.

[Custara @Custarafinance]

ERPNext connector is now live on Custara.

ERPNext stays the ledger. Custara handles approvals, risk, and USDC settlement on Arc.

Connect your site and submitted purchase invoices flow in. Mark a bill for crypto in Remarks, pay in USDC on Arc

Here’s how it works:

[Custara @Custarafinance]

The bill lands in your Custara inbox. Controls check it, then you pay USDC on Arc to the allowlisted address.

A failed payment does not mark ERPNext paid.