PAYMENTS API

Payments and billing data, one shape.

Charges, refunds, payouts, fees, subscriptions and disputes from Stripe, Square, PayPal, Adyen and billing systems, normalized and linked to the invoices they settle.

Get started See coverage

Sample data

JSON

GET /v1/finance/payouts/po_01JC7T2D9Q?expand=transactions

{
  "id": "po_01JC7T2D9Q",
  "object": "payout",
  "platform": "stripe",
  "remote_id": "po_1QAbCdEfGh",
  "status": "paid",
  "arrival_date": "2026-10-30",
  "currency": "USD",
  "amount": "4812.37",
  "transactions": [
    {
      "type": "charge",
      "amount": "5100.00",
      "invoice_id": "inv_01JC8Q2K7M"
    },
    {
      "type": "refund",
      "amount": "-120.00"
    },
    {
      "type": "fee",
      "amount": "-167.63",
      "fee_type": "processing"
    }
  ]
}

OBJECTS

Supported objects.

Read and write status comes from coverage data for each platform on this API. Write shows only where write-back is confirmed.

Customers
Read: BetaWrite on roadmap
On 8 of 11 platforms; readable on 2.
Refunds
Read: BetaWrite on roadmap
On 7 of 11 platforms; readable on 3.
Invoices
Read: BetaNo write-back
On 6 of 11 platforms; readable on 1.
Subscriptions
Read: BetaWrite on roadmap
On 6 of 11 platforms; readable on 1.
Payments
Read on roadmapNo write-back
On 6 of 11 platforms.
Disputes
Read: BetaNo write-back
On 5 of 11 platforms; readable on 3.
Payouts
Read: BetaNo write-back
On 5 of 11 platforms; readable on 3.
Transactions
Read: BetaNo write-back
On 3 of 11 platforms; readable on 1.
Balance Transactions
Read: BetaNo write-back
On 2 of 11 platforms; readable on 2.
Charges
Read: BetaNo write-back
On 2 of 11 platforms; readable on 2.
Credit Notes
Read on roadmapNo write-back
On 2 of 11 platforms.

Also in the data model: Customer, Fee, Invoice (billing), Plan, Coupon.

See object-level coverage by platform

NO LOWEST COMMON DENOMINATOR

Same depth as a direct integration.

Custom fields.
Map your customers' custom fields into the model, per connection, without code changes.
Raw records.
Every object carries the platform's original record in raw, for the edge cases.
Passthrough.
Call any native endpoint with Unify auth, rate limiting and logging.
Entities and currencies.
Subsidiaries, locations and currencies are fields, not afterthoughts.

From payout to ledger in one join.

Payout breakdowns.
Every payout lists the charges, refunds and fees inside it.
Fee visibility.
Processor fees are separate lines, ready for the expense account.
Invoice matching.
Payments link to the invoice they settle when the source provides a reference.

Processors and billing systems.

10 platforms live or in beta across 9 categories.

Explore integrations

Coverage, object by object.

Live, beta and roadmap status for every object below.

Coverage, object by object.: coverage by platform and capability
Platform	Read	Write	Webhooks	Bank feeds	Catalog/PIM
PayPal	Beta	On the roadmap	Beta	Beta	Not supported
Square	Beta	On the roadmap	Beta	Not supported	Not supported
Stripe	Beta	On the roadmap	Beta	Not supported	Not supported
Adyen	On the roadmap	On the roadmap	On the roadmap	Not supported	Not supported
Authorize.net	On the roadmap	On the roadmap	On the roadmap	On the roadmap	Not supported
Braintree	On the roadmap	On the roadmap	On the roadmap	On the roadmap	Not supported
Chargebee	On the roadmap	On the roadmap	On the roadmap	Not supported	Not supported
GoCardless	On the roadmap	On the roadmap	On the roadmap	Not supported	Not supported

Live
Beta
On the roadmap
Via Technology Center
Not supported

Showing 8 of 11 platforms.

See full coverage

Related APIs and use cases.

Payments API questions.

Is this a payment processor?

No. The Payments API reads and manages data in your customers' existing processors and billing systems. Money never moves through Unify Int.

Can we reconcile payouts automatically?

You get payouts with their transactions and fees on the Unify Graph, and the Accounting API to post them. Matching rules stay in your product.

Do you handle multiple currencies?

Yes. Each transaction keeps its presentment and settlement currency and amounts.

Is there a sandbox?

Yes. Sandbox access is free for early-access teams and design partners: demo companies on QuickBooks Online, Xero and Shopify, and test credentials for other platforms where the vendor offers them. Request it on the Get started page.

Can I reach fields you don't model?

Yes: through raw, custom field mapping, or passthrough requests to native endpoints.

Payments and billing data, one shape.

Supported objects.

Customers

Refunds

Invoices

Subscriptions

Payments

Disputes

Payouts

Transactions

Balance Transactions

Charges

Credit Notes

Same depth as a direct integration.

Custom fields.

Raw records.

Passthrough.

Entities and currencies.

From payout to ledger in one join.

Payout breakdowns.

Fee visibility.

Invoice matching.

Processors and billing systems.

Coverage, object by object.

Related APIs and use cases.

Payments API questions.

Connect once. Build everything else on top.