NewCost-based routing with an approval floor→

One integration. Every processor.

Finyst sends each payment to the processor most likely to approve it, retries soft declines on the next best route, and reconciles it all against one ledger. Saved cards stay portable, so you are never locked to one processor.

Automatic failoverNo per-transaction fee from FinystKeeps PCI DSS scope contained
finyst.techyst.net / acme / routingLive · test mode
Authorisation rate94.58%after retries · last 240
Recovered by retries$18,402.10today · USD equivalent
Processed volume$1,284,31018,240 payments
p95 latency366 mscheckout to decision
Checkoutweb · iOS · AndroidFinyst routerrules · v14StStripe33% of trafficAdAdyen19% of trafficCoCheckout.com24% of trafficBtBraintree15% of trafficPpPayPal8% of traffic

Illustrative test-mode traffic. Switch strategy, click a processor to take it offline, or press P to send a payment.

One integration for the processors and payment methods your customers already use

StripeAdyenCheckout.comBraintreePayPalWorldpayRazorpayCybersourceAuthorize.netAirwallexKlarnaMollieNuveiRapydShift4WorldlinedLocalTrustpay
CardsApple PayGoogle PayPayPalKlarnaUPISEPA Direct DebitACHiDEALBancontactBLIKPix

The problem

Every new processor is another integration to babysit.

Different SDKs, webhook formats, decline codes and settlement files. Each one works in isolation, and none of them helps the others when a payment fails.

  • One payments API. Create, capture, refund and dispute the same way on every processor.
  • One set of events. Normalised statuses and decline codes, signed webhooks, one format.
  • One ledger. Settlement from every processor matched against your orders in one place.

Integration backlogengineer-weeks

StripeSDK · webhooks · idempotency6 wk
AdyenAPI · HMAC notifications · 3DS28 wk
Checkout.comFlow · webhooks · disputes7 wk
BraintreeGraphQL · vault · PayPal7 wk
RazorpayOrders · UPI · settlements6 wk
34 wk and countingOne Finyst integration

Illustrative estimates for a typical in-house build.

The routing layer

Everything between checkout and the bank.

Seven building blocks that turn a pile of processor accounts into one payment system you can reason about.

One API, many processors

Create, capture, refund and void through one API. Finyst translates each call for the processor that takes it.

POST /payments
StripeAdyenCheckout.comBraintreePayPalRazorpay

Unified checkout

One SDK for web and mobile that shows the right methods for each customer.

CardApple PayPayPalKlarnaUPIiDEAL
•••• 424212/34Pay $65.40

3DS when it earns its place

Frictionless where issuers allow it, challenge where risk or regulation calls for it.

Frictionlessrisk 12 / 100

Refunds and disputes

Refund on any processor from one screen. Disputes arrive with deadlines and evidence slots.

dp_2291Product not received6 days left

dp_2287Fraudulent · 10.4Evidence sent

re_8812Refund · $24.00Settled

Card vault

Store a card once, then charge it on any connected processor with the same token.

tok_9f3a2c71e0b4visa · 4242tok_1b77d0e9a2c5visa · 4242tok_c40e8f13b6d2visa · 4242tok_77aa0c2e91f8visa · 4242

Unified analytics

Authorisation, decline reasons, latency and cost for every processor on the same axes, down to network and country.

93.4%St
95.1%Ad
92.2%Co
91%Bt
96.3%Pp
94.1%Rz

Network tokens

Where your processors support them, card-scheme tokens keep saved cards working after a reissue, and can lift approval on repeat payments.

Card •• 4242expires 12/26Issuer reissuesnew expiry 12/29Network tokenupdated automatically

Intelligent routing

Decide who takes each payment, and see what it costs.

Pick a strategy, move the sliders, flip the rules. The flow and the projected approval and fees update as you go.

Routing · checkout-live · draftUnsaved draft

Write explicit rules on network, amount, currency, country or method. First match wins.

else cards → Stripe · wallets → Braintree

US cards 34%EU cards 20%UK cards 9%Amex > $500 6%INR 12%PayPal wallet 9%Under $10 10%Stripe 73.0%Adyen 6.0%Checkout.com 0.0%Braintree 0.0%PayPal 9.0%Razorpay 12.0%
Projected approval93.34%+1.65 pts
Blended fee3.15%-0.29 pts
Extra approved / month$66,000on $4M attempted
Fees saved / month$8,429including fees on extra approvals

Compared with one card processor plus PayPal. Illustrative rates and fees for a fictional merchant.

View as config routing.json
{
  "algorithm": "rules",
  "rules": [
    {
      "if": "card_network = amex && amount > 50000",
      "then": "adyen"
    },
    {
      "if": "currency = INR",
      "then": "razorpay"
    },
    {
      "if": "payment_method_type = paypal",
      "then": "paypal"
    }
  ],
  "default": {
    "card": "stripe",
    "wallet": "braintree"
  }
}

Automatic failover

When a processor falls over, checkout doesn't.

Finyst watches error rates and latency on every connector. When one breaks its threshold, the circuit opens, traffic moves to the next best route and soft declines are retried there. Take one down yourself.

Connector health · checkout-liveAll connectors healthy
Authorisation rate95.0%
Lowest in window95.0%
Kept by failover$00 payments

With FinystPinned to one route

100%90%80%70%
StripeOperational
Traffic40%
p95
212 ms
Errors
0.2%
AdyenOperational
Traffic30%
p95
248 ms
Errors
0.2%
Checkout.comOperational
Traffic20%
p95
231 ms
Errors
0.2%
BraintreeOperational
Traffic10%
p95
266 ms
Errors
0.2%

Event logUTC

Health checks passing on 4 connectors

Routing rules v14 published by m.okafor

Runs its own drill until you take over. Illustrative traffic, thresholds and figures.

Seconds, not a war room

Health is scored per connector, so failover happens before anyone opens a dashboard.

Careful recovery

A restored processor comes back at a fraction of its share and earns the rest.

Everyone hears about it

Circuit changes post to your alerting and land in the audit log.

Life of a payment

Five steps, one record.

From the first connector to the last settlement line, every payment keeps its full history.

01

Connect

Add each processor's credentials once. Finyst checks them, pulls supported methods and turns each account into a connector you can route to.

Connectors · acme

Stripesk_live_••••7QaCards · WalletsConnected
AdyenAQE••••••x9kCards · iDEAL · SEPAConnected
Checkout.comsk_••••••c21Cards · Apple PayConnected
Razorpayrzp_live_••••NeUPI · RuPay · CardsConnected
02

Route

Rules, volume splits, success rate or cost decide the first attempt. Every version of every rule is kept, so you can see which one moved a payment.

Rule set · checkout-live · v14

payment

wallet = paypal→PayPal

amex and amount > $500→Adyen

currency in EUR, GBP→Checkout.com

else→Stripe 60 · Braintree 40

Published by m.okafor · diff against v13 · rollback in one click

03

Authorise

One call carries the payment through 3DS when needed, to the chosen processor, and back with a normalised status in a few hundred milliseconds.

pay_Q7f3a91c20 · $65.40

  1. Payment created
  2. 3DS · frictionless
  3. Routed to Adyen by rule 2
  4. Authorised
  5. payment_succeeded webhook sent
04

Retry

A soft decline or a timeout is retried on the next best route. Hard declines like stolen cards are never retried, so issuers keep trusting you.

Attempts · pay_Q7f3a91c20

Attempt 1 · Stripedo_not_honor · softDeclined
Attempt 2 · Adyenauthorised · 186 msRecovered

Hard declines (stolen, lost, insufficient funds) are never retried.

05

Reconcile

Settlement files from every processor land in one ledger, matched to your orders, with fees, refunds and chargebacks broken out.

Settlement · Sep 24

Stripe98.6%
Adyen99.4%
Checkout.com100%
Razorpay97.9%

3 lines need review · $41,212.08 net settled · illustrative

Vault and tokenisation

Collect a card once. Use it anywhere.

The card number goes into the Finyst vault and comes out as a token. Every processor can charge that token, and card-scheme network tokens keep it working when the plastic changes.

finyst.techyst.net / acme / vaultDemo, nothing is collected
VISA

 

Card holderDEMO CUSTOMERExpires12/34
Test data · display only

Waiting for a card.

Finyst vaultPCI DSS scope · contained

token
tok_············
network
…
last4
…
expiry
…
network_token
…
cryptogram
…
pan
…

Reuse the tokenstored once · used 0×

StripeReady
AdyenReady
Checkout.comReady

Same customer, three processors, no re-collection. Switching processors later does not strand your saved cards.

  • Portable. Tokens belong to you, not to the processor that saw the card first.
  • Contained. Raw card data stays inside the vault boundary, never in your app or logs.
  • Current. Network tokens pick up reissued cards without asking the customer.

Recovered revenue

Declines are money you already earned.

A customer who reached the pay button wanted to buy. Put in your own volume and decline rate and switch on the levers Finyst gives you.

Revenue recovered each month$143,488

$1,721,856 a year · about 2,759 orders a month at a $52 basket

Approved todayRecoveredStill declined
Approval today92.0%
With Finyst93.43%

Illustrative model, not a forecast. Assumes 60% of declines are soft and effects that vary a lot by business, region and card mix.

Reconciliation

Close the books before lunch.

Settlement lines from every processor are matched to your orders automatically. Only the exceptions reach a person, with the context to resolve them.

Reconciliation · settlement files for Sep 24Matching…
Matched0/10
Needs review0
Net settled$0.00
Processor fees$0.00
Internal orderAmountProcessorSettlement lineGrossFeeStatus
ord_10421Sale$120.00Stripetxn_3NqL…8f2$120.00$3.78
ord_10422Sale€89.00Adyenpsp_8816…402€89.00€1.69
ord_10423Sale$42.50Checkout.compay_k2x9…e1c$42.50$1.02
ord_10424Sale£310.00Adyenpsp_8817…19a£309.40£6.81
ord_10425Sale$18.00Stripetxn_3NqM…a07$18.00$0.82
ord_10426Sale$64.00Braintreenot in file——
ord_10427Sale€250.00Checkout.compay_k2xa…77d€250.00€4.75
ord_10428Refund-$99.00Stripere_3NqN…c11-$99.00—
ord_10429Chargeback$1,240.00Adyenchb_5510…e83-$1,240.00$15.00
ord_10430Sale₹4,999.00Razorpaypay_Nd81…Q2₹4,999.00₹99.98

Illustrative settlement data for a fictional merchant. Open a flagged line to resolve it.

For developers

One request. Any processor behind it.

Create a payment the same way whoever ends up taking it. Idempotency, retries and webhooks behave identically on every connector.

create-payment.sh

curl https://finyst.techyst.net/api/payments \
  -H "api-key: $FINYST_SECRET_KEY" \
  -H "Idempotency-Key: ord_10421" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 6540,
    "currency": "USD",
    "confirm": true,
    "customer_id": "cus_acme_8812",
    "payment_method": "card",
    "payment_token": "tok_9f3a2c71e0b4",
    "profile_id": "checkout-live"
  }'
POST/payments

Press “Send request” to replay one payment through the router. Sandbox data only.

REST APIWeb SDKReactiOSAndroidReact NativeFlutterNodePythonJavaGo

The difference

One processor at a time, or all of them at once.

A single processor is simple until it declines, goes down or reprices. Stitching several together by hand means a new integration every time. Finyst gives you one routing layer across all of them.

Single processor or hand-built integrationsFinyst
Saved cardsLocked to the processor that saw them firstPortable tokens, usable on any processor
Soft declinesLost sales, or a retry on the same routeRetried on the next best processor in milliseconds
Processor outageCheckout goes down with itTraffic fails over to the next route
Routing logicNone, or if-statements in app codeRules, splits, success rate and cost, versioned
Adding a processorA new integration projectAdd credentials, update a rule
PCI scopeGrows with every integrationKept contained by the vault and tokens
ReportingOne dashboard and file format per providerOne ledger, one set of statuses and decline codes
Fees on topOrchestration often adds a per-payment cutNo per-transaction fee from Finyst

Control and security

Built for teams who answer to auditors.

PCI scope kept contained

Card data enters the vault and never touches your application servers or logs, so the systems in PCI DSS scope stay few and well defined.

Encrypted, tokenised vault

Card data is encrypted at rest with rotating keys and replaced by tokens everywhere else. The vault keeps PCI DSS scope contained.

Audit log for every change

Rule edits, refunds, key rotations and dashboard sign-ins are recorded with who, what and when.

Role-based access

Separate roles for engineering, finance, support and admins, with refund limits per role and sign-in through your identity provider.

Signed webhooks

Every event carries an HMAC signature so your services can verify it came from your Finyst before acting on it.

Exports for finance and audit

Payments, refunds, disputes and settlement lines export to CSV or your warehouse on a schedule, with the rule version that routed each one.

Webhooks

Trust the event, not the network.

Each webhook is signed with a secret only your services and your Finyst know. Verify it in a few lines, then act.

webhooks.ts

// Verify a Finyst webhook before acting on it
import { createHmac, timingSafeEqual } from "node:crypto";

export function verify(rawBody, header, secret) {
  const expected = createHmac("sha512", secret).update(rawBody).digest("hex");
  return timingSafeEqual(Buffer.from(expected), Buffer.from(header));
}

// header: x-webhook-signature-512
// event:  payment_succeeded · pay_Q7f3a91c20 · adyen · attempt 2

FAQ

Questions, answered.

Payments carry real risk, so here are straight answers. If yours isn't here, write to us and an engineer who works on Finyst will reply.

Does Finyst replace Stripe, Adyen or our current processor?

No. You keep your processor contracts and merchant accounts. Finyst sits in front of them, decides which one takes each payment, and retries on another when that helps.

Which processors and payment methods can we connect?

The major card processors and acquirers, the big wallets and a long list of local methods, from iDEAL and SEPA to UPI and Pix. Coverage varies by country and method, so we confirm your exact list before kickoff and add new connectors as you need them.

Does Finyst make us PCI compliant?

No product can promise that on its own. Finyst keeps raw card data inside the vault, so your application servers only ever handle tokens. That keeps PCI DSS scope contained to a small, well-defined boundary. Your own assessment still applies, and we help you document the boundary for it.

How does pricing work?

Finyst doesn't take a cut of each payment, so your costs don't climb with volume. Your processors still charge their own fees. Ask us for a quote.

What if Finyst itself has a problem?

Finyst is built for high availability, with redundancy, continuous health checks, alerting and changes rolled out gradually. We agree an on-call and escalation path with you before go-live, and your team gets status updates the moment anything changes.

Who on our team can do what?

Roles separate engineering, finance, support and admins. Refund limits are set per role, rule changes can require a second approver, and sign-in goes through your identity provider with SSO. Every action lands in the audit log.

Can we bring saved cards over from our current processor?

Many processors will export stored card data to another PCI-compliant vault on request. We plan that migration with you, import them into the Finyst vault, and keep the old processor running until the move is verified.

How much work is the integration?

One API and one set of SDKs for web and mobile, in sandbox first. We set up your account, connect your processors and run test traffic with your team before a single live payment goes through.

Stop losing good payments. Route every one.

Connect your processors once, set the rules you want, and watch declines turn into recovered revenue, with every payment on one ledger.