Status page
Guides

Product Overview

Suggest Edits

Introduction

Paybis EMI On-Ramp lets Electronic Money Institutions embed crypto purchase experience while keeping control of fiat movement. The widget handles quote, request creation, and UX; you debit client balances and settle fiat to Paybis under a model we jointly define. Once you confirm irrevocable settlement via API, Paybis releases crypto to the client’s wallet delivering a smooth, compliant, and auditable flow with minimal client effort.

Key Benefits

  • Zero client effort on fiat: Clients confirm the purchase; you move funds from the client’s account.
  • Flexible settlement models: Fiat reaches Paybis, per partner agreement - internal account (at the partner/EMI) or external bank account.
  • Native experience: Embed the widget in your product and surface transaction history (fiat and crypto) in your UI via APIs.
  • Operational confidence: Crypto releases only after settlement is confirmed, with signed webhooks and shared IDs for clean reconciliation.

How It Works

  1. Integrate: Embed the Paybis on-ramp widget in your platform.
  2. Client login and verification: The client authenticates and completes KYC/KYB (as required) inside the widget.
  3. Select crypto and amount: Client chooses asset and amount. In this setup, the payment rail is internal transfer within your EMI system.
  4. Accept quote and enter wallet: Client confirms the quote and provides the payout wallet address.
  5. Confirm transaction: Client confirms and can leave the widget; the rest is automated.
  6. Process payment (you): Your backend fetches bank details and amount via API, debits the client, and settles fiat to Paybis under the agreed model.
  7. Notify settlement (you): Send a signed webhook to confirm completed (irrevocably settled) or failed (cancelled/reversed/unprocessed).
  8. Crypto payout (Paybis): On valid completed confirmation, Paybis executes the crypto payout to the client’s wallet.

What You Build

  • Front end: Embed widget; listen to the emi-payment-created event and persist the orderId.
  • Back end:
    • Retrieve EMI payment details (amount, currency, bank requisites) for the request.
    • Move client funds accordingly and confirm final status via webhook.
    • Expose transaction history to your clients by reading Paybis APIs and rendering it in your UI.

What You Control

  • Settlement path and timing (internal vs external).
  • Client debiting and internal ledgering.
  • Final status confirmation (webhook).

What Paybis Provides

  • Widget UX (quote, request, bank details capture).
  • API endpoints for payment details and webhooks, plus retrieval endpoints for history.
  • Secure verification (API keys, RSA-PSS signed webhooks) and deterministic reconciliation via shared IDs.

Getting Started

  • Embed the widget and capture orderId.
  • Call the EMI payment-details endpoint to obtain the exact bank requisites.
  • Settle fiat under the chosen model and send a signed webhook when irrevocably settled.
  • Display history in your product by reading transactions via API.

Updated 2 days ago