Skip to main content

MOBILE SDK / PREPARE · PROTECT · TEST

One guide.
From setup to testing.

← Mobile SDKMOBILE SDK / VALIDATE AND PROTECT
Use this checklist as a quick guide before requesting final validation of your Mobile SDK flow.
This guide applies to native Android and iOS implementations, for both payment and affiliation flows.

​
Security and best practices

Apply these recommendations when integrating Alignet One through the Android SDK or iOS SDK.

Mobile app

Invoke the SDK, present the payment or affiliation flow and display user-friendly responses.

Backend

Generate tokens, protect credentials, record operations and confirm final results.
Do not include credentials, secrets or sensitive logic in the app. Keep critical functionality on the backend.

​
Mobile security

Tokens

  • Generate the Access Token from the backend.
  • Do not persist sensitive tokens in insecure storage.
  • Avoid printing tokens or complete payloads in logs.
  • Do not upload private .aar, .xcframework or ZIP files to public repositories.
  • Use the version provided or approved by the integration team.
  • Validate compatibility before updating dependencies.
  • Use callbacks or delegates to update the user experience.
  • Confirm states from the backend when required by the method.
  • Handle cancellation, errors, timeouts and returning to the app.
  • Test Android and iOS separately.
  • Validate approvals, declines and controlled errors.
  • Review behavior with poor connectivity.
  • Keep the operation number and minimal logs for support.

​
Core checklist

1. Preparation

  • Target platform defined: Android, iOS or both.
  • Technical requirements reviewed for each platform.
  • Credentials and test environment available.
  • Use case defined: payment, affiliation or both.
  • SDK installed correctly in the project.
  • Compatible dependencies and versions validated.
  • Permissions, network configuration and sandbox environment reviewed.
  • Initialization completed without errors in the app.
  • Required parameters sent in the correct format.
  • Callbacks or listeners implemented for success, decline and error.
  • Navigation and return to the app flow validated.
  • Sensitive data not exposed in the client, logs or screens.
  • Approved payment flow tested successfully.
  • Declined flow or controlled error validated.
  • Affiliation flow tested where applicable.
  • Messages and user experience reviewed.
  • Sandbox completed with minimum test evidence.
  • Final build reviewed for the production environment.
  • Minimal logs available for support and diagnostics.
  • Integration ready to go live.

​
Platform-specific checks

Gradle dependencies

Confirm the required dependencies, repositories and versions are configured.

Activity lifecycle

Check that the SDK handles navigation, return flows and app states correctly.

Android

Review the complete Android flow.

iOS

Review the complete iOS flow.

Test data

Use sandbox scenarios to validate Mobile SDK and other payment flows.

iOS installation

Download and configure the iOS SDK in your Xcode project.

Production checklist

Gather evidence and coordinate final validation with Alignet before enabling live payments.