Getnet DocsGetnet Docs

Prerequisites and Configuration

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

This guide provides the necessary steps to set up your environment before integrating the Get Tap on Phone (App2App) solution. You must exchange specific configuration details with your processor to establish a secure, functional connection between your client application and the Tap on Phone platform.

Step 1: Set up your organization account

Before writing any code, you must configure your developer organization account on the platform. You also need to create one or more test merchant accounts.

Work with your assigned Implementation Manager, who manages this initial setup process for you.

Step 2: Obtain your platform credentials

During the onboarding process, your Implementation Manager provides you with the necessary credentials to access the platform. For an App2App integration, the most critical identifier you receive is the Client ID.

  • Client ID: A unique identifier for your organization. The platform uses this ID to correctly route Single Sign-On (SSO) permission requests to your backend API endpoint.

You must pass this Client ID in the operationMetadata field whenever you initiate an intent that requires SSO validation (such as initialization or refunds).

Step 3: Register your application details

To ensure the Tap on Phone platform only accepts requests from authorized sources, you must provide your Implementation Manager with the following details about your client application and backend:

  • Android Package Name: The unique application ID of your Android client app (for example, com.yourcompany.pos).
  • Android Certificate Fingerprint (SHA-256): The cryptographic hash of the certificate you use to sign your Android application. The platform uses this to verify the authenticity of your app.
  • SSO API Endpoint: A secure, internet-accessible HTTPS URL hosted on your backend. The Tap on Phone backend calls this endpoint to authorize user sessions and sensitive operations.

Step 4: Configure your test environment

In a production environment, all credentials and application details are strictly unique to your integration. However, to help you start developing and testing immediately in the sandbox environment, you can use a set of default, pre-configured values.

Use the following values to build your initial App2App intents:

ParameterSandbox Test Value
Android App Package Namecom.dejamobile.cbp.sps.app
Client ID4bac0922d476436697283b8238ba282b
Merchant ID19
User ID19
User Token1234567

Next Steps

Now that you understand the required credentials and configuration parameters, your next step is to prepare your server to handle the authorization requests from the Tap on Phone platform.

Proceed to Backend Integration: Handling SSO Requests to set up your SSO API endpoint.