Pyncht reads twelve months of settlement data over a read-only connection, rebuilds what your payments actually cost, and turns on the fixes worth taking.
Sample analysis: 17.3% of processing spend removed 7 fixes found, ranked by annual value
Millions of companies of all sizes use Pyncht
The savings engine
No migration, no code, no switching before you have seen the number. The connection is read-only, the arithmetic is shown for every line, and nothing changes at your processor until you decide it should.
Point Pyncht at the processor you already use. It pulls twelve months of statements, settlement files and decline logs over a read-only connection. Nothing reroutes, nothing settles anywhere new, and your checkout does not change.
Pyncht rebuilds your true cost line by line — interchange, scheme fees, processor markup, per-charge fixed fees, cross-border assessments, FX spread and chargebacks — split by card type, then compares each line against what that same volume should cost. The blended rate on your statement is almost never the rate you pay.
Then it enables the fixes: network tokens on recurring cards, Level 2/3 data on commercial cards, local acquiring for EU and UK volume, issuer-aware retry schedules, card account updater, pre-chargeback deflection and a costed case for renegotiating your markup. Each one arrives with the arithmetic behind it, ranked by what it is worth.
Figures shown come from a sample analysis of a B2B SaaS merchant processing $269,269 a month — $3.23M annualised. Every per-year figure on this page is that month carried across twelve. It illustrates the method, not a guaranteed or typical result; your own statements will produce different numbers.
Modular solutions
Start with one product and add the rest without a second integration — charges, subscriptions, and payouts all settle into the same balance.
Products
Nine products, one integration. Start with Payments and switch on Billing, Radar or Tax from the same API — no new stack, no second contract.
Online payments in 195 countries. Cards, wallets, bank debits and buy now, pay later — one integration, one reconciliation, one payout.
Learn moreSubscriptions and invoicing
Learn morePayments for platforms
Learn moreIn-person payments
Learn moreFraud prevention
Learn moreCard creation
Learn moreSales tax and VAT automation
Learn moreOnline identity verification
Learn moreStartup incorporation
Learn moreNeed something custom? Talk to sales
Developer-first
Clean, modern REST APIs with predictable resource URLs and machine-readable errors. Idempotency keys make every retry safe, so a dropped connection or a client timeout never charges a customer twice.
const pyncht = require('pyncht')('sk_test_pyn_9v3K…');
app.post('/pay', async (req, res) => {
// Amounts are in the smallest currency unit
const intent = await pyncht.paymentIntents.create({
amount: 2000,
currency: 'usd',
automatic_payment_methods: { enabled: true },
}, {
idempotencyKey: 'order_4f8b21',
});
res.json({ clientSecret: intent.client_secret });
});
import pyncht
pyncht.api_key = "sk_test_pyn_9v3K…"
# Amounts are in the smallest currency unit
intent = pyncht.PaymentIntent.create(
amount=2000,
currency="usd",
automatic_payment_methods={"enabled": True},
idempotency_key="order_4f8b21",
)
print(intent.client_secret)
require 'pyncht'
Pyncht.api_key = 'sk_test_pyn_9v3K…'
# Amounts are in the smallest currency unit
intent = Pyncht::PaymentIntent.create({
amount: 2000,
currency: 'usd',
automatic_payment_methods: { enabled: true },
}, {
idempotency_key: 'order_4f8b21',
})
puts intent.client_secret
$pyncht = new \Pyncht\PynchtClient('sk_test_pyn_9v3K…');
// Amounts are in the smallest currency unit
$intent = $pyncht->paymentIntents->create([
'amount' => 2000,
'currency' => 'usd',
'automatic_payment_methods' => ['enabled' => true],
], [
'idempotency_key' => 'order_4f8b21',
]);
echo $intent->client_secret;
pyncht.Key = "sk_test_pyn_9v3K…"
// Amounts are in the smallest currency unit
apm := &pyncht.PaymentIntentAutomaticPaymentMethodsParams{
Enabled: pyncht.Bool(true),
}
params := &pyncht.PaymentIntentParams{
Amount: pyncht.Int64(2000),
Currency: pyncht.String("usd"),
AutomaticPaymentMethods: apm,
}
params.SetIdempotencyKey("order_4f8b21")
pi, err := paymentintent.New(params)
Pyncht.apiKey = "sk_test_pyn_9v3K…";
// Amounts are in the smallest currency unit
var apm = AutomaticPaymentMethods.builder()
.setEnabled(true)
.build();
var params = PaymentIntentCreateParams.builder()
.setAmount(2000L)
.setCurrency("usd")
.setAutomaticPaymentMethods(apm)
.build();
var opts = RequestOptions.builder()
.setIdempotencyKey("order_4f8b21").build();
PaymentIntent intent = PaymentIntent.create(params, opts);
PynchtConfiguration.ApiKey = "sk_test_pyn_9v3K…";
// Amounts are in the smallest currency unit
var options = new PaymentIntentCreateOptions
{
Amount = 2000,
Currency = "usd",
AutomaticPaymentMethods = new() { Enabled = true },
};
var opts = new RequestOptions();
opts.IdempotencyKey = "order_4f8b21";
var service = new PaymentIntentService();
var intent = service.Create(options, opts);
99.999%
API uptime
250M+
API requests per day
<100ms
Median API latency
7
Official client libraries
Global scale
Pyncht runs on redundant infrastructure across five regions and three continents, so a business in Dublin and a customer in Osaka hit the same API on the same latency budget.
Learn more about global infrastructure99.999%
Historical uptime across Pyncht services over the last 12 months
500M+
API requests per day, peaking at 10K+ per second
135+
Currencies and payment methods supported out of the box
$1T+
Total payment volume processed on Pyncht in 2023
Customers
Peak weeks are the only real test. We didn't need better average latency; we needed the tail to hold when an acquirer in one region goes soft for an hour, and the retries to route around it before anyone opened a ticket.
Every new market meant a tax registration, a local currency, and a proration rule somebody hand-wrote. We moved subscriptions in the spring and tax a quarter later, and we've stopped budgeting engineering time for either.
The showroom and the online configurator ran on separate stacks for years, and the two ledgers never quite agreed. Consolidating them was a reconciliation project more than a payments one, and it's live in 27 markets now.
Create a Pyncht account and take your first live payment in minutes, or talk to our team about a plan shaped around your platform.