Corefy

Corefy is a payment orchestration and gateway software layer for operators and payment businesses. It connects existing PSP and acquirer accounts, normalizes payment APIs, controls routing and cascading, presents a hosted checkout, and centralizes reporting and reconciliation.

Page updated August 13, 2026

Visit website

Company details

Organization typebrand

Statusactive

Websitecorefy.com

Research checkedJuly 11, 2026

Main categoryiGaming Payment Providers

Corefy is a trading name used across active UK companies Corefy Limited, number 12962906, and PayCore.io Limited, number 11654625. Corefy Limited owns the trademarks, while PayCore.io Limited has controller and processor roles. The customer-agreement company is contract-specific, and office details conflict with company records. The brand has no universal legal name.

Buyer decision brief

Use this summary to decide whether the offer belongs on your shortlist and which terms need a written answer.

iGaming Payment Providers iGaming Local Payment Method Providers

Fit and use case

Editorial fit

Gaming operators with several PSP, acquirer, wallet, or crypto provider accounts that need one routing, checkout, and reporting layer.

Primary offer: Corefy Payment Orchestration

Primary offer delivery

API
iFrame

Integration boundary: The operator integrates Corefy and connects existing PSP and acquirer credentials.

Critical contract questions

Start with unresolved terms, negotiated terms, and dependencies that need a named owner.

8 of 9

Resolve before shortlist

No usable standard answer is available on the public terms.

Software price and financial-provider costsNot disclosed: Corefy Payment Orchestration · Commercial terms
Configuration, token, and record exitNot disclosed: Corefy Payment Orchestration · Exit and portability

Fix in the signed order

The answer changes by operator, market, package, or negotiated order.

Provider and market approvalSet in contract: Corefy Payment Orchestration · Market and approvals
Contracting software companySet in contract: Corefy Payment Orchestration · Contract and supplier
Orchestration and connector scopeSet in contract: Corefy Payment Orchestration · Implementation
Chargebacks and payment incidentsSet in contract: Corefy Payment Orchestration · Operations and service

Assign outside supplier scope

The operator or another supplier needs a named owner for this dependency.

Settlement and reconciliationExternal dependency: Corefy Payment Orchestration · Operations and service

Reconfirm before signature

A current boundary is available, but the final order still needs to match it.

1 of 2 shown

Merchant relationshipsPublished boundary: Corefy Payment Orchestration · Contract and supplier

Next buyer step

Ask Corefy to resolve “Software price and financial-provider costs” and “Configuration, token, and record exit” before moving Corefy Payment Orchestration to a commercial shortlist. Then compare the answer with the complete product record below.

Read the full product record Open the category RFP builder

Confirm every selected term in the proposal and signed order. No price, market approval, availability, or contracting entity is implied unless it is stated above.

What this provider offers

1 offering

OfferingCorefy Payment Orchestration
TypePayments · Multi Product
Ownership and packagingFirst Party · Standalone
DeliveryAPI, iFrame
Compare in
- iGaming Payment Providers · Integrator
- iGaming Local Payment Method Providers · Integrator

Corefy Payment Orchestration

Multi ProductFirst PartyAvailability: Standalone

Corefy is not an acquirer, PSP, or crypto processor. It does not participate directly in financial transaction processing or hold funds, and clients retain direct contracts with their financial providers.

Products

Payments and payouts: Unified APIs and dashboards for transactions routed through connected external payment and payout providers.

Checkout: Hosted and customizable payment page that presents methods enabled through connected provider accounts.

Connectors: Ready-made integrations that require the merchant's own active account and credentials with each financial provider.

Routing and operations: Cascading, retries, reporting, reconciliation, tokenization, and merchant management tooling.

Integration: The operator integrates Corefy and connects existing PSP and acquirer credentials. Methods and routing are configured in Corefy, while payment and payout requests use its unified API or hosted checkout.

Delivery options

API

Delivery model

Unified orchestration API for an operator with direct contracts and active merchant accounts at external payment providers.

Operator license: Operator
Merchant of record: Unknown
Player data controller: Operator

Included

+ Provider connectors
+ Payment and payout routing
+ Cascading and retry logic
+ Unified reporting and reconciliation

Not included

! Acquiring
! Payment settlement
! Fund custody
! Gambling license
! Merchant underwriting by Corefy

iFrame

Delivery model

Hosted checkout that collects payment details and routes transactions through the operator's connected provider accounts.

Operator license: Operator
Merchant of record: Unknown
Player data controller: Operator

Included

+ Hosted payment page
+ Localized method presentation
+ Provider routing and fallback
+ Transaction reporting

Not included

! Merchant account
! Acquiring
! Settlement
! Guaranteed provider acceptance

Procurement record

Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.

Known is usable now. Contract specific changes by order or market. Not disclosed has no usable standard term. Unknown remains unresolved. Outside provider scope is handled by the operator or another supplier.

Use the provider procurement guide

Contract and supplier

Contracting software companyContract specific: Corefy is a trade name used by Corefy Limited and PayCore.io Limited. The order must name the signing company, software licensor, support entity, processor under the DPA, and any subcontractor rather than contracting only with the brand name.
Merchant relationshipsKnown: The operator retains direct contracts and active merchant accounts with its PSPs, acquirers, wallets, and crypto providers. Corefy does not process financial transactions or hold funds, and a connector does not confer merchant approval.

Implementation

Orchestration and connector scopeContract specific: The operator can use unified payment and payout APIs, hosted checkout, routing, cascading, tokenization, reporting, and reconciliation software. The signed technical schedule must list connectors, credentials, methods, routes, fallback logic, environments, and acceptance tests.

Operating responsibilities

Data and security rolesKnown: The customer is controller and PayCore.io Limited is processor for the processing covered by the current DPA. The order still needs route-specific PCI scope, token ownership, subprocessors, transfers, retention, breach duties, access logs, and provider-to-provider data flows.

Operations and service

Settlement and reconciliationOutside provider scope: Corefy does not settle or hold funds. It consolidates transaction and reconciliation data, while each financial provider controls settlement accounts, cutoffs, deductions, reserves, prefunding, and bank credits.
Chargebacks and payment incidentsContract specific: Corefy can centralize status and route transactions, but the connected PSP or acquirer controls chargebacks and financial disputes. The support model must assign incident ownership, evidence, retries, duplicate prevention, ledger correction, provider escalation, and audit records.

Commercial terms

Software price and financial-provider costsNot disclosed: License, volume, implementation, connector, support, minimum, and exit fees are not published. Processing rates, reserves, foreign exchange, dispute fees, and settlement deductions remain in the operator's separate financial-provider agreements.

Market and approval scope

Provider and market approvalContract specific: Corefy connector availability does not establish method, gambling, or market availability. The operator must hold approval from every underlying PSP or acquirer for its entity, licenses, domains, player countries, currencies, methods, and transaction directions.

Exit and portability

Configuration, token, and record exitNot disclosed: Routing rules, connector configuration, token portability, transaction exports, reconciliation history, credentials, termination assistance, and post-termination access are not established outside the customer agreement.

Best for: Gaming operators with several PSP, acquirer, wallet, or crypto provider accounts that need one routing, checkout, and reporting layer.

Strengths

+ Corefy excludes financial processing and fund custody from its orchestration role.
+ Operators must bring active merchant accounts for the connected payment providers.

What to verify in procurement

! Connector and payment method counts describe software integrations, not merchant approvals or direct Corefy payment coverage.
! Corefy Limited and PayCore.io Limited are both active group companies, so the signed agreement must identify the contracting entity.
! Reserves, settlements, accepted gambling licenses, market coverage, and underwriting remain with external PSPs and acquirers.

Reference documents7

Key public documents supporting the company identity, primary offer, delivery route, and highest-priority questions above.

More providers with similar products