Leffel Consulting Payments is one API to accept payments online, in person, and via ACH. Your application integrates a single REST API; we handle the payment processor, onboarding, webhooks, and reconciliation behind it.
Preview
The API is in active development and not yet publicly live. The base URL and examples below are for integration planning. Contact us for early access.
The merchant-of-record model
Every business you onboard becomes its own connected account — the merchant of record. That means:
- Their funds settle to their bank account, on their payout schedule.
- Charges show their statement descriptor.
- We never hold their money. We apply a small per-transaction platform fee at settlement.
You (the integrator) hold one API key and talk to one API; the merchant owns their payment account.
Core concepts
lcPaymentId— a stable payment id (lcpay_…) we issue for every payment. Store this as your reference. You never handle raw processor ids.- API key — a secret (
lc_live_…) sent in theX-Api-Keyheader. Keep it server-side. - Connected account — the merchant’s account (
acct_…), created during onboarding. - Application fee — the platform fee applied per transaction (percentage, flat, or hybrid).
- Callbacks — signed events we POST to your app as payments progress.
Base URL
https://payments.leffelconsulting.com/v1All amounts are integer cents (for example, 4999 means $49.99).
Where to go next
- Quickstart — onboard a merchant and take a payment.
- Authentication — keys and idempotency.
- API reference — every endpoint, field, and error.