Preview Leffel Consulting Payments is in active development and migrating to Finix — the API isn't publicly live yet, and some examples still reflect the outgoing build. Request early access →

API Reference

API reference

A versioned REST API returning JSON. All requests are authenticated with your API key over HTTPS.

Base URL

All endpoints are relative to the versioned base URL. The /v1 surface is stable — breaking changes ship under a new version prefix.

Authentication

Send your key in the X-Api-Key header (or Authorization: Bearer <key>). Keys look like lc_live_…. A missing or invalid key returns 401. Keep keys server-side — never expose them in a browser.

Idempotency

Send an Idempotency-Key header when creating a payment. Retrying with the same key and body returns the original response; reusing it with a different body returns 409.

Conventions

  • Amounts are integer cents (e.g. 4999 = $49.99).
  • Errors are application/problem+json (RFC 7807).
  • A traceId accompanies failures (also in X-Correlation-Id).

Base URL

https://payments.leffelconsulting.com/v1
Authenticated request 
curl https://payments.leffelconsulting.com/v1/payments/lcpay_9f2c... \
  -H "X-Api-Key: lc_live_XXXXXXXXXXXXXXXXXXXX"

Resources

Payments

Create and manage payments. A payment is a direct charge on the merchant’s connected account with the platform fee attached; you receive a stable lcPaymentId and a clientSecret to complete the charge in the browser.

Terminal

Accept in-person, card-present payments with Stripe Terminal readers. Create a connection token for the Terminal SDK, and manage the merchant’s locations and readers.

Onboarding

Onboard a merchant as a Standard connected account (merchant of record). Create the account, send the merchant through Stripe-hosted onboarding, and check whether they can accept charges and payouts.

Webhooks & callbacks

Leffel Consulting Payments receives processor webhooks, updates the ledger, and forwards signed events to your application. Verify the LC-Signature header, then react to payment lifecycle events.

Errors

The RFC 7807 error shape and the full status/title catalog.