Krepling Pay is a REST API with hosted pieces where they matter. Create a session from your backend and send the shopper to a checkout on your own domain, or mount hosted card fields in the form you already have. Payments, wallets, subscriptions and the assistants come back as signed webhooks into whatever you run. No platform, no plugin, no card data on your servers.
One API key, three integration styles. Pick by how much of the checkout you want to own; the payment, the wallet and the webhooks are the same underneath.
Your backend posts the cart to /v1/checkout/sessions and redirects the shopper to the URL that comes back: pay.veldt.audio, your logo, six fields, wallets first, sign-in by code, Kora on hand, Autopilot testing it. When the payment clears, payment.captured arrives at your endpoint and you write the order.
Your form, your fields, your button. krepling.fields.mount('#card') renders the card number, expiry and code inside iframes Krepling hosts, hands you a token, and your backend charges it with POST /v1/payments. Card data never reaches your origin.
Create the session on your backend, then krepling.checkout.mount('#checkout', session) in the browser. Wallets, sign-in by code, saved cards and Kora render inside the element you give it, styled from Checkout Studio; your header, cart and footer stay around it.
Keys from the portal, one request from your backend, one endpoint for the webhook. Plain HTTP and JSON; the samples are curl, Node, PHP and .NET, and the OpenAPI spec generates a client for anything else.
sk_test_ key for the sandbox, sk_live_ when you're ready; a publishable pk_ key for the browser.payment.captured to your endpoint, signed. Verify, insert the order, return 200. Done.Five flows connect them, all over HTTPS with JSON. Your storefront, backend and database stay what they are; Krepling holds the card data, the sessions and the wallet, and tells you what happened.
Every one of them is an API you can build on. The four on the right take the card. Krepling Pay takes the card and brings the shopper, the plan, the assistant and the test with it, with the checkout on your own domain.
On Shopify or Magento the app reads the catalog; on your own stack you send it, as a push to the catalog API or a feed URL Krepling polls every hour. Beacon scores how the assistants answer about you and lists the fixes; AI Channel publishes the feed Gemini, Claude and Perplexity can buy from. An agent's order is paid on Krepling and arrives at your endpoint as order.created.
Krepling holds a copy of what you send and nothing else. Fixes you approve are written to the feed; your catalog changes only when your next push carries them.
order.created carries the lines, the shopper and the payment, with source: "agent:claude". Your endpoint writes it the way it writes a checkout order.
Krepling Pay takes the payment and reports back. Whatever you calculate before it, and whatever your systems do after it, carries on unchanged.
Line items, quantities and prices are yours; the session is created from them and charges the total you send.
Apply your codes and discounts before the session; the checkout shows the lines you pass.
Your engine, TaxJar or Avalara, or a rate table; pass the amount and the checkout displays it.
Shoppers keep your accounts and sessions. Krepling's sign-in by code recognises their wallet alongside.
Orders are written by your endpoint from the events, with your IDs; the Krepling IDs ride along for reconciliation.
Send your own from the event, or switch on Krepling's receipts; off by default.
Your events fire from your pages as before; Krepling Reports adds the payment side.
Keep your own checks before the session; Krepling's risk engine runs on the payment, with its decisions in the event.
If it can make an HTTPS request and receive one, it can run Krepling Pay. The OpenAPI spec generates a typed client for the rest.
You call the API; Krepling calls you back. Every authorization, capture, refund, dispute, renewal and agent order is posted to your endpoint, signed, retried until you answer, and replayable from the portal or the CLI.
Every event carries a Krepling-Signature header you verify with your secret. Every write you make can carry an Idempotency-Key, so a timeout and a retry never charge twice. Pick an event to see its payload; send the same request twice to see what happens.
krepling events replayThe sandbox is the same API with a sk_test_ key: nothing moves, every path can be exercised. Example cards approve, decline or ask for 3-D Secure; the CLI forwards events to localhost and triggers or replays any of them.
Moving processors usually means every returning customer typing their card again. Your current provider exports the vault to Krepling's PCI environment, a transfer Stripe and Adyen both support; each token is mapped to a card in the Krepling Wallet, and your customer IDs come along so your database doesn't change.
Per successful charge, whatever you build and wherever you host it. No monthly fee, no setup fee, no charge for the hosted checkout on your domain, the drop-in, the hosted fields or the CLI, no surcharge for agent orders. Beacon and AI Channel are included. Enterprise volumes and multi-entity settlement are priced on the Scale page.