Custom build

Your stack, your language. One request to a checkout.

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.

Any language · REST and JSONHosted checkout on your domainSigned webhooks, replayableSandbox with test cards
veldt.audio/webhooks104,821events delivered · 200 OK
api.krepling.com/v1Your backend
veldt-api · zsh
pay.veldt.audioHosted session
Demo store on its own stack. One request from your backend creates the session; the checkout on pay.veldt.audio is built from the response; the payment comes back to your endpoint as a signed webhook.
Three ways in

A hosted session, your own form, or a drop-in.

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.

One call, one redirect. The checkout is Krepling's, on your domain.

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.

You keepYour cart, pricing, promotions, tax, customer accounts and database
Krepling runsThe checkout page, the card data, the processor
Price2.5% + 30¢ per successful charge · the API is free
The three steps

Keep your checkout page. Swap the card inputs.

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.

You keepThe whole checkout page and its layout
Krepling runsThe card fields, the token, the processor; wallets as buttons you place
NoteThe Krepling Wallet and sign-in by code are available as a field too
Where everything lives

Mount the whole checkout inside your page.

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.

You keepYour page, your URL, your surrounding layout
Krepling runsEverything inside the element: fields, wallets, sign-in, the processor
NoteAutopilot can test the drop-in like a hosted session
The three steps
Quickstart

Three steps to a first payment.

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.

  1. 1
    Get your keysPortal › Developers › API keys. A sk_test_ key for the sandbox, sk_live_ when you're ready; a publishable pk_ key for the browser.
  2. 2
    Create a session and redirectPost the cart from your backend. The response carries the URL of the checkout on your domain; send the shopper there, or mount it.
  3. 3
    Verify the webhook, write the orderKrepling posts payment.captured to your endpoint, signed. Verify, insert the order, return 200. Done.
Architecture

Your stack on the left. Krepling on the right.

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.

Your stack · any language, any hostKrepling Pay
Your backendNode, PHP, .NET, Rails, Go, anything that speaks HTTPS
POST /v1/checkout/sessions201 · the session and its URL
The APIapi.krepling.com/v1 · JSON · idempotent writes · OpenAPI spec
Your storefrontServer-rendered or a single-page app; the cart and pricing are yours
redirect · or mount in your pagewallets · sign-in by code · Kora
Hosted checkout on your domainpay.veldt.audio by CNAME · hosted fields · the drop-in · Checkout Studio
Your webhook endpointVerify the signature, write the order, return 200
payment.captured · refunded · disputedretried · replayable · signed
EventsEvery payment, renewal, dispute and agent order, as it happens
Your databaseOrders, customers, catalog · yours, as they are
POST /v1/catalog · or a feed URLBeacon score · AI Feed
Beacon · AI ChannelThe assistants read your catalog and buy from it; the order comes back as an event
Your teamFinance, support, growth
POST /v1/refunds · /capturesor from the portal
The portalReports, disputes with responses prepared, Autopilot's log, Checkout Studio, keys
Stays on your side
  • The cart, prices, promotions and tax you calculate; Krepling charges the total you send
  • Customer accounts and sessions on your storefront
  • Orders and their lifecycle in your database, written from events
  • Your emails, analytics and fulfilment; receipts from Krepling are optional
Lives with Krepling
  • Card numbers, tokens and the saved cards in the Krepling Wallet; nothing card-shaped touches your servers
  • Checkout sessions, their state and expiry
  • Authorizations, captures, refunds, disputes and the risk engine's decisions
  • Subscription plans and renewals, reported to you as events
Side by side

Krepling Pay next to Stripe, Adyen, Braintree and Checkout.com.

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.

Integration surfacesREST API, hosted sessions, hosted fields, drop-in, CLI, OpenAPI spec and Postman collection.API, Checkout, Elements, CLIAPI, Drop-in and Components, hosted checkoutAPI, Drop-in, Hosted FieldsAPI, Frames, Hosted Payments Page
Hosted checkout on your domainYes, by CNAME: pay.yourdomain.com, your logo and type from Checkout Studio.Stripe-hosted; a custom domain is an add-onAdyen-hosted pageDrop-in or Hosted Fields in your pageCheckout.com-hosted page
Returning shoppersKrepling Wallet: recognised at any Krepling store, on any platform. A code to email or phone, no account on your site.Link, at stores running StripeStored cards against your customer IDsVault, against your customer IDsStored instruments, against your customer IDs
SubscriptionsBuilt in: a plan on the session, renewals and retries as events, card updates from the network. Nothing extra to build.Stripe Billing, priced separatelyBuild it on their tokensRecurring billing includedBuild it on their tokens
Saved cards migrate inToken import from Stripe or Adyen; your customers re-enter nothing.Export on requestExport on requestExport on requestExport on request
Kora, the voice assistantIn the hosted checkout and the drop-in: answers out loud, adds products, checks shoppers out.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
AutopilotTests the hosted checkout and the drop-in: wallet order, field order, the sign-in prompt. Nothing changes until you approve it.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
Selling in AI assistantsAI Channel: Gemini, Claude, Perplexity; ChatGPT and Copilot as ACP opens. The order arrives as an event.Not part of the gatewayNot part of the gatewayNot part of the gatewayNot part of the gateway
US online card rate2.5% + 30¢2.9% + 30¢ · +1.5% internationalInterchange++ · $0.13 + 0.6% + interchange2.59% + 49¢Quoted: interchange++
Published US rates and product names as of November 2026, from each provider's pricing and documentation pages. Adyen and Checkout.com price interchange++, so they aren't in the calculator. Rates vary by product and change; check theirs before you decide.
Processing cost at your volumeUS card payments through each API, at your monthly volume and order size.
Monthly card volume$240,000
About 688 orders a month—
Krepling Pay—2.5% + 30¢ · the API, the hosted checkout and the sandbox are free
—2.9% + 30¢ · +1.5% on international cards
—2.59% + 49¢ · cards
Domestic US cards only; international, currency-conversion and dispute fees are extra on every provider. Krepling Pay's published rate is 2.5% + 30¢ per successful charge; enterprise volumes are priced on the Scale page.
Beacon · AI Channel

No platform to read from. So you push the catalog.

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.

Visibility scoreveldt.audio · 5 assistants · 40 questions
Up 9 this week
0of 100
Named first for “wireless over-ears with multipoint under $400”Skipped for “headphones with USB-C audio”: the spec isn't in the feed
From your database to the order$0 added by Krepling
Your catalog412 products · pushed nightly · or a feed URL
AI FeedFixes drafted, approved by you, undoable
The assistantsNamed, then bought from where checkout is supported
Your endpointorder.created · VD-104823 · source agent:claude
Fix drafted · Veldt V2“USB-C audio” added as an attribute in the feed; written back to your catalog only if your push includes it
Agent order · via Claude · Veldt BudsPaid on Krepling Pay · order.created to veldt.audio/webhooks · your fulfilment
200 OK
Read-only, your way round

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.

An order like any other

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.

The rest of your stack

Everything else stays yours.

Krepling Pay takes the payment and reports back. Whatever you calculate before it, and whatever your systems do after it, carries on unchanged.

Your cart and pricing

Line items, quantities and prices are yours; the session is created from them and charges the total you send.

Promotions

Apply your codes and discounts before the session; the checkout shows the lines you pass.

Tax

Your engine, TaxJar or Avalara, or a rate table; pass the amount and the checkout displays it.

Customer accounts

Shoppers keep your accounts and sessions. Krepling's sign-in by code recognises their wallet alongside.

Your order database

Orders are written by your endpoint from the events, with your IDs; the Krepling IDs ride along for reconciliation.

Emails and receipts

Send your own from the event, or switch on Krepling's receipts; off by default.

Analytics

Your events fire from your pages as before; Krepling Reports adds the payment side.

Your fraud rules

Keep your own checks before the session; Krepling's risk engine runs on the payment, with its decisions in the event.

Any language. Any framework. Any host.

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.

Requests and events

Every payment comes back as an event.

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.

Requests you makeveldt.audio · todayEvents we send
0.4 sfrom the payment to your endpoint
5retries over 24 hours if you don't answer 2xx
1signature header to verify, one secret
0card numbers on your servers
Webhooks and idempotency

Signed on the way out. Safe to retry on the way in.

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.

IdempotencyThe same key returns the same result; a new key makes a new session
POST /v1/checkout/sessions
Idempotency-Key: VD-104822Authorization: Bearer sk_test_veldt_4Kq9…{ "reference": "VD-104822", "currency": "usd", "line_items": [ … ], "customer": { "email": "maya@reyes.co" } }
If your endpoint doesn't answer 2xx, the event is retried
now+1 min+10 min+1 h+6 h+24 hthen replay from the portal or krepling events replay
Sandbox

Test keys, test cards, events on your laptop.

The 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.

Keys
sk_testsk_test_veldt_4Kq9mX2pLw7…
pk_testpk_test_veldt_8Hn3vQ1rTz5…
whsecwhsec_veldt_Yc0… · the webhook signing secret
Example test cards
krepling listen · forwarding to localhost:3000/webhooks/krepling
Token import

Bring your saved cards. Nobody re-enters anything.

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.

Import · veldt.audioStripe customers and payment methods → Krepling Wallet
Importing
0 of 12,480 saved cardsstarted 09:00 · about 20 minutes
StripeKrepling WalletStatus
0imported
0expired, skipped
0cards re-entered
Pricing
2.5%+ 30¢

The API is free. So is the sandbox, forever.

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.

IncludedThe API and the OpenAPI spec, hosted sessions on your domain, hosted fields, the drop-in, the CLI and the sandbox, Krepling Wallet, sign-in by code, Kora, Autopilot, Subscriptions, Checkout Studio, Beacon, AI Channel, Reports, dispute responses prepared for every case, token import.
Not includedYour hosting and your engineers' hours, and any platform fee an assistant charges, which is listed before you switch that channel on.
LeavingStop creating sessions. Your orders are already in your database; your customers' saved cards can be exported to your next processor on request.
FAQ

Questions, answered.

Still wondering? Read the docs or speak to an expert.

Which languages are supported?
All of them. The API is REST over HTTPS with JSON, so anything that makes a request works. The docs carry samples in curl, Node, PHP and .NET, and the OpenAPI spec generates typed clients for the rest.
Do card numbers ever touch my servers?
No. With a hosted session the shopper is on a Krepling page; with hosted fields and the drop-in the card inputs live in iframes Krepling hosts and your page only ever sees a token. Saved cards live in the Krepling Wallet.
Can the hosted checkout be on my domain?
Yes. Point a CNAME such as pay.yourdomain.com at Krepling and verify it in the portal; the certificate is issued for you. Checkout Studio sets your logo, type and colours.
How do webhooks work?
Register an endpoint and pick the events. Each delivery carries a Krepling-Signature header you verify with your signing secret; anything but a 2xx is retried over 24 hours, and any event can be replayed from the portal or the CLI. Payloads carry the event id, so your handler can be idempotent too.
Is there a sandbox?
Yes, free and permanent. Test keys hit the same API with nothing moving; example cards approve, decline or ask for 3-D Secure; a test wallet behaves like a returning shopper; the CLI forwards events to localhost and triggers any of them.
Can I migrate saved cards from Stripe or Adyen?
Yes. You request the export from your current provider; it goes straight into Krepling's PCI environment, never through you. Each token becomes a Krepling Wallet card mapped to your customer ID, so your customers see their cards at the first checkout and your database keeps its keys.
How do Beacon and AI Channel work without a platform?
You push the catalog to the catalog API, or publish a feed URL Krepling polls hourly. Beacon scores it, AI Channel publishes it, and an agent's order arrives at your endpoint as order.created, paid on Krepling.
Can I run subscriptions through the API?
Yes. Put a plan on the session's line item and Krepling runs the renewals, retries and card updates; each renewal reaches you as subscription.renewed with the payment, and a paused or cancelled plan as its own event.
What about native mobile apps?
The hosted session works in a web view today, with Apple Pay and Google Pay where the device supports them. For native SDKs, speak to an expert and we'll scope it with you.

You've seen what Krepling Pay can do. Now let's build it into your stack.