Payments
Most processors treat a transaction as a single decision: approve or decline. Pyncht treats it as four — which acquirer, which network, which retry window, which data to attach. The difference shows up on your statement.
Route each charge to the acquirer with the lowest landed cost for that card, country, and amount — not the one you signed with first.
Commercial cards carry the highest interchange you pay. Pyncht attaches line-item and tax data automatically so they qualify for commercial rates.
Tokenised recurring credit transactions price below PAN-based ones and authorise more often. Pyncht provisions and refreshes tokens for you.
A decline is not a verdict. Pyncht retries recoverable reason codes on schedules tuned per issuer, and stops retrying the ones that never recover.
Cross-border assessments and FX spread compound on international volume. Settle locally in the EU and UK and most of that cost disappears.
Charges, refunds, disputes, and payouts land in a single balance with a single fee ledger, whatever route the money took.
Clean, versioned, and idiomatic. The same call works whether Pyncht is analysing your existing processor or moving the money itself.
Read the API referenceconst charge = await pyncht.charges.create({
amount: 4900,
currency: 'usd',
customer: 'cus_QjR2mK',
// Pyncht picks the route; you never pick an acquirer.
optimize: { routing: true, network_token: true },
});
charge.fees.effective_rate; // 0.0206No. Analysis runs read-only against your existing processor. Moving volume is a separate decision you make after you have seen the numbers.
Orchestrators route for authorisation rate. Pyncht routes for landed cost — authorisation rate is one input, alongside interchange qualification, cross-border assessment, and FX spread.
It goes out on your existing path at your existing cost. Pyncht never adds a hop that does not pay for itself.
Connect a processor read-only and get a full cost breakdown. Nothing moves until you decide it should.