Skip to main content

Integration support

Integration Information​

In order to support our partners in an optional way, the integration team needs a information that allows to get a better understanding of the project and be optimal prepared for a smooth support. So please find below a set of questions that are needed for this support. If you are not sure about some answers, just add "unsure" to your answer.

Versions​

  • SDK version (if applicable):
  • WPI API version (if applicable):
  • WPI Bridge version: 1.0.6 (deprecated)

Solution Information​

  • Package name (e.g., com.myapp.name):\
  • How will the app be distributed?
    • Google Play Store
    • Mobile Device Management (MDM) system dedicated to the Merchant/Integrator
    • MDM system dedicated to the Device Manufacturer
    • If using MDM, specify its name:
  • Which operating system will the app run on?
    • Android — version:
    • iOS — version:
  • Which device is the app being developed for?
    • BYOD (Bring Your Own Device)—standard commercial off-the-shelf (COTS) devices, such as consumer phones or tablets that meet our requirements. Device details:
    • Dedicated enterprise devices (Sunmi, Zebra, Datalogic, etc.). Device details:
    • Dedicated Android payment terminal. Device details:
  • Which programming language is the app using?
    • Kotlin
    • Java
    • C++
    • Flutter / Xamarin.Forms
    • Other:
  • What is the integrator’s development environment?
    • Android Studio
    • Xamarin — Visual Studio
    • Other:
  • What types of transactions will the app use?
    • Purchase
    • Refund
    • Reversal (last transaction only)
    • Pre-authorization
  • What else will the app use?
    • Tap on Mobile receipts or custom-built receipts
    • Tips
    • DCC (Dynamic Currency Conversion)
  • Is this a local or international integration project?
  • Countries where the solution will be available:
    Enter in the “Terminal Country” field.
  • *MCC (Merchant Category Code) of the business ⭐ Important — This information must be provided by the Worldline Sales Partner. The MCC is used in the payment industry to classify merchants, see Merchant category code

Integration Steps​

The steps below apply to app-to-app (WPI) integrations as well as SDK integrations.

Phase 1: Intake & Request Initiation​

  1. Submit Integration Request:
    The integrator sends their integration request along with the completed integration checklist to their dedicated Sales Representative / Account Manager.
  2. Internal Handoff to Integration Support:
    The Sales / Account Manager creates an internal request for the Tap on Mobile (ToM) Integration Support Team.

Phase 2: Sandbox Provisioning & Welcome Package​

  1. Information Verification & Setup:
    Once all required information is verified, the ToM Integration Support Team initiates the onboarding setup:
    • Creates the test merchant account and test terminals on the ToM Sandbox backend, configured with terminal profiles defining accepted card schemes.
    • For Android: Whitelists the application package name in the Sandbox environment.
    • For iOS and backend-to-backend: Setup OAuth2 Sandbox credentials, preferably using a technical user.
  2. Official Welcome Email:
    The ToM Integration Support Team sends an official Welcome Email to the integrator. This email includes:
    • Sandbox portal invitation link, where users set their password to manage and manually register terminals.
    • Sandbox terminal credentials / OAuth2 details, if applicable.
    • Links to official developer documentation, test applications, and test card suites.

Phase 3: Development & Support​

  1. Development & Testing:
    The integrator develops the solution against the Sandbox environment.
  2. Technical Support:
    At this stage, any technical questions or support requests are addressed directly to the ToM Integration Support Team. Integrators should provide relevant logs and transaction details to ensure prompt support.

Phase 4: Validation Session​

  1. Submit Validation Deliverables:
    Once integration and end-to-end sandbox tests are complete validation has to be made, see Integration Validation. The integrator submits the required validation deliverables to the ToM Integration Support Team:
    • A completed validation Word document detailing test case results.
    • Video recordings demonstrating the partner application executing the payment flow and required scenarios.
  2. Production Package Whitelisting:
    The integrator provides the final Production application package name to the ToM Integration Support Team to be whitelisted for the production environment.
  3. Validation Review & Approval:
    The ToM Integration Support Team reviews the submitted documentation and video recordings, confirms test compliance, and marks the application as approved / ready for production.

Phase 5: Production Handover & Go-Live​

  1. Handoff to Sales:
    The ToM Integration Support Team informs the Sales / Account Manager that technical validation is complete and the production package has been added.
  2. Production Onboarding:
    The Sales / Account Manager drives the production onboarding:
    • Initiates production account, terminal, and user creation in the Production Portal.
    • Requests production OAuth2 credentials, if backend-to-backend registration is used.
    • Production portal activation invites are sent to the merchant/partner.
  3. Go-Live:
    The solution is registered in production and ready to process live transactions.

Integration Steps Diagram​