All Seven Cores

Payments Core

Money Movement

One orchestration layer across payment methods, providers, countries, and brands.

Payments Core enables FinDech products to initiate, accept, route, reconcile, and manage payments across multiple providers, methods, jurisdictions, currencies, and use cases. It is designed to reduce dependence on a single provider while giving each product a consistent internal payment model.

Routing Model

One payment intent
  • Bank transfer
  • Card acceptance
  • Payment link and QR
  • Cross-border rail
One normalized status

Core Principle

One Intent, Many Rails

A product should express what it wants to happen once. Payments Core decides how it happens — which method, which provider, which fallback — and returns a single normalized status regardless of how many rails were involved.

Capabilities

What This Core Provides

Reusable Payments Core capabilities available to FinDech products, configured per product, market, and partner model.

  • Bank-transfer initiation
  • Card payment acceptance
  • Payment links
  • QR payments
  • Request-to-pay
  • P2P payments
  • Merchant collections
  • Cross-border transfers
  • Remittance workflows
  • Bulk and marketplace payouts
  • Payment-method orchestration
  • Provider routing and fallback
  • Fees and FX configuration
  • Payment status normalization
  • Refunds, returns, and reversals
  • Settlement and reconciliation
  • Webhook and event normalization
  • Payment receipts and evidence
Operating Model

How Payments Core Works

The same sequence underneath every product that uses this Core.

  1. Intent

    The product expresses one payment intent — pay, request, collect, or pay out — without choosing a provider.

  2. Evaluation

    Method availability, currency, fees, FX, jurisdiction, and Risk Shield evaluation are applied to the intent.

  3. Routing

    The intent is routed to a suitable provider and method, with fallback where a route is unavailable or fails.

  4. Normalization

    Provider webhooks and events are normalized into one internal status model shared by every brand.

  5. Settlement

    Settlement, refunds, returns, reversals, receipts, and reconciliation close the payment lifecycle.

Applications

Where This Core Is Used

Product categories this Core is designed to support. Availability depends on the product, jurisdiction, and selected partners.

  • Consumer payments
  • Business payments
  • Marketplace payouts
  • Merchant acceptance
  • Cross-border payments
  • Remittances
  • Payment links
  • Creator payouts
  • Affiliate payouts
  • Agent-initiated payments
Cross-Core

Designed To Work With The Other Cores

Payments Core is built to be combined. Each connection below is a reusable relationship, not a bespoke integration.

Portfolio Use Cases

Designed For Products Like These

Payments Core is intended to be reusable across the FinDech portfolio. The brands below are the products this Core is designed for — not a statement that each one currently uses it.

  • Paym
  • Chinatown Bank
  • NFI
  • GLWS
  • Woney
  • MONOBANK

Partner And Regulatory Boundary

Where FinDech Stops And Partners Begin

FinDech does not itself execute regulated payment services or hold funds in transit. Payment initiation, acceptance, and settlement are performed by banks, payment institutions, EMIs, acquirers, and other authorized providers. FinDech develops the orchestration technology used to connect products with those partners.

Build From The Core

Partner with FinDech to develop financial products using reusable infrastructure across crypto, cards, banking, payments, deals, investing, and risk protection.