Payments, balances, payouts. Built into your product.
We’re building APIs for payment acceptance, merchant onboarding, balance management, and fiat and stablecoin payouts.
POST /api/v1/payment-intents
Idempotency-Key: order_1048_create_intent
{
"amount": 12500,
"currency": "usd",
"merchant_reference": "order_1048",
"capture_method": "automatic"
}Create the payment on your server. Attach checkout to the intent.
Read the integration contract →From a checkout session to a reconciled payout.
One integration model for collecting funds, allocating proceeds, and paying the right recipient.
Create a payment. Control how it completes.
The payment API is being built around intents and checkout sessions: create the amount and currency on your server, collect payment details through checkout, and follow authorization, capture, cancellation, and refund activity against the same payment record. Hosted, embedded, and custom integrations are part of the platform roadmap.
Explore the fitAmount · currency · merchant reference · capture method
Keep checkout, payment status, and post-payment operations connected to your order.
Read the integration contract →Payment proceeds
├─ Pending balance
├─ Reserved funds
└─ Available balance
├─ Platform fee allocation
└─ Seller entitlement
└─ Verified recipient
├─ Bank account
├─ Eligible card
└─ Stablecoin walletRetain the relationship between the sale, allocation, and payout.
Read the integration contract →Allocate the proceeds. Program the payout.
We’re building merchant-scoped balances with available, pending, and reserved funds; allocations that retain platform fees and seller entitlements; and payout instructions tied to verified recipients. The planned payout layer covers eligible bank, card, and stablecoin destinations, with currency and network requirements attached to the instruction.
Trace every request. Reconcile every movement.
The integration contract specifies scoped credentials, operation-level idempotency, signed webhook events, structured errors, and request IDs. We’re extending that foundation with delivery history, replay tooling, and reconciliation exports that connect payments, fees, refunds, settlements, and payouts to your own order references.
Planned tooling for tracing API activity, reviewing event delivery, and matching financial activity to your records.
Read the integration contract →Payments that fit your stack.
Connect Acru to the platforms behind your business.
From payment complete
to money in motion.
Follow into balances, settlement, payouts, and supported
money movement. All connected to the transaction that started it.
Frequently
asked questions


4.9 / 5
#2,150Build the product. Connect the money.
Developer platform in development. The v0.1 API contract is published; roadmap features and production access are confirmed with the implementation team.


