That guide applies to native implementations at Android e iOSfor both collection and affiliations.
Overview
Preparation
Platform, technical requirements, credentials and case of use defined before integrating.
Installation
SDK Added to project, solved dependencies and permissions set up by platform.
Functional Validation
Approved cozo, rejection, Affiliation and management of revised errors from the app.
Output to production
Ready evidence, revised production environment and validated flow with integrations.
Suggested route
1
Prepare the environment
Confirms target platform, credentials, sandbox environment and case of use: collection, affiliation or both.
2
Install the SDK
Add the library to your mobile project and valid dependencies, permits and initial configuration.
3
Implement the flow
Configure required parameters, callbacks, response management and user experience.
4
Sandbox Test
It runs approved, rejected and tested data-controlled scenarios.
5
Requests final validation
When the flow is stable, prepare evidence and coordinate the review with the integration team.
Checklist base
1. Preparation
1. Preparation
- Target platform as defined: Android, iOS Or both.
- Revised technical requirements by platform.
- Credentials and testing environment available.
- Case of defined use: collection, affiliation or both.
2. Installation and configuration
2. Installation and configuration
- SDK correctly installed in the project.
- Validated supported dependencies and versions.
- Rejected permits, network configuration and sandbox environment.
- Initiation completed with no bug in the app.
3. Flow implementation
3. Flow implementation
- Mandatory parameters sent with proper format.
- Callbacks or list put in place for success, rejection and error.
- Navigation and return management to valid app flow.
- Sensitive data that are not exposed to client, login or display.
4. Functional Validation
4. Functional Validation
- Approved collection flow tested correctly.
- Rejected flow or validated controlled error.
- Affiliation flow tested if applicable.
- Revised messages and user experience.
5. Production
5. Production
- Sandbox complete with minimum evidence of evidence.
- Revised final build for production environment.
- Minimum logs available for support and diagnosis.
- Integration ready for live leave.
Points by platform
- Android
- iOS
Fat Dependencies
Confirms that the required dependencies, repositories and versions are set up.
Activity cycle
Check that SDK conduct proper navigation, return and app status.
- Review Requirements SDK Android.
- Validate installation from Installation Android.
- Prove Recovery from Start Alignet One SDK Android.
- Test affiliations if they are within range of the merchant.
Minimum approval criterion
Validated amount
At least an approved flow and one rejected properly revised Sandbox.
Controlled response
The app manages success, rejection, cancellation and errors without breaking the user’s experience.
Ready to certify
Evidence, logs and final build available for review with integration equipment.
Related guides
Android
Check the complete flow for Android.
iOS
Check the complete flow for iOS.
Test data
Use sandbox scenarios to validate SDK Mobile and other payment flows.
Installation iOS
Download and configure SDK iOS at your Xcode project.

