Android Production Deployment
Move the tested merchant checkout into production with SDK 1.0.7 and a signed release build. Use this guide after the Android Quickstart and alongside the Launch Checklist.
1. Provision Production Configuration
Use Koard Production and https://api.koard.com. Provision the production merchant, terminal, linked location, and merchant login credentials with the processor's assigned live identifiers. Select an available production processor configuration; UAT IDs and credentials are not interchangeable.
Initialize the SDK with its assigned production client key and KoardEnvironment.PROD. Keep privileged backend keys on your server. Obtain SDK client keys through your assigned account/developer access and keep real credentials out of source control.
2. Build the Release Variant
Resolve com.koard:koard-android-sdk:1.0.7 from Maven Central. The public demo's production flavor is prod; use assembleProdRelease for its release APK. Configure signing through your app's build/CI process, with the signing material kept outside source control.
SDK 1.0.7 includes consumer rules for R8. Test the minified release build that you will distribute; a debug build is not sufficient verification. Clean-rebuild any JVM/Flutter/React Native wrapper after changing the SDK version or payment method signatures. See Minification and R8.
Use Android's app signing guide for release signing and Play App Signing when distributing through Google Play.
3. Validate a Production Device
Use a supported physical device with NFC and the required Visa Tap to Pay Ready version. Disable developer options before enrollment, switching locations on an enrolled device, or payments.
Log in with the production merchant, select and display its active location, and complete the documented enrollment flow when needed. Block payments until readiness passes. Test logout, app restarts, lost connectivity, and merchant/location changes on the release build.
4. Verify Payments and Settlement
Coordinate controlled live testing with your processor and Koard contact. Production payments can move real money. Inspect the resulting status and amount, then perform the supported reversal or refund appropriate to the recorded transaction state.
Test the outcomes in your approved plan, including declines, cancellation, partial approval and surcharge decisions where supported, and recovery of a lost response. Verify signed webhook persistence/retries and reconciliation against batch events and processor reports.
The supported Fiserv integration manages batches automatically. TSYS/Elavon support explicit opening; Worldpay creates batches through host capture. Use Running Batches for the processor-specific behavior.
5. Distribute and Pilot
Choose your approved distribution path and complete its current requirements. For Google Play, follow the publishing checklist, including the release artifact, app content, listing, and rollout requirements applicable to your app.
Pilot with a small merchant group, monitor payment outcomes and settlement, and retain a way to pause new payment initiation if the rollout has a problem. Reconcile uncertain in-flight payments before another submission.
Release Checklist
- Production environment, client key, merchant, processor configuration, terminal, and location agree.
- Signed, non-debuggable, minified release build tested on supported physical hardware.
- KiC package visibility, kernel installation, NFC lifecycle, and readiness validated.
- Developer options disabled before enrollment and payments.
- Active location visible in settings and checkout; stale selections cleared after merchant changes.
- Payment outcomes, follow-up operations, response recovery, and settlement reconciled.
- Webhook deliveries persisted before acknowledgment and business failures retried.
- Distribution requirements completed and pilot/support ownership assigned.
