SwapnoPay Console

Developer workspace
storefront Demo workspace
Developer workspace

Your integration, at a glance.

Explore payment flows, test your integration, and inspect webhook events. This public workspace uses sample data.

API reference
API Volume (24h)
1,482
▲ 14.8% vs yesterday
Match Success Rate
99.85%
▲ 0.15% vs last week
Avg Webhook Latency
48ms
▼ 12ms faster
Active Devices
2 Online
● bKash + Nagad SIMs

phone_iphoneMFS Channel Health & Ping Latencies

Example channel metrics for exploring the payment workflow.

bKash (01712345678)
18ms
Nagad (01812345678)
24ms
Rocket (01912345678)
19ms
Upay (01612345678)
22ms

keySandbox & Live API Credentials

Example credentials for the sandbox. Replace them with your own merchant credentials when integrating.

pk_sandbox_swapnopay_88f92a1109
sk_sandbox_swapnopay_99a83b2201

paymentsReal Live Gateway Examples

Production-style gateway pages, checkout flows, merchant callbacks, and live testing scenarios for MFS payments.

speedCore Platform Health

Sample service indicators in this demonstration workspace.

API Gateway Router
Realtime Socket.io Engine
PostgreSQL / Admin Supabase
SMS Automation Receiver

terminalLive Console Terminal Stream

Real-time output log stream of mock requests and verification events.

[00:00:00] [OK] SwapnoPay Developer Console initialized. Ready for API testing and SMS simulation.

rocket_launchMerchant Integration Onboarding Wizard

Follow these 4 steps to test and launch your automated MFS checkout integration.

1. Create Developer Application Completed on project initialization (App ID: app_dreammart_01)
2. Register Merchant Gateway Configuration Pending - Configure MFS receiving numbers in API Explorer
3. Perform Test Payment in Sandbox Simulator Pending - Trigger mock bKash or Nagad SMS broadcast
4. Verify Signature & Webhook Delivery Pending - Awaiting automated webhook dispatch

playlist_playFull Payment Flow Simulator

Run the real merchant flow: create order → request payment → receive SMS → verify → dispatch webhook → settle order.

Status: waiting for sandbox trigger

smsMFS SMS Broadcast Simulators

Simulate incoming mobile operator SMS broadcasts to test real-time matching.

⚖ Dispute & Edge Case Simulators

Test order expiration timeouts, failed verification, and dispute resolution.

timelineOrder Lifecycle Pipeline

Track status transitions in real time as SMS events are parsed.

1. Order Created (PENDING) Waiting for matching MFS broadcast
2. SMS Intercepted by App Parsing TrxID & amount via Regex
3. Transaction Matched (PAID) Executing atomic SQL update
4. Webhook Dispatched Signed HMAC SHA256 payload sent

travel_exploreInteractive API Endpoint Explorer

Test SwapnoPay API endpoints live directly inside your browser console.

Click "Execute Endpoint Call" to dispatch request...

codeInteractive SDK & Code Generator

Customize parameters to dynamically generate complete checkout code for your tech stack.

// Code generates dynamically...

hubWebhook Event Delivery Ledger

Inspect payload dispatches, HTTP status responses, and HMAC signatures. Click any row to inspect full payload.

Timestamp Target Webhook URL Event Type HTTP Status Latency Action
No webhook events logged yet in this session. Run a Sandbox simulation to trigger deliveries.

menu_bookSwapnoPay Developer Documentation

Complete reference guide for integrating automated MFS payments, webhooks, and dispute resolution.

1. System Architecture Overview

SwapnoPay acts as an automated middleware bridge between your e-commerce platform and Android smartphones carrying mobile banking SIMs (bKash, Nagad, Rocket, Upay). SMS messages received by the Android app are matched against pending merchant orders in 1 to 3 seconds.

2. Authentication & Headers

All server-to-server API requests must include your sk_live_... Secret API key in the authorization header:

Authorization: Bearer sk_live_swapnopay_secret_key

3. Webhook Signature Verification

To ensure security, incoming webhook callbacks from SwapnoPay include an x-swapnopay-signature HMAC SHA-256 header signed using your merchant secret. Always verify signature header before marking orders fulfilled.

Notification message