SoftPOS Overview

Accept contactless card and Mada payments on Android with DigetPay SoftPOS.

DigetPay SoftPOS turns a compatible Android device into a contactless payment terminal — no separate hardware required.

📘 SoftPOS SDK Documentation

The complete SoftPOS SDK implementation guide is available on the external DigetPay Developers portal:

Open DigetPay SoftPOS SDK Documentation


What SoftPOS is for

Use caseExample
Field salesPop-up stores, delivery drivers
Small retailShops without fixed terminals
EventsTemporary payment points

SoftPOS is designed for merchants that want to accept contactless card payments directly from a compatible Android device without deploying a dedicated payment terminal.


How SoftPOS fits into DigetPay

SoftPOS is an in-store payment channel, but the resulting transaction is handled through the same DigetPay transaction lifecycle used by other payment integrations.

The SoftPOS device initiates the payment, DigetPay processes the transaction through the configured payment provider, and the final transaction status becomes available through the standard transaction status and webhook mechanisms.

Transaction flow

sequenceDiagram
    participant C as Customer
    participant S as SoftPOS Android Device
    participant D as DigetPay
    participant P as Payment Provider
    participant M as Merchant Backend

    C->>S: Tap contactless card
    S->>D: Initiate SoftPOS transaction
    D->>P: Process payment
    P-->>D: Transaction result
    D-->>S: Payment result
    S-->>C: Approved / Declined

    D-->>M: Webhook notification
    M->>D: Check transaction status
    D-->>M: Final transaction status

Transaction lifecycle

  1. The customer taps a contactless card or supported payment method on the SoftPOS device.
  2. The SoftPOS application sends the transaction through DigetPay.
  3. DigetPay processes the payment with the configured payment provider.
  4. The payment result is returned to the SoftPOS application.
  5. DigetPay records the transaction using the standard transaction model.
  6. The merchant backend can receive the transaction update through the configured webhook.
  7. The merchant can also use the Transaction Status API to verify the final status.

This means SoftPOS transactions are not isolated from the rest of the DigetPay platform — they follow the same transaction and notification model.

Important: The exact SDK implementation, initialization, device requirements, and payment flow are documented in the external DigetPay Developers portal.


Requirements

RequirementDetail
DeviceNFC-enabled Android phone or tablet
OSAndroid 10+ (API 29+) with NFC — contact [email protected] for the latest device list
NetworkStable internet connection
SDK tokenGenerated from Dashboard → SDK Tokens
Merchant accountActive DigetPay merchant on Fin staging or production

Setup flow

flowchart LR
    onboard[Merchant onboarded]
    token[Generate SDK token]
    docs[Open SoftPOS SDK docs]
    install[Install SoftPOS app]
    provision[Provision SDK token]
    test[Test on Fin staging]
    live[Production go-live]

    onboard --> token
    token --> docs
    docs --> install
    install --> provision
    provision --> test
    test --> live
  1. Complete Business Onboarding.
  2. Generate an SDK token from SDK Tokens.
  3. Open the DigetPay Developers portal for the SoftPOS SDK implementation.
  4. Install the DigetPay SoftPOS application on a compatible Android device.
  5. Sign in and provision the device using the SDK token.
  6. Run test transactions on Fin staging.
  7. Verify transaction status and webhook handling.
  8. Go live using the production SDK token after completing the Go-Live Checklist.

Staging vs production

EnvironmentNotes
Fin stagingTest SoftPOS transactions without live settlement
ProductionLive transactions using a separate production SDK token

See Environments Overview for more information.


Transaction status and webhooks

SoftPOS transactions use the same DigetPay transaction concepts as other payment channels.

After a payment is initiated, merchants should use the standard transaction handling model:

  • Webhook — receive asynchronous transaction updates.
  • Transaction Status API — verify the current or final transaction status.
  • Merchant Dashboard — review transaction details and history.

For integration guidance on transaction status and webhook handling, see:

Best practice: Treat the webhook as a notification that a transaction status has changed. For critical business logic such as order fulfillment, use the Transaction Status API to verify the final transaction state before completing the order.


Online vs in-store

SoftPOS is an in-store payment channel and is separate from online Hosted Checkout flows.

IntegrationPayment experience
SoftPOSCustomer taps a contactless payment method on an Android device
Hosted CheckoutCustomer completes payment through a hosted online checkout
S2SMerchant backend directly integrates with DigetPay payment APIs

See Hosted Checkout Integration for online payment integrations.


SoftPOS SDK documentation

The complete implementation documentation is maintained separately on the DigetPay Developers portal.

Android SoftPOS SDK

The external SDK documentation covers the Android-specific implementation, including:

  • SDK integration
  • Device and NFC requirements
  • SDK initialization
  • Authentication and provisioning
  • Payment initiation
  • Transaction results
  • Error handling
  • Testing and troubleshooting

→ Open DigetPay SoftPOS SDK Documentation


Support

For the SoftPOS application distribution link, supported-device list, or integration assistance, contact:

[email protected]


Related


Did this page help you?