Skip to content
Goatify

Payment infrastructure we plan to build

A payment gateway and orchestration platform for digital businesses, from API request to reconciliation. Everything on this page is planned product scope, not a service available today.

Connect

How digital businesses could connect to the planned platform.

  • Payment APIs

    One API for payment requests, refunds and status checks across connected providers.

  • Real-time webhooks

    Event notifications, so merchant systems can react when a payment status changes.

  • Multiple acquiring connections

    More than one acquirer or licensed provider, each under its own agreement.

Route

How each payment request would find its way.

  • Payment orchestration

    A layer that manages how payment requests move between connected providers.

  • Smart routing

    Rules that choose a route by method, country, currency or provider availability.

  • Cascading and retry logic

    Fallback to another route after a soft decline or technical failure, within scheme rules.

Operate

How businesses could manage payment operations.

  • Payment gateway

    A planned gateway for businesses to manage payment methods and connected providers through one integration.

  • Multi-merchant management

    Configuration, permissions and settings for many merchants in one place.

  • Merchant dashboard

    A view of each merchant's payments, statuses and reports.

Reconcile

How records would stay accurate afterward.

  • Transaction reporting

    Searchable records and exports across methods and providers.

  • Reconciliation

    Matching gateway records against provider reports to surface differences.

  • Refund management

    Full and partial refund requests, tracked through to the provider's response.

Planned. Scope may change as partners and our regulatory structure are defined.

How cascading would work

Connecting more than one provider gives a payment request somewhere else to go when the first route cannot complete it.

RequestRulesPrimary routeFallback route
  1. A payment request reaches the orchestration layer.
  2. Rules select the primary route.
  3. The provider's response returns to the merchant.

Concept illustration of planned behavior. It does not show a live system.

Rules and records in one place

The planned merchant dashboard would show routes, refunds, reports and reconciliation for each merchant.

Conceptual visualization. Providers are placeholders, and no rule is active.
Conceptual visualization. It contains no real or sample transactions.

Technology, not custody

We plan to provide the technology layer. We do not hold, receive, move or settle funds. Any regulated activity would be carried out by appropriately authorized entities.

Payments for your business. Across Europe.

Discover our planned approach to European payments and talk to us about your business needs. The gateway is still in development.