Skip to content

v1.0 Android Kotlin & Java PCI-safe

Payments for your Android app

The DigetPay Android SDK adds hosted checkout, card payments, refunds, captures, and recurring charges through a single entry point — DigetPay. Clear guides, real code, and a generated API reference.

Get started Download the AAR

minSdk 24Android 7.0 and up

Kotlin & JavaFirst-class support

One objectSingle entry point

3-D SecureHandled for you

Overview

The DigetPay Android SDK handles checkout sessions, card tokenization, 3-D Secure redirects, status verification, and result routing, so you can focus on your product instead of payment plumbing.

The recommended path is short: install the AAR, initialize DigetPay once, run a hosted checkout, store the returned IDs on your backend, then use the operation APIs — status, capture, void, refund, recurring — when your flow needs them.

What you can build

  • Hosted Checkout

    Open a DigetPay-hosted payment page and keep card data out of your app — the safest default.

    Read more

  • Card Payment

    Collect card data in-app and run a server-to-server sale with 3-D Secure handled for you.

    Read more

  • Recurring

    Tokenize a card once, then charge subscriptions or installments later.

    Read more

  • Operations

    Check status, capture authorizations, void, and refund transactions.

    Read more

  • Callbacks

    Handle outcomes with PaymentCallback and OperationCallback.

    Read more

  • Error Handling

    Predictable failures with structured ErrorCode values.

    Read more

How a payment flows

1

Initialize once — Call DigetPay.initialize() at app start with your DigetPayConfig.

2

Start checkout — Call DigetPay.checkout() with the amount, currency, and customer details.

3

Customer pays — The SDK opens the hosted checkout screen and watches for the redirect.

4

Verify & return — The SDK verifies the final status, then PaymentCallback reports success, failure, or cancellation.

Store sessionId, transactionId, and orderId on your backend after success. Don't rely only on the visual success page for critical order state.

Requirements

Minimum SDK
24 (Android 7.0)
Compile SDK
36 (recommended)
Kotlin
2.0+
Java target
11
Internet permission
Added automatically by the SDK

Dependencies are not bundled

The AAR does not embed transitive runtime dependencies (Retrofit, OkHttp, Coroutines, AndroidX). Add them explicitly in your app module — see Installation.

What's in the SDK

  • DigetPay

    The entry point: initialize, checkout, card payments, operations, and recurring charges.

  • DigetPayConfig · Environment

    API key, environment (SANDBOX / PRODUCTION), and logging options.

  • Request & result models

    CheckoutRequest, CardPaymentRequest, RecurringRequest, PaymentResult.

  • Callbacks

    PaymentCallback for payments, OperationCallback for operation results.

Start integrating