One integration · 4 providers connected
How it works
From four contracts to one.
Pharos sits between your storefront and the providers you already use. Live in an afternoon.
01
Drop in Pharos
Replace every PSP widget with one SDK — hosted, embedded, or fully custom.
02
Connect your PSPs
Bring existing contracts. We talk to Stripe, Mercado Pago, dLocal and dLocal Go natively.
03
Route & reconcile
Smart routing picks the best provider per transaction; every PSP settles into one ledger.
Platform
Everything you'd build in-house. Already built.
Smart routing
Rules + ML pick the optimal PSP per transaction — country, method, BIN, cost, historical auth.
Unified ledger
Every authorization, capture, refund and payout — across providers — in one double-entry ledger.
Retries & fallbacks
Soft declines auto-retried on a different provider. Recover roughly 3% of revenue.
Local methods
Pix, Boleto, OXXO, SPEI, PSE, Yape — surfaced natively per market, settled into one balance.
Fraud & risk
Provider-native signals stitched with our model. Block, challenge, or route around at the edge.
One reconciliation
Statements from every PSP normalized into a single export. Stripe-grade across your stack.
Developers
One SDK. Every provider, every market.
Replace four PSP SDKs with one. Switch routing strategies at runtime. Webhooks normalize into a single event stream.
Node
@pharos/node
Python
pharos-python
Go
pharos/go
Ruby
pharos-ruby
FAQ
The unglamorous questions.
Things finance & engineering both want answered before signing.
Yes. Pharos sits on top of your own contracts. You keep the rates you've negotiated; we orchestrate.
Every provider.
One control plane.
Ship a unified checkout in a sprint. Keep your PSP contracts. Lose the integration tax.