Sheet 4 of 6 · Documentation
The platform behind the sheet.
A REST API, webhooks and four SDKs. Create a payment in the customer’s currency, settle in yours, and listen for the events in between. Most teams send their first test transaction within the hour.
SDKs
- JavaScript
- @denvik/js
- Python
- denvik
- PHP
- denvik/denvik-php
- Ruby
- denvik
import { Denvik } from "@denvik/js";
const client = new Denvik({ apiKey: "dk_test_7Hq4…" });
const payment = await client.payments.create({
amount: 4900, // minor units, settled in your currency
currency: "EUR",
customerCurrency: "JPY", // the shopper pays in their own currency
method: "card",
capture: "automatic",
metadata: { order: "A-10294" },
});
console.log(payment.status); // "authorised"Amounts are in minor units. The key shown is a truncated test key; live keys are issued per account.
What the documentation covers.
The six sections below are issued with your API keys when your account is opened. Until then, the summary tells you what to expect.
- 4.1
Getting started
Create API keys, choose test or live mode, send a first transaction and read the response.
- 4.2
API reference
Every endpoint of the REST API: payments, refunds, customers, payouts, disputes and reports.
- 4.3
SDKs
JavaScript, Python, PHP and Ruby clients with the same methods and the same error model.
- 4.4
Guides
Multi-currency checkout, local payment methods, subscriptions, tax configuration and reporting exports.
- 4.5
Webhooks
Events for authorisations, captures, refunds, disputes and payouts, with signature verification.
- 4.6
Best practices
Idempotency keys, retries, handling declines, fraud rules and keeping keys out of client code.
Stuck on a step?
Write to contact@denvik.io with the request you sent and the response you received. We answer within 24 hours.
Go to the contact sheet