Third-Party Application Integration Details

Overview

A Third‑Party application must notify the Moneris Payment application of its intention to receive notifications and exchange data at predefined integration points, also referred in this section as “hooks”. This one-time notification, called a Third‑Party Application Registration Request, is stored by the Moneris Payment application and used for all future interactions with the Third‑Party application.

When the transaction flow reaches one of the registered integration points / hooks, the Moneris Payment application transfers control to the Third‑Party application by issuing an Android startActivityForResult intent targeted to that application. This intent also includes the relevant transactional data, as defined within the scope of this document.

The transaction flow works as follows:

1. Moneris Payment app initiates a transaction by calling startActivityForResult with a hook-specific action (e.g.
   com.moneris.hooks.PreCardEntry for PRE_CARD_ENTRY integration)
2. This launches the registered third-party app's activity
3. The third-party app processes the transaction
4. Results are returned to Moneris Payment app via the setResult method with response data in the intent, except for TRANSACTION_RESULTS hooks

For TRANSACTION_RESULTS integration, the communication happens over explicit broadcast, for which, the third-party app would receive the data via BroadcastReceiver.

The Moneris Payment application doesn't expect a response.

Sample Code