AAakashPay

Integration
Guide.

The official guide for connecting an Android application, merchant workspace or WebView to AakashPay.

Current access model

The merchant console now uses the Android-generated Client ID for each sign-in. Firebase email-link verification is no longer required in the merchant flow.

Official Android client

Install the AakashPay app.

The latest approved Android release will appear here after an administrator publishes the APK.

No release published

1. Register the Android application

On first launch, create a stable Android device identifier and register it. The resulting Client ID is the identity of the device, merchant workspace and connected project.

POST https://akashpay-api.axura.workers.dev/v1/public/devices/register
Content-Type: application/json

{"deviceId":"your-stable-android-id","deviceName":"Production Reader","version":"1.0.0"}

Store the returned clientId. The Android app should also send an activation event when installation or project activation completes.

POST https://akashpay-api.axura.workers.dev/v1/public/activation

{"clientId":"client_your_id","deviceId":"your-stable-android-id","projectId":"project_main","version":"1.0.0"}

2. Merchant sign-in

Open the Merchant Console, enter the Client ID and continue. The API returns an HTTP-only session cookie. Every later merchant request is scoped to that authenticated Client ID.

Merchant overview

Use GET /client/me for counts, projects, payments and activity.

Project view

Use GET /client/projects for active and locked project records.

Payment verification

Use GET /client/payments for pending and completed verification states.

Audit activity

Use GET /client/activity for merchant and activation history.

3. WebView setup

Point the Android WebView to https://akashpay-app.pages.dev/. The app surface is designed as a mobile application workspace with bottom navigation for overview, logs, payments, projects and account. Pass the Android interface methods used by the existing app so the WebView can obtain the current device identity.

4. Payment API

Use the API key issued from the merchant workspace for server-to-server payment operations. Keep it on your backend only; never embed it in a public Android bundle or browser script.

POST /v1/payment/create
X-API-Key: ak_live_...
Content-Type: application/json

{"amount":100,"customer":"01700000000","redirectUrl":"https://example.com/return"}

5. Project and payment states

active projects are operational. locked projects remain visible but should not initiate new production operations. Payment verification records use pending, verified or rejected. The merchant workspace shows these states without exposing another merchant's records.

6. Admin operations

The main admin panel uses the private Admin Token. The analytics endpoint is GET /admin/analytics and reports active merchants, active sessions, Android activations, active projects, locked projects, pending payments and recent audit events. The activation endpoint is GET /admin/activations.

7. Migration from Firebase email links

  1. Remove the email-link login screen from the Android or merchant client.
  2. Register each Android installation and persist its returned Client ID.
  3. Use the Client ID login form for merchant access.
  4. Keep API keys and Admin Tokens server-side and rotate any key exposed during testing.
Security note

Client-ID-only access is intentionally simple but the ID acts as a bearer credential. Protect it, rate-limit attempts, and plan to add an Android device signature or PIN before handling sensitive production operations at scale.

AakashPay API · https://akashpay-api.axura.workers.dev