Skip to content
Celdor

Developers

Integrate once,see every part.

JSON over HTTPS, signed webhooks and a complete test mode. Every payment object carries its own breakdown — tax, fees, refunds, payout — so your books match ours.

Quick start

  1. 1

    Create an account

    Test keys are issued straight away.

  2. 2

    Create a payment

    POST the amount and currency, redirect to checkout_url.

  3. 3

    Handle the webhook

    Fulfil when payment.succeeded arrives.

const res = await fetch("https://api.celdor.app/v1/payments", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.CELDOR_SECRET_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": order.id,
  },
  body: JSON.stringify({
    amount: 9400,            // smallest currency unit
    currency: "eur",
    customer: { email: "ada@example.com" },
    success_url: "https://shop.example/thanks",
  }),
});
const { id, checkout_url } = await res.json();

API reference

Send your secret key as a bearer token. Amounts are integers in the smallest currency unit. Lists are paginated with limit and cursor.

MethodRoutePurpose
POST/v1/paymentsCreate a payment, receive a checkout URL
GET/v1/payments/{id}Read a payment and its breakdown
POST/v1/linksCreate a payment link
POST/v1/refundsRefund a payment in full or in part
GET/v1/disputesList disputes with deadlines
GET/v1/payouts/{id}/linesRead the lines of a payout statement
GET/v1/customers/{id}Read a customer record

The full field-by-field reference is available in your dashboard once your account is open.

Libraries

Any HTTP client works; no package is required. Plugins for Shopify, WooCommerce, PrestaShop and Magento are set up from the dashboard. Need a server library in a given language? Let us know.

Guides

  • Hosted checkout

    Send buyers to a page we host, styled to your brand.

  • Embedded fields

    Secure card fields inside your page; card data goes to our partners.

  • Payment links

    One link per order or a reusable link, created in the dashboard or by API.

  • Recurring charges

    Schedule charges, retry failures, trigger CRM follow-ups.

  • Refunds and disputes

    Refund by API; upload evidence before the deadline.

  • Reconciliation

    Match transactions to payouts with statement lines.

Webhooks

Events arrive as POST requests signed in a Celdor-Signature header. Check the signature with your endpoint secret, reply 2xx quickly and process afterwards. Undelivered events are retried.

  • payment.succeeded
  • payment.failed
  • payment.review_required
  • refund.created
  • dispute.created
  • dispute.updated
  • payout.planned
  • payout.sent
import hmac, hashlib

def verify(payload: bytes, header: str, secret: str) -> bool:
    parts = dict(p.split("=", 1) for p in header.split(","))
    signed = f"{parts['t']}.".encode() + payload
    digest = hmac.new(secret.encode(), signed, hashlib.sha256).hexdigest()
    return hmac.compare_digest(digest, parts["v1"])

# Celdor-Signature: t=1763550000,v1=9b2f…

Test mode

Keys beginning cd_test_ never move money; live keys begin cd_live_. Test cards and scenarios — approved, declined, authentication required, review, dispute — are listed in the dashboard.

Good practice

  • Keep secret keys server-side only.
  • Fulfil from webhooks, not from the return page.
  • Send an Idempotency-Key with every POST.
  • Rotate keys from the dashboard if exposed.
  • Show currency and total before payment.
  • Keep proof of delivery for disputes.

Need a hand?

Send us the request ID and we’ll trace it with you.

contact@celdor.app