Skip to main content
HighRiskPaymentProvider.comPayment provider reviews
Payment Hub

Company overview

About Corefy

What the company provides

  • Orchestrator
  • Gateway

Available countries, payment methods, data access, contracts and funds handling depend on the selected product.

Corefy is a payment-orchestration platform and payment hub that connects a merchant's own payment-provider and acquirer accounts through one integration.

It provides gateway, checkout, routing, payout orchestration, reporting and reconciliation software; it does not provide financial services, hold client funds or supply the merchant account.

Founded 2018corefy.comUpdated Jul 30, 2026

Selected product

Payment Hub

Connected payment-provider setup

  1. Connected payment account

    Not included with this product

  2. Connected-provider approval

    Separate approval from the connected PSP or acquirer

    Each connected payment provider sets its own account and activation requirements.

Primary legal entity

PayCore.io Limited

Jurisdiction
United Kingdom
Registration number
11654625
Company type
Private limited company

Legal entities by jurisdiction

One legal entity registered in United KingdomOne jurisdiction

The legal entity supplying a product can differ by product and country.

Product portfolio

Corefy products

Compare payment-orchestration products by provider connections, routing, tokenization, channel coverage, production activation and the external merchant-services boundary.

Payment Hub

Role in this product

  • Payment orchestration provider
  • Payment gateway

A technical orchestration layer for connecting the merchant's existing payment providers and acquirers, accepting payments, routing transactions, initiating payouts and consolidating provider data.

The merchant keeps the direct provider contracts, merchant accounts and credentials.

Related services
Payment orchestrationPayment routingDecline recoveryHosted checkoutEmbedded payment fieldsPayout orchestration
Features
PSP and acquirer connectionsOrchestrationGatewayCheckoutPayment vaultRecurring billingPayoutsFraud and riskReconciliationReportingCurrency management

Selected product

Payment Hub

Related services
6 capabilities
Features
11 capabilities

Orchestration platform, provider connections & funds boundary

Who supplies the orchestration layer, which processors or acquirers connect to it, who activates live processing and who handles merchant funds.

01 · Role in this product
Payment orchestration provider · Payment gateway
02 · Orchestration platform
Not included with this product
03 · Production activation
Each selected payment provider controls its own account activation
04 · Connected-provider funds
Corefy does not hold merchant funds or provide merchant settlement

Selected product: Payment Hub.

Payment orchestration

Payment Hub: routing, retries & provider failover

Review routing rules, retry behavior, provider failover, configuration ownership and the connected accounts required for live payments.

Selected product: Payment Hub

Included in Payment Hub

Features included with this product.

Solutions
Payment orchestrationPayment routingDecline recoveryHosted checkoutEmbedded payment fieldsPayout orchestration
Capabilities
PSP and acquirer connectionsOrchestrationGatewayCheckoutPayment vaultRecurring billingPayoutsFraud and riskReconciliationReportingCurrency management

Routing, retries & connected providers

Who controls routing and failover, and which connected PSPs or acquirers process and settle payments for Payment Hub.

Included

Currency management

Presentment currency, checkout conversion, merchant reporting currency and payout currency conversion.

Customer chooses currency

Dynamic currency conversion

Available
Yes
Configuration
Merchant-defined currency pairs, routing rules and exchange-rate sources
Connected payment providers · Payment Hub

Which connected providers must approve this setup?

Separate approval from the connected PSP or acquirer.

Client company country

Eligible client countries are not specified

Company offices do not establish client eligibility or merchant-account eligibility.

Connected-provider approval

Separate approval from the connected PSP or acquirer

Each connected PSP, acquirer or processor sets its own account and activation requirements.

Provider connection
Connected PSP or acquirer
Product
Payment Hub
01Product eligibility & acceptable use

Which businesses and provider connections can use this product?

Product eligibility and each connected provider's account requirements are separate decisions.

Restricted activity

Business restrictions

Product · MCC · jurisdiction · sales practice

Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.

Before applying

Provider setup requirements to confirm

Company eligibility, connected-provider requirements, credentials and activation timing are not fully specified.

Provider activation & restrictions

Required provider accounts, production credentials, prohibited activities and country restrictions.

  1. 01

    Which connected processors, PSPs, acquirers and payment methods must be contracted and active for this configuration?

    Required provider agreements, active accounts and production credentials depend on the selected configuration.

  2. 02

    Which products, MCCs, sales practices and jurisdictions are prohibited for this product?

    Product-specific restrictions on products, MCCs, sales practices and jurisdictions are not specified.

Payment methods & countries · Payment Hub

Which client countries, provider connections and payment methods are available for this orchestration setup?

Connected payment providers determine payment-method, country and currency coverage for this configuration.

Selected product

Payment Hub

Gateway and payment-provider configuration

Selected product

Client company

Eligible client countries are not specified

Business availability and connected-service coverage are separate requirements.

Payment connection capabilities

  • Unified provider API
  • Provider account connection
  • Provider credential management
  • Normalised API webhook and error handling
  • Provider switching

Availability depends on

  • Connected provider
  • Business country
  • Payment method
  • Currency

Corefy connects to payment providers, and the merchant must obtain approval from the PSP or acquirer used for the setup. Configuration-specific payment methods, countries and currencies are not specified.

01Selected product

Payment Hub capabilities and connections

These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.

Product capabilities

Connected provider types

  • Payment service providers
  • Acquirers

Connected payment providers

Connected payment providers

≥600 ready-made connectors

The number available to one merchant depends on the product, jurisdiction and agreement.

Types of connected payment providers

Payment service providers and Acquirers

The specific connected providers, their commercial terms, approval responsibility and country coverage depend on the merchant configuration.

Connected payment provider
02Countries & availability

Where can the client use the platform, which connected providers cover each market, and where can customers pay?

Client eligibility, connected-provider coverage, customer country, payment method and currency are separate parts of the setup.

Country coverage

Client, connected-provider, customer and product countries

  1. 01

    Client location

    Where can the company using the orchestration platform be registered?

    Eligible client countries are not specified

    This is where the client company is registered; it does not determine connected-provider or customer-country coverage.

    Client and provider-account eligibility
  2. 02

    Connected provider coverage

    Which connected provider accounts cover each target market?

    Set by the connected provider accounts

    Business-country, customer-country, currency and payment-method coverage depends on the selected processor, PSP, acquirer or payment-method connection. Corefy does not itself provide acquiring.

    Connected payment provider
  3. 03

    Customer location

    Where can customers pay from?

    Customer-country coverage is not specified for this configuration

    Customer-country coverage depends on the connected PSP or acquirer, payment method and currency. The exact country list is not specified for this product.

    Connected payment provider

Countries and payment methods

Countries and payment methods to confirm

  1. Which gateways, PSPs, processors and acquirers are available for each business country, payment method and currency?

    Payment methods, countries and currencies depend on the connected provider accounts and the merchant configuration.

  2. Which connected providers require a separate agreement, approval or production credentials?

    Commercial and account requirements differ by connected provider.

Pricing & funds · Payment Hub

What does Payment Hub cost, and which related charges are governed by another agreement?

Orchestration quote, billable events, minimum commitment and order-form terms

Pricing

Orchestration quote, billable events, minimum commitment and order-form terms

Pricing method

No public rate card; obtain the quote and order form

01Commercial terms

What makes up the quoted price?

Review the pricing plan, pricing model, fees and contract duration.

Quote & order form

No public rate card; obtain the quote and order form

02Billable events

Which billable events terms apply?

The payment, connection or workflow events that generate charges.

Billable events & unit prices

Not specified in the public pricing information

The quote or order form must identify each billable event, included allowance and overage rate.

03Settlement & payouts

Which provider settles merchant funds, and are payouts included?

The merchant settlement provider and terms are not specified unless listed below. Customer or third-party payouts are a separate service and may use another provider.

Merchant settlement & customer payouts

Sale proceeds and customer payouts

Settlement makes processed sale proceeds available to the merchant. A payout sends separate funds to a customer or third party.

01 · Minimum commitment

Minimum commitment

Any minimum monthly or annual spend required by the agreement.

Minimum commitment

Amount not specified

The applicable commitment is set in the order form.

02 · Order-form terms

Order-form terms

Initial term, renewal, cancellation notice, billing cycle and invoice currency.

Contract & invoicing

Monthly or annual billing; cancellation is available at any time.

Pricing & settlement terms

Terms to confirm in the agreement

Other terms

  1. What total price and included usage appear in the quote or order form?

    The public pricing information does not provide a usable total price.

  2. Which events or account units are billable, and what is the unit price for each?

    Billable events, included allowances and overage rates are not specified.

  3. What monthly or annual minimum commitment applies?

    The minimum commitment amount is not specified.

  4. What initial term, renewal rule, cancellation notice, billing cycle and invoice currency appear in the order form?

    The contract and invoicing terms are not specified.

Route decision flow · Payment Hub

How do routing, provider failover, decline recovery and decision logs work?

Routing rules, provider failover, decline recovery and decision logs

Route decision flow

Routing inputs → provider selection → outcome → retry & logs

The orchestration setup determines routing inputs, provider selection, retry rules, failover and route-decision visibility.

Selected product

Payment Hub

Routing rules, connected providers, decline recovery and operational logs.

  1. Routing inputs

    Payment routing · Cascading

  2. Routes & failover

    Retry through next eligible provider · Cascading

  3. Payment routing responsibilities

    Corefy applies routing and recovery rules · Connected PSP or processor authorizes each transaction

  4. Routing controls & logs

    Included

01

Routing inputs

Which fields and rules can drive payment routing?

Transaction fields, merchant rules and provider state used to select a route.

Routing capabilities

  • Payment routing
  • Cascading
  • Automatic retries
  • Provider failover
  • Traffic splitting
  • Routing triggers
  • Dynamic currency conversion
  • Transaction blocking
  • Recurring token routing
02

Routes & failover

How are providers selected, retried and failed over?

Provider selection, volume splits, conditional routes, retries and failover.

Selected setup

Routing entry point

How requests enter this product and which integration boundary applies.

Routing modes

  • Priority routing
  • Balance based routing
  • Weighted routing
  • Turnover caps
  • Optimal routing
  • Rules-based routing

Routes & failover

Routing, retry and failover controls

Routing
01

Decline recovery

  • Retry through next eligible provider
  • Cascading

Recurring payment recovery

Recurring payment recovery

Retries, provider failover and controls for recurring payment recovery.

Recovery support
Not specified

Not specified

03

Payment routing responsibilities

Who selects routes, authorizes transactions and handles merchant funds?

Corefy selects and submits routes; connected payment providers authorize transactions and handle funds.

Payment routing responsibilities

  • Corefy applies routing and recovery rules
  • Connected PSP or processor authorizes each transaction
  • Connected acquirer or PSP handles merchant funds

Available controls

Corefy selects and submits routes; connected payment providers authorize transactions and handle funds.

  1. 01

    Connected provider types

    Which controls are available with this product?

    Connected provider types

    • Payment service providers
    • Acquirers
04

Routing controls & logs

Which route decisions, provider-health signals and retry outcomes are available?

Rule management, route decisions, provider health, retries and operational logs.

Routing controls & logs

Routing inputs → route decision → provider outcome → retry & logs

Rule changes, route decisions, provider health, retries and operational logs.

  1. 01

    Routing controls & logs

    Rule management, route decisions, provider health, retries and operational logs.

    Control panel

    Included

    Route-decision logs and provider-health fields are not specified.

Before integration

Integration details not specified

  1. 01

    Which fields can drive routing, how are rule priorities resolved and when do changes take effect?

    Routing inputs, priority rules and deployment timing are not specified.

  2. 02

    Which declines can be retried through another provider, and how are duplicate authorizations prevented?

    Retry eligibility and duplicate-authorization controls are not specified.

  3. 03

    Which route decisions, provider-health signals, retries and outcomes are available in logs or webhooks?

    Routing observability and event fields are not specified.

Routing, failover & support

Payment Hub: risk, licenses & support

Connected providers, routing rules, retries, failover, change controls, contracting entity and support.

01 / Routing & service continuity

What happens when a payment provider fails?

Routing rules, retry limits, failover behavior, duplicate-payment protection, rule permissions and rollback.

Routing & failover

Corefy routes transactions across connected payment providers

Payment routing and gateway connections do not make Corefy the processor or funds holder. Authorization and settlement remain with the selected connected payment providers under their own agreements. The Payment Hub agreement controls routing rules, retries, failover and access to routing data.

Role in this product
Payment orchestration provider · Payment gateway
Connected providers & merchant funds
Corefy does not hold merchant funds or provide merchant settlementThe funds holder and merchant settlement provider are not specified.

Provider outages & routing continuity

How are failed routes retried, switched or rolled back?

Timeout handling, retry limits, failover, duplicate-payment protection and routing-rule change controls belong in the agreement.

  • What happens when a connected gateway, processor or acquirer is unavailable or returns an uncertain result?

  • Who can change routing rules, and how are rule changes tested, approved and rolled back?

Fraud rules, 3-D Secure & provider disputes

Controls in the orchestration layer and risks held by connected providers

Fraud screening and 3-D Secure are available. The orchestration platform controls workflow routing, fraud-provider calls and available 3-D Secure options. Refunds, chargebacks, negative balances and settlement holds remain subject to the applicable connected-provider agreements.

  1. 01

    Before authorization

    Fraud screening

  2. 02

    At checkout

    3-D Secure authentication

BEFORE AUTHORIZATION

Fraud screening

Which fraud rules can block or flag a transaction for review?

Capabilities
Rule based transaction blockingSmart blacklisting3-D Secure controls
Cardholder checks
3-D Secure 13-D Secure 2Routing rule based 3-D Secure

AT CHECKOUT

3-D Secure authentication

Which 3-D Secure and verification methods are included?

3-D Secure
Yes
Before signingRouting, retry, failover, duplicate-payment and rule-change terms2 items to confirmReview contract terms
02 / Contracting entity & connected providers

Which legal entity signs the software agreement, and which connected-provider agreements are required?

The software contracting entity and each connected payment provider's regulated services are separate. The connected-provider agreements identify who processes and settles each payment.

For this product

Software contracting entity and connected providers

Payment orchestration. The contracting legal entity for Payment Hub is not specified. Payment Hub is a technology product; payment processing, merchant-account services and settlement remain with the selected connected providers under their own agreements and authorizations.

A software company registration or PCI DSS certification does not identify which connected provider processes or settles a payment.

  1. 01 · Software contracting entity

    Not specified for this product

  2. 02 · Product role

    Payment orchestration

  3. 03 · Connected payment services

    Separate provider agreements and authorizations

Company legal entities, licenses & registrations

Company registrations and payment-services licenses do not identify the contracting entity for every product.

1 entity · license or registration not specified

PayCore.io Limited

United Kingdom · Registry 11654625 · Private limited company

License or regulatory registration not specified

Security & regulatory information

These certifications, safeguarding arrangements and cross-border permissions apply to named company entities or to the company generally. Which ones apply to Payment Hub is not specified.

01

Security standards

Certifications and assessments

PCI DSS

Service provider level 1 · Entity: PayCore.io Limited

PCI DSS applies to PayCore.io Limited.

02

Security controls

Privacy and security controls

Security controls
Payment card tokenizationEncryption in transitEncryption at RESTMulti factor authenticationRole based access controlActivity loggingSigned webhooksNetwork segmentationContinuous security monitoringIsolated provider credential storage
Before signingContracting entity, payment services license and legal terms3 items to confirmReview contract terms
03 / Support

How can merchants reach support?

Company support hours and contact channels are available. It is not specified which ones cover Payment Hub and routing errors, failed retries or connected-provider outages. First-response and resolution targets are also not specified.

Support contacts

Company support hours and contacts

The contacts that cover this product and routing errors, failed retries or connected-provider outages are not specified.

Other company contacts

Support hours are not specified for these contacts.

General

info@corefy.com

Sales

sales@corefy.comcorefy.com/contact-us

Developer

docs.corefy.comcorefy.com/docs/integration/api-references

Privacy

info@paycore.io
Before signingSupport contacts, hours and response times3 items to confirmReview contract terms
Payment Hub / Before signing

What should the payment orchestration agreement include?

Confirm connected-provider agreements, pricing, routing rules, retries, failover, duplicate-payment protection, logs, support and termination.

Before signing

Payment Hub: terms to confirm

Confirm which providers can be connected, how routes and retries work, and who handles outages and uncertain payment results.

Providers, routing & pricing

Connected providers, usage allowances, route inputs and priorities, retry eligibility and premium features

Failover, control & observability

Provider outages, uncertain results, duplicate protection, rule permissions, rollback, logs and webhooks

Contract checklist

Terms to review by topic

Jump to the underlying product details

  1. 01Payment continuity & routing controlsProvider outages, uncertain results, duplicate-payment protection, permissions and rule rollback.
  2. 02Contracting entity & payment responsibilitiesPlatform contract, connected-provider agreements, data roles and any regulated payment service involved.
  3. 03Routing & provider supportContacts and response targets for routing errors, failed retries and provider outages.
Payment orchestration agreement

Routing and provider terms to confirm

Review pricing, connected-provider requirements, routing rules, retries, failover, duplicate-payment controls, logs, support and termination.

Payment continuity & routing controlsProvider outages, uncertain results, duplicate-payment protection, permissions and rule rollback.

  1. What happens when a connected gateway, processor or acquirer is unavailable or returns an uncertain result?

    Timeout handling, retry limits, failover behavior and duplicate-payment protection are not specified.

  2. Who can change routing rules, and how are rule changes tested, approved and rolled back?

    Routing-rule permissions, testing and rollback controls are not specified.

Contracting entity & payment responsibilitiesPlatform contract, connected-provider agreements, data roles and any regulated payment service involved.

  1. Which legal entity will sign the agreement for this product?

    The contracting legal entity is not specified for this product.

  2. Which privacy framework, controller roles and data-transfer terms apply to this product?

    The privacy framework, controller roles and data-transfer terms are not specified for this product.

  3. Who receives security incidents, and what notification window applies?

    The security incident contact and notification deadline are not specified.

Routing & provider supportContacts and response targets for routing errors, failed retries and provider outages.

  1. Who handles routing errors, failed retries, provider outages and duplicate-payment risks?

    No escalation contact or process is specified for routing and connected-provider incidents.

  2. Which support hours and contact channels cover Payment Hub, and where should a business report routing errors, failed retries or connected-provider outages?

    The support scope for Payment Hub and the contacts for routing and connected-provider issues are not specified.

  3. Which support-request topics and routing options are available in the support form?

    Support-form topics and routing options are not specified.

Product summary

What this product already includes

What the orchestration product includes, which provider restrictions apply and which routing terms are not specified.

Included capabilities

Capabilities included with Payment Hub.

  • Payment routing, Cascading, Automatic retries, Provider failover, Traffic splitting, Routing triggers, Dynamic currency conversion, Transaction blocking, Recurring token routing, Priority routing, Balance based routing, Weighted routing, Turnover caps, Optimal routing, Rules-based routing, and Retry through next eligible provider

  • Payment orchestration technology

Provider and routing conditions

Connected-provider approvals, agreements, credentials, operating limits and market coverage.

  • Connected-provider requirements, operating limits, event coverage and service levels depend on the selected configuration.

Terms to confirm

Pricing, provider, routing, retry, failover, observability and termination terms to include in the agreement.

  • Unit prices, usage allowances, overage rates, contract length, minimum spend and renewal terms are not specified.