SDK Libraries

Android SDK

Use mobile-safe Android helpers for checkout intents, Custom Tabs, return deep links, and backend-created payment links.

Overview

Use mobile-safe Android helpers for checkout intents, Custom Tabs, return deep links, and backend-created payment links.

  • Runtime: Mobile checkout
  • Package: io.makepay:makepay-android
  • No API secrets on device
  • Checkout intents
  • Deep-link parsing

Installation

implementation("io.makepay:makepay-android:0.1.0")

If the package registry entry is not published in your environment yet, pin the source repository to a reviewed commit and follow the repository README until the package release is available.

Authentication

Create a MakePay API key in MakeCrypto and store the key ID and secret outside source control.

Do not put MakePay API secrets in the client application. Create payment links through your trusted backend, then pass only hosted checkout URLs or short-lived session data to the app.

See API authentication for header names, rotation, and permissions.

Use the SDK or source client to call the MakePay payment links API with an amount, currency, label, customer context, return URL, and metadata. Persist the MakePay payment UID beside your internal order or invoice ID.

The request and response model is documented in payment links.

Webhook verification

Read the exact raw request body, verify the MakePay signature, reject stale timestamps, and process events idempotently.

The signing model and event payloads are documented in webhooks.

Framework notes

  • No API secrets on device
  • Checkout intents
  • Deep-link parsing
  • Keep request creation, webhook verification, and fulfillment updates in trusted backend code.

Source and releases

Review the repository README, examples, and release notes before using the package in production.

Source repository: github.com/makepay-io/makepay-android

Troubleshooting

  • Authentication failures usually mean the key ID and secret belong to different environments or were copied after rotation.
  • Webhook failures usually mean the handler parsed JSON before signature verification or the configured webhook secret does not match.
  • Checkout issues usually mean the backend did not persist the MakePay payment UID or returned an expired checkout URL.

Need partner setup help?

Open the payment link details view in MakeCrypto to copy the generated snippets for a real payment UID, or return to the portal to manage merchant settings.

Open portal