Fragment

A ledger API with a schema-defined chart of accounts, plus card and ACH payments, priced per ledger entry.

Fragment lets a team define its chart of accounts as a schema and post ledger entries through a GraphQL API, where each entry type maps an event in the funds flow to balanced lines. Its documentation covers idempotency keys on entry calls, so a retried request does not post twice, balance history by period and reconciling payments against the ledger. Fragment now presents the product as a way to automate customers’ billing, payments and accounting.

Fragment publishes its prices. Teams can start for free with 1,000 ledger entries a month and sandbox payments; after that, each ledger entry costs $0.005. Card payments cost 2.9% + 40¢, plus 1.5% for international cards and 1% for currency conversion; next-day ACH costs $0.50 and same-day ACH $2.00. Fragment asks teams with custom pricing needs or a need for dedicated infrastructure to contact it.

Website
fragment.dev
Infrastructure layers
Ledger infrastructure, payments
Products (as published)
Ledger API (GraphQL, schema-defined chart of accounts)
Balance history and reconciliation
Card payments
Next-day and same-day ACH
Client types
Software companies automating their customers' billing, payments and accounting
Pricing model (only if published)
Free to start with 1,000 ledger entries/month and sandbox payments; $0.005 per ledger entry; cards 2.9% + 40¢; ACH $0.50 next-day, $2.00 same-day; custom pricing on request
API documentation
fragment.dev
Date checked
Profile type
Standard

Questions

What does Fragment cost?
It is free to start with 1,000 ledger entries a month and sandbox payments; each ledger entry then costs $0.005. Payments are charged separately, such as 2.9% + 40¢ per card payment.
How do you write to a Fragment ledger?
Through its GraphQL API, posting entries whose types are defined in the ledger’s schema.
Does Fragment handle payments as well as the ledger?
Yes. Its pricing lists card payments and next-day and same-day ACH.

See also

Sources

Source: each provider’s own documentation, product pages, official announcements and filings, and official registers for licences, as linked in each profile. Fields a provider does not publish stay empty. How we build profiles: methodology.

remwm

What are you looking for?

Search by headline, topic or keyword.