Error Handling
Learn how to properly handle errors and exceptions from the SDK to provide a smooth user experience.
Overview
The DigetPay SDK uses a sealed class hierarchy (DigetSposError) and typed exception (DigetSposException) to provide structured, actionable error information.
DigetSposException
Typed exception thrown in catch blocks
DigetSposError
Sealed class hierarchy for structured errors
Response Codes
Server response codes for transaction results
Custom Errors
Plugin-level error categories
DigetSposException
The SDK throws DigetSposException for SDK-specific errors. It wraps an DigetSposError with a typed error category and optional cause.
| Property | Type | Description |
|---|---|---|
| error | DigetSposError | The typed error object with code and message |
| message | String? | Human-readable error description |
| cause | Throwable? | Underlying cause, if available |
DigetSposError Hierarchy
The modern, type-safe error hierarchy used by the SDK. Each subtype carries a numeric code in a specific range.
| DigetSposError Subtype | Code Range | Category |
|---|---|---|
| DigetSposError.InitializationError | 1xxx | SDK setup and auth failures |
| DigetSposError.NetworkError | 2xxx | Connectivity and server communication issues |
| DigetSposError.CardError | 3xxx | Card reading and NFC issues |
| DigetSposError.KernelError | 4xxx | EMV kernel processing failures |
| DigetSposError.TerminalError | 5xxx | Terminal configuration and binding problems |
| DigetSposError.TransactionError | 6xxx | Transaction processing failures |
| DigetSposError.AuthenticationError | 7xxx | Auth token or credential issues |
| DigetSposError.ValidationError | 8xxx | Input/parameter validation failures |
| DigetSposError.SecurityError | 9xxx | Security policy violations |
Error Handling Pattern
Use when-expression (Kotlin) or instanceof (Java) to handle each error category precisely.
Loading...Debug Logging
Enable debug logging during development: DigetSposPlugin.enableLogs(true)
Transaction Response Handling
Handle different transaction outcomes using the TxnResponse callback.
Loading...Common Errors
Frequently encountered error codes with causes and resolution guidance.
| Code | Category | Meaning | Resolution |
|---|---|---|---|
| 1001 | Initialization | Invalid auth credentials | Check your authToken or email/password |
| 1002 | Initialization | SDK not initialized | Call DigetSposPlugin.initiate() first |
| 1003 | Initialization | No terminal bound | Complete terminal binding in onTerminalBindingTask |
| 2001 | Network | Network connection timeout | Check device internet/network connection |
| 2002 | Network | Server unreachable | Verify API endpoint and network access |
| 3001 | Card | Card read timeout | Ask user to tap card again within timeout window |
| 3002 | Card | Unsupported card type | Only NFC-capable payment cards supported |
| 3003 | Card | Card communication error | Clean card/device NFC area and retry |
| 4001 | Kernel | EMV processing failure | Sync terminal to update EMV parameters |
| 5001 | Terminal | Terminal not activated | Call activateTerminal() first |
| 5002 | Terminal | Terminal binding required | Select terminal in onTerminalBindingTask callback |
| 6001 | Transaction | Transaction declined | Card declined by issuer — do not retry |
| 6002 | Transaction | Insufficient funds | Customer should use different card |
| 6003 | Transaction | Transaction already reversed | Cannot reverse same transaction twice |
| 7001 | Authentication | Session expired | Call initiate() again to create new session |
| 9001 | Security | Location validation failed | Enable real device location, disable mock locations |
| 9002 | Security | Certificate pinning failure | Check certificate validity and network proxy |
On this page
Downloads
Coming SoonSample apps, release bundles, and more content will be available here soon.