SDK Access & Distribution
This page explains how partners receive access to the Netevia Tap to Pay SDK and how SDK releases are distributed.
Overview
Netevia provides partners with SDK packages for integration into partner-owned mobile applications.
The SDK package allows partners to add Tap to Pay acceptance to their own apps while Netevia remains the PSP and manages the payment-side setup, merchant configuration, and production enablement.
Available SDKs
Netevia provides SDK access for the following platforms:
- iOS — Tap to Pay on iPhone
- Android — Tap to Pay / SoftPOS
Each platform has its own installation method, requirements, and release package.
SDK Repositories
Partners may receive access to Netevia SDK repositories for the platforms they are approved to integrate.
SDK repositories may include:
- SDK release package
- Installation instructions
- Platform requirements
- Version information
- Release notes
- Integration examples
- Links to full documentation
- Support contact information
iOS SDK Distribution
The iOS SDK may be distributed through one or more supported methods:
- Swift Package Manager
- CocoaPods
- Static framework
- XCFramework
- Partner-access SDK repository
The exact distribution method will be confirmed during partner onboarding.
Android SDK Distribution
The Android SDK may be distributed through one or more supported methods:
- Maven
- Gradle dependency
- AAR package
- Partner-access SDK repository
The exact distribution method will be confirmed during partner onboarding.
Partner Access
SDK access is provided by Netevia after partner approval.
Before SDK access is provided, Netevia confirms:
- Partner eligibility
- Target platform
- App ownership
- Technical owner
- Integration scope
- UAT readiness
- Required agreements or approvals
Partners should only use the SDK for approved applications and approved integration use cases.
What Partners Receive
A partner should receive:
- SDK access for the approved platform
- Installation instructions
- Platform-specific requirements
- UAT environment instructions
- Configuration guidance
- Apple entitlement guidance, if integrating iOS
- Testing checklist
- Production launch checklist
- Support and escalation process
SDK Versioning
Each SDK release should include a clear version number.
Release information may include:
- SDK version
- Release date
- Supported platform
- New features
- Bug fixes
- Breaking changes, if applicable
- Migration steps, if applicable
- Known issues, if applicable
Partner Responsibilities
The partner is responsible for:
- Reviewing SDK installation instructions
- Integrating the SDK into their application
- Following platform-specific requirements
- Testing the SDK in UAT
- Managing their application release process
- Coordinating production rollout with Netevia
Netevia Responsibilities
Netevia is responsible for:
- Providing SDK access
- Providing integration documentation
- Supporting UAT setup
- Supporting merchant/payment configuration
- Supporting production enablement
- Communicating SDK release updates
- Providing first-line integration support
Security Requirements
Partners must follow secure implementation practices.
Production credentials must not be:
- Hardcoded into public source code
- Shared through unsecured communication channels
- Stored in plain text
- Used outside the approved production environment
- Shared with unauthorized users or systems
Partner applications should use only the approved configuration flow provided by Netevia.
Technical Integration Instructions
Platform-specific technical installation instructions are provided in the SDK repositories.
Partners should use the SDK repositories for:
- SDK installation
- Dependency setup
- Code examples
- SDK initialization
- Payment flow examples
- SDK version details
- Release notes
This documentation portal explains the partner onboarding process, Apple approval requirements, testing expectations, production launch flow, and support model.
SDK Access Checklist
Before SDK access is provided to a partner, confirm the following:
- Partner has been approved by Netevia for SDK access.
- Required agreement or commercial approval is in place.
- Target platform is confirmed: iOS, Android, or both.
- Partner technical owner is identified.
- Partner support owner is identified.
- Partner has confirmed the app name.
- Partner has confirmed the iOS bundle ID or Android package name.
- SDK distribution method is confirmed.
- UAT access process is confirmed.
- Production access approval process is confirmed.
Summary
Partners receive access to Netevia SDK repositories or SDK packages for approved platforms.
The SDK package should include everything needed to integrate, test, and prepare for production launch.
Netevia remains the PSP and provides payment-side setup, merchant configuration, SDK documentation, and first-line integration support.
