Work / ŌURA
ŌURA · 2024 – present · 0 to 1 platform
Vault, then orchestrate.
One payments platform behind D2C, B2B, and subscriptions. The card is ours. The processor is a choice.
- Vault
- Basis Theory
- PAN out of app scope
- Processors
- Adyen · Braintree
- failover without re-collecting cards
- Products
- D2C · B2B · Subs
- one money path, three surfaces
The problem
If the processor is the source of truth for the card, you do not have a platform. You have a vendor. Failover means re-collecting PANs. 3DS is whatever that processor ships. A second market or a second product line becomes a second integration, then a third.
The design
Vault the card once in Basis Theory. Route each payment to the processor and local payment method with the best approval rate and the lowest fees in that market. Keep 3DS provider-agnostic so a challenge is not married to Adyen or Braintree. Do not expand PCI scope to buy that flexibility.
The same platform sits behind D2C checkout, B2B, and subscriptions. Authorization, capture, settlement, and reconciliation are shared problems. The product surface is not.
What this is for
Approval rate is a routing problem. Cost is a routing problem. PCI is an architecture constraint, not a checklist you visit after the integration works. If the vault is the source of truth, adding a processor is an adapter. If the processor is the source of truth, adding a processor is a migration.
I have lived the migration version. At Natural Cycles I led Braintree to Stripe and bought 13.36 points of approval. I would rather route than migrate.