Halo Dot
  • Intents
    • Getting Started with Intents
    • Transaction App to App Integration Guide
    • TT3 App to App Integration Guide
  • SDK
    • Accessing the SDK
    • SDK Mobile Integration Guide
    • Halo System Baseline
    • Branding Guidelines
      • Mastercard
        • Android SDK
          • Steps to Integrate
            • Step 1: Initialise
            • Step 2: Prepare
            • Step 3: Play
            • Step 4: Review
          • Android Reference App
          • Code and Formats
      • Visa
        • Android SDK
          • Step 1: Prerequisite
          • Step 2: Integration
          • Step 3: Integrations (Optional)
          • Appendix
  • API Docs
    • Authentication
    • Get Transaction Status and Details
    • Refunds
    • Integrator Merchant
  • Tap on Own Device
    • Create the Checkout
  • Security Guidance
    • Security Architecture
    • Key Management
Powered by GitBook
On this page
  • 1. Intent Integration Methods
  • 2. Intent Authorization
  • 3. Intent Use Cases
  • 4. Conclusion
  1. Intents

Getting Started with Intents

Pick the Intent Integration Method. Get required information from the Merchant Portal.

PreviousIntentsNextTransaction App to App Integration Guide

Last updated 1 month ago

1. Intent Integration Methods

The Halo.Go application currently provides different mechanisms to integrate and try our payment solution depending on your use case. The different methods are:

  1. Android Intents

  2. Deeplinking

Have a look at the image below as a guideline:

2. Intent Authorization

  1. To get started register on the Merchant Portal and retrieve your Merchant ID and API Key.

Get Merchant ID

The Merchant ID can easily be found on the Merchant Portal. From the Portal, navigate to Users. There, you will see your unique Merchant ID.

Get API Key

In the user table generate your API Key.

Note the warning pop-up when generating an API Key.

Since an API Keyis a sensitive value, it is stored as an encrypted value in our database and only presented in clear text once during the initial retrieval. It is the responsibility of the user to keep their API Key safe.

The combination of the MerchantID and the API-Key will be used to make API request to the backend see Intent Transaction for more details.

3. Intent Use Cases

With Halo Dot the exact same technology can be used for different use cases. However, the integration is slightly different to allow us to distinguish the use cases. The use cases and their specific integration guides are:

  • Transactions / Payments Acceptance

  • TT3 / Debicheck

4. Conclusion

Not what you are looking for? To get started with the Halo.SDK, have a look at this guide

API Key Warning
API Key