SANDBOX
Sandbox Environment Development
The Development team creates comprehensive test environments for partner technical integration based on confirmed scope of work and approved API fields. Program code creation follows standardized naming conventions with two distinct scenarios.
Technical integration requires partners to provide HTTPS URL pages for webhook reception, while Project Management facilitates partner access to Jira systems through Support team requests. These access requests must contain partner organization names and comprehensive user lists with email addresses and names for individuals requiring system access.
Upon task completion, sandbox credentials are delivered to partners containing the necessary information for accessing the Sandbox environment and performing the relevant tests.
Top-Up Configuration
Top-up setup involves technical configuration of Merchant ID (MID) and Paynetics payment page systems.
Production environment top-up implementation requires more comprehensive procedures beginning with production instance creation. Partners complete designated forms for either Account Funding Transactions (AFT) or Original Credit Transactions (OCT) through the Pack Acquiring top-up program, declaring application URLs for Google and Apple platforms plus web platform URLs where applicable. Project Management forwards completed forms to Underwriting teams with MID creation requests, specifying AFT or OCT registration requirements, merchant names, and production instance declarations.
Partners can choose between Paynetics default payment pages or customized Paynetics payment pages requiring CSS file provision from partners for personalization purposes.
This comprehensive process ensures thorough evaluation, risk assessment, and proper integration of new partners while maintaining regulatory compliance and operational efficiency across all Paynetics departments.
PRODUCTION
Production Environment Setup
Production environment creation involves comprehensive coordination across all teams to establish live technical integration based on confirmed scope of work and approved API fields. Project Management begins by verifying all setup fees and pending invoices are properly paid and documented in the Projects Details repository.
Critical pre-production validation requires partners to complete comprehensive end-to-end testing in test environments with all requirements fulfilled before production switching. Project Management must inform all Paynetics departments about pending production switches and receive explicit confirmation from each department that partners are ready for live environment activation. This includes verification that all fees and limits are properly configured by CardOps teams for cards and Development teams for accounts.
Security protocols mandate partners provide PGP keys in both .gpg and .asc file formats for credential encryption. Task completion triggers partner notification and encrypted PGP file transmission. Partners initially conduct "friends and family" testing phases while providing estimated Go Live date projections. Two weeks prior to launch, Project Management coordinates with Account Management teams for assignment and facilitates internal handover meetings where Go Live letters are issued.
SDK for In-App Provisioning
The Mobile Development team provides SDK endpoints for partners requiring in-app provisioning capabilities when PCI DSS certificates are unavailable or development resources are insufficient. Prerequisites include completed Apple and Google Pay setup with Apple entitlements properly configured. Project Management provides comprehensive SDK documentation covering backend, iOS, and Android implementation guidelines.
Following documentation requirements, partners create endpoints enabling card addition to Google and Apple Pay platforms, providing these endpoints to Paynetics for SDK trigger operations as detailed in the SDK overview documentation. Partners complete integration and testing phases before conducting In-app Provisioning Lab certification procedures.