Prerequisite

The operator (CPO/site owner) who intends to support ad-hoc payments via eMabler must contact a PTP provider (for example, Payter) to establish a merchant account and obtain payment terminal hardware.

1. With Payter, the merchant must complete a business onboarding process: select acquiring bank/gateway, provide company documentation, obtain a Merchant ID (MID) and linking to an acquirer.

2. Payter emphasises that the terminal must have a MID and the acquirer must have vetted the merchant.

3. The merchant/DPO should account for boarding time: the application step should be completed at least two weeks in advance of critical deadlines, as the acquirer onboarding (“boarding”) process can take time.

Test Terminal & Staging Environment (optional but recommended)

• While the merchant account and terminal product activation are in progress, the operator may request a test terminal to validate integration in non-production environments (eMabler test environment + Payter staging environment).

• This allows end-to-end testing of the workflow

Important: This test terminal is not yet mapped to a live site/connector in eMabler; it is purely for validation. Although a live charger can be moved to eMabler test enviornment for testing purpose.

Production-Ready Terminal Mapping

1. Only once the merchant account is fully approved and the terminal hardware is in production mode (i.e., live MID, activated in Payter’s production environment— “MyPayter Live”) may the terminal be mapped to a live charging site in eMabler.

2. With Payter for example:

   • The terminal serial number (hardware ID) must be registered/activated in MyPayter.

   • The operator must enter terminal details, currency, MCC (Merchant Category Code) for global use.

   • Once the terminal is in production, in eMabler, the terminal serial/hardware ID is linked to a location/Charger, and OCPI direct payment flows can commence (e.g. payment terminal authorisation → remote start → session data → CDRs → settlement)

3. Therefore, a transition from test environment to production environment is required; premature mapping to a live site before acquirer/merchant/terminal activation may result in failed authorizations or unsupported processing.