Crypto-friendly PSP

An example use case of how the Terminal can be utilized.

Customer Profile

A Payment Service Provider (PSP) already offering some crypto services, or working with crypto-native clients, that wants to upgrade to a robust, production-grade crypto payment solution with more control, scalability, and compliance.

Problem

The PSP may already support crypto payments using basic infrastructure or third-party wallets, but needs better custody, webhook handling, gas management, and multi-chain support to scale effectively and serve higher volumes securely.

Solution

Inabit Terminal provides a scalable infrastructure for crypto payments with advanced customization, organizational hierarchy, and integration tooling. PSPs can operate multiple organizations (e.g., per merchant) and automate flows via API, enabling enterprise-grade crypto payment processing.

Actors

• PSP (integration owner

• Merchant clients (end users)

• End customers (crypto payers)

Integration Flow Explained

1. PSP enables Terminal via Inabit support.

2. PSP Implements the Inabit Approval App to access wallets and configure permissions.

3. PSP provisions organizations per merchant or segment (optional).

4. Widgets are created via the API with specific chains, assets, confirmation settings.

5. PSP integrates webhooks and/or uses polling to update merchant systems in real time.

6. PSP manages gas, settlements, and off-ramp logic through Inabit’s APIs and dashboards.

Relevant Features

• GraphQL API for full automation

• Multi-org setup for merchant isolation

• Advanced gas controls and refueling

• Webhook reliability with retries

• Support for on-chain settlement, fiat conversion, and reporting

Benefits

• Full control over payment flows and configurations

• Scalable architecture for high-volume PSP operations

• Enhanced compliance, visibility, and automation

• Better UX for crypto-native and hybrid merchants