Specified, not yet built · technical preview

Integration preview.

For merchant CTOs, engineering leads, and developers integrating qardon.com checkout into their POS, website, or mobile app. The full production-grade SDK and REST API documentation is not published yet. This page is a forward-looking technical preview — useful for scoping the integration ahead of time.

Integration options

Five paths. Build sequence by AOV.

{ }

Custom JavaScript embed v1 priority

Drop-in JS snippet for any e-commerce platform. One line in your HTML, one configured button. It is not built yet, and we have no date for it.

🛒

Shopify plugin v1

Native Shopify App Store listing. Install, enable, live. Goes through Shopify Partners certification before public availability.

▦

WooCommerce plugin v1.1

Native WordPress / WooCommerce plugin. Published to the WordPress Plugin Directory. WooCommerce-certified.

⊞

REST API v1

Direct REST API with OAuth 2.0 + HMAC signing. For custom integrations, headless commerce, and merchants with proprietary platforms.

📱

iOS SDK (Swift) v1.2

Native iOS SDK published to CocoaPods + Swift Package Manager. For merchants with native iOS POS apps.

📱

Android SDK (Kotlin) v1.2

Native Android SDK published to Maven Central. For merchants with native Android POS apps.

Custom JavaScript embed

One line. One button. Live.

Add the qardon.com checkout JS to your page (typically in <head>):

<!-- Add to your checkout page -->
<script src="https://js.qardon.com/v1/checkout.js"></script>

<!-- Render the button at checkout -->
<button
  class="qardon-checkout-btn"
  data-qardon-merchant-id="YOUR_MERCHANT_ID"
  data-amount="5000.00"
  data-currency="USD"
  data-order-id="ORDER-12345"
  data-installments="12,24,36,48">
  Pay in installments — 0% interest via qardon.com
</button>

Specified, not yet built. The design: the customer clicks, our JS opens a hosted modal handling identity verification, a creditworthiness check, installment-plan selection, agreement signing and payment-method capture, and on approval we POST a webhook to your configured endpoint with the transaction ID and approved installment schedule. Settlement to your merchant account begins per your agreed schedule.

REST API

Endpoints overview.

OAuth 2.0 client credentials. HMAC-signed payloads. Idempotency keys on every mutating request. Sandbox + production environments. The full OpenAPI 3.1 spec is not published yet.

Method Endpoint Purpose Status
POST /api/v1/merchant/transactions Create a new transaction. Returns transaction ID + hosted checkout URL. v1
GET /api/v1/merchant/transactions/:id Retrieve transaction status, approval result, installment schedule, settlement record. v1
POST /api/v1/merchant/refunds Initiate a refund (partial or full). Cancels remaining installments, refunds prior payments, claws back paid settlement. v1
GET /api/v1/merchant/settlements Settlement reports with date-range filters. Returns per-transaction settlement details + reconciliation. v1
POST /api/v1/merchant/disputes Respond to a customer-initiated dispute. Submit evidence + response within 30-day window. v1
POST /api/v1/merchant/milestones Construction / multi-stage merchants: submit completion proof for a milestone, trigger next-tranche settlement. v1.1
GET /api/v1/merchant/dashboard/metrics Real-time metrics for embedding in merchant's own dashboard. Approval rate, volume, settlement totals. v1.1
Sample request

Create a transaction.

curl -X POST https://api.qardon.com/api/v1/merchant/transactions \
  -H "Authorization: Bearer ${QARDON_API_KEY}" \
  -H "X-Qardon-Signature: ${HMAC_SIGNATURE}" \
  -H "X-Qardon-Idempotency-Key: ${UUID}" \
  -H "Content-Type: application/json" \
  -d '{
    "merchant_id": "merch_abc123",
    "amount_cents": 500000,
    "currency": "USD",
    "order_id": "ORDER-12345",
    "customer": {
      "email": "[email protected]",
      "first_name": "Jane",
      "last_name": "Doe",
      "billing_address": { ... }
    },
    "installment_options": [12, 24, 36, 48],
    "category": "furniture",
    "metadata": { "sku": "couch-large", "store_id": "store-7" },
    "webhook_url": "https://yourstore.example/qardon-webhook"
  }'

Response includes a hosted checkout URL for redirect, or — for fully embedded flows — a transaction token to inject into your in-page Qardon Element. Approval result + final installment schedule arrives via the configured webhook.

Architecture

What happens between checkout and settlement.

  1. Customer clicks "Pay with qardon.com" at your checkout. Your code POSTs to our /transactions endpoint, receiving a hosted checkout URL or in-page transaction token.
  2. Customer completes the identity + creditworthiness flow in our hosted modal. As designed: identity verification, creditworthiness scoring on the shared Qardon engine, fraud-signal review. None of it is built. There is no hosted modal today, no scoring engine behind it and no latency to quote — the figure that used to sit here was invented, and the step is specified, not shipped.
  3. Approval result returned. Approve / conditional / decline. As designed, an ECOA-compliant adverse-action notice would be surfaced to a declined customer; the decisioning surface is specified and not built, and nothing sends one today. Approved customer sees installment schedule + 0%-interest disclosure + TILA-equivalent terms summary.
  4. Customer e-signs the agreement. Payment method captured (debit card / ACH / Apple Pay). First payment authorized.
  5. Webhook fires to your endpoint. Transaction ID, approved schedule, customer reference (no sensitive credit data ever shared with merchant).
  6. Settlement initiated. T+2 ACH/wire for standard merchants; T+1 for tier-2+ merchants. Single transaction or milestone tranches for multi-stage construction.
  7. The installments are collected on a licensed party's own rail, never through a Fotoh account. Auto-charge on schedule. Failed-installment retry. Humane-default flow if hardship hits. Specified, not yet built.
  8. Reconciliation reports delivered. Daily settlement file + monthly statement + on-demand API exports.
Industry-specific integrations

Built for specific verticals.

Some industries have their own systems-of-record. We build dedicated integrations for those — same engine, industry-specific data model and UX.

🚗

Auto-dealer integration Live

DealerSocket + Reynolds & Reynolds + CDK Global DMS sync. CSV bulk inventory upload. Direct REST API for independents. Trade-in valuation (KBB + Black Book). Inventory aging dashboard. Pre-qualified buyer badges.

Auto-dealer integration preview →

⌂

Home builder integration v1.1

Milestone-based settlement (slab / framing / MEP / CO). Construction-loan-equivalent UX. Permit and inspection hooks. Multi-stage milestone API documented at /api/v1/merchant/milestones.

Specified, not yet built.

▣

Retail integration v1

Native Shopify + WooCommerce plugins. Custom JS embed. iOS / Android SDKs for native POS apps. Covered above in the standard integration options.

See above

Developer waitlist

Get notified when the SDK lands.

You'll receive: full OpenAPI 3.1 spec, SDK release notes, sandbox credentials, integration guides per platform, technical support contact during your integration. First 100 developer waitlist members get priority sandbox access.

Routed to merchants@qardon.com. The sandbox is not built and we have no date; this records your interest, and nothing opens from it today.