Overview & Decision Guide

DigetPay provides REST APIs, SDKs, and payment applications for online, mobile, and in-store payment scenarios.

Use the guide below to choose the integration option that best fits your business and technical requirements.

Choose the right integration

Need	Use
Website checkout redirect	Hosted Checkout + Integration Guide
Custom website checkout	Embedded Integration + Integration Guide
Android tap-to-pay	SoftPOS
Fixed retail terminal	SmartPOS
WooCommerce / CMS	Plugins Hub · WooCommerce · OpenCart 3

REST API vs SDK

	REST API	SDK
Authentication	`x-api-key`	SDK token or SDK-specific credentials
Integration	Your backend application (PHP, Node.js, Java, etc.)	Mobile or client application
Use case	Server-to-server payment operations and backend integrations	Native mobile payment experiences
Documentation	API Reference and integration guides	SDK-specific integration guides

Note: SoftPOS and SmartPOS are dedicated payment applications and device-based solutions. Their authentication and provisioning flows may differ from standard mobile SDK integrations.

SDK authentication and tokens

Some DigetPay SDKs use SDK tokens to authenticate the application with DigetPay services.

The typical token lifecycle is:

Generate an SDK token from Dashboard → SDK Tokens.
Provision the token securely to the authorized application or device.
The application uses the token to authenticate with DigetPay services.
Rotate or deactivate the token when required, such as when a device is replaced or lost.

For detailed authentication and token-management requirements, see SDK Tokens & Authentication.

Related products

SoftPOS

Accept contactless payments directly on compatible Android devices.

SmartPOS

Accept payments through dedicated POS terminals.