Corefy integration

Corefy is a payment orchestration and payment-infrastructure platform used by PSPs and merchants. Omno is listed as a ready-made connector in Corefy's library, so a business that already runs on Corefy can add Omno's provider network as one more route, without a new integration on its side.

Updated

Cascading: an automatic fallback. If a provider is unavailable or rejects the request, the payment moves to the next provider in the rule, without the customer re-entering anything. Examples. Values are illustrative.
Type
Platform partner
Regions
Global
Flows
Pay-in, Pay-out
Currencies
USD, EUR, AUD, NZD, CAD
Status
Live
On this page4 sections

What does the Omno connector in Corefy do?

Corefy’s connector library lists Omno as a provider that can be added from the Corefy dashboard. Once a business enters its Omno account credentials in Corefy, Omno appears as a route in Corefy’s routing rules next to the business’s other providers. Corefy’s public connector page lists card pay-ins and pay-outs in USD, EUR, AUD, NZD and CAD for this connector.

For the business, that means one more route behind the same Corefy integration. For Omno, Corefy is a distribution channel: merchants reach Omno’s providers and routing without integrating Omno’s API directly.

Who is this for?

It suits two kinds of teams. The first already runs its payments on Corefy and wants extra card capacity or redundancy for high-risk traffic without starting a new integration project. The second is evaluating Omno and wants to test real traffic through an existing orchestration layer before deciding on a direct integration.

Teams that need Omno’s hosted checkout, Card Fields or Direct Links on their own checkout, eligibility rules by customer verification level, or the full transaction trail should integrate with Omno directly. Those features live in Omno’s own API and dashboard, not in a third-party connector.

How do routing and cascading work when both platforms are involved?

When a payment goes through Corefy to Omno, Corefy decides that Omno is the route. Omno then applies its own eligibility and routing rules to choose a provider inside its network, and if a provider is unavailable or rejects the request, it moves the payment to the next provider in the rule. The final status goes back to Corefy, which reports it to the merchant. Each layer logs its own decisions, so reconciliation should match transaction IDs across both systems.

Running two orchestration layers in a row is a trade-off. It adds redundancy and reach, but it also adds a hop, two sets of rules to keep consistent, and two places to look when something fails. Most teams that start this way either keep Omno as a backup route or move high-volume flows to a direct Omno integration once the numbers are clear.

How do you enable it?

  1. Open the connector library in your Corefy dashboard and select Omno.
  2. Enter the Omno account credentials you receive during Omno onboarding.
  3. Add Omno to your Corefy routing rules for the currencies and card flows you want to send.
  4. Test against fake payment providers, then switch on live traffic for a small share of payments and compare approval rates by route.

Frequently asked questions

Do I need a separate contract with Omno to use the Corefy connector?

Yes. The connector uses your own Omno account credentials, so you complete Omno onboarding first and then add those credentials in Corefy.

Which payment methods does the Corefy connector support?

Corefy's public connector page lists card pay-ins and pay-outs in USD, EUR, AUD, NZD and CAD. Local methods, crypto and the hosted checkout are available through a direct Omno integration.

Should I integrate Omno directly instead?

If you want Omno's hosted checkout, Card Fields, Direct Links, eligibility rules by customer verification level or the full transaction trail, a direct integration gives you all of them. The connector is the faster path when Corefy is already your main platform.

it will.

Tell us where your payments fail. We will show you how routing changes the outcome.

esc
↑↓ to move ↵ to open All results