Integrations

Runs on the stack you already have.

Keep your processor, your checkout, and your team. ChargeSecured layers evidence capture and dispute response on top, through terminal software, a checkout SDK, or one API call per sale.

Ask about your stackRead the API reference
Where it sits

A layer on top. Not a replacement underneath.

Your registerYour online checkoutYour POS and back officeYour processorYoursChargeSecured layerTerminal softwareCheckout SDKAPI and webhooksMoneyauthorization and settlementnever through ChargeSecuredevidence record → dispute responseCard networks and issuersthe record, only when a dispute is filedFunds settle from your processor to you. ChargeSecured receives only its disclosed fee.

Four ways in.

Most merchants use two: one for the register, one for the web. All four feed the same record and the same portal.

In person

Terminal software

Disclosure and acknowledgement on the terminal screen. Signature, ID, and photo capture when the transaction score calls for it, on the register you already run.

  • Configured at implementation
  • Hardware reviewed at assessment
Online

Checkout SDK

Adds disclosure, acknowledgement, and step-up to your existing payment step. Records device, IP, and billing match on every order; 3-D Secure or a one-time passcode above your threshold.

  • Drops into the payment step
  • No change to your cart or catalog
Any system

API and webhooks

Post each completed sale to one endpoint and the record, accounting, and dispute defense populate from it. Forward processor dispute notices and the package assembles itself.

  • REST, JSON, bearer keys with scopes
  • Webhooks on dispute events, HMAC-signed
API reference →
Your processor

Pass-through

Keep your acquiring relationship. Payments settle from your processor to you; ChargeSecured receives only its disclosed fee. Card-network and processor fees pass through at cost.

  • No markup, no interchange skimming
  • One statement, reconciled in the portal

What each path sends, and what comes back.

PathYou sendWe captureYou get back
Terminal softwareThe sale as it closes on the registerDisclosure shown, acknowledgement, signature, ID match and photo at step-upThe record, the response when a dispute lands, the portal
Checkout SDKThe order at the payment stepDisclosure, acknowledgement, device, IP, billing match; 3-D Secure or passcode at step-upThe record, the response, the portal
APIOne POST /api/v1/sales per completed sale, with items or totals and your external_idPurchase, timestamps, source system; disputes you forward to /api/v1/disputes201 with the stored sale, webhooks on dispute events, GET to reconcile
Processor pass-throughNothing newAuthorization and settlement stay with your processorProtection and processing on one statement, in the fee ledger

Backfilling history: post past sales with occurred_at set to the original date. Writes are idempotent on external_id, so a replay is safe to run twice.

Live in weeks, not quarters.

Nothing to rip out. The same four steps for every merchant, whatever the path.

Assessment
1 to 2 days

Current terminals, checkout, dispute volume, and merchant categories. Your band is set here.

Configuration
1 week

Risk rules, verification thresholds, and evidence capture for your business.

Implementation
2 to 4 weeks

Terminal software installed, checkout SDK integrated, protected transactions switched on.

Full deployment
Ongoing

Scale to full volume. Monitoring, tuning, and dispute defense included.

Not sure where you fit?

Tell us what you run at the register and online. If a path is missing for your setup we will say so at assessment, before anything is signed.

Ask about your stack

Bring your stack. We'll show you where the record comes from.

Schedule a demoAPI reference

Charge Secured LLC is not a bank, payment processor, insurer, or law firm. Chargeback outcomes are determined by card issuers and networks. No win rate or recovery is guaranteed.