ImaCash integration

Epos Now · EposNowV2

Distinguish the EposNowV2 webhook flow from the direct API profile. Confirm preparation, private access and availability with support.

Epos Now logo for the EposNowV2 profile
Hospitality

EposNowV2: confirm preparation

This profile uses an intermediary service and Epos Now webhooks. It does not automatically replace EposNow or correspond to the file-based EposNowV3 profile. Setup requires a technical review and supervised test; this page does not establish commercial availability or physical validation.

Provider preparation

The administrator must confirm the receiving service, permissions, authentication and event delivery before configuring ImaCash. BaseURL, AuthenticationKey and AuthenticationSecret are private settings supplied and verified by the service administrator; there are no universal values to copy from a guide. Keep screenshots of these settings private.

ImaCash fields

Under Configuration > Integration, POS > EposNowV2, Database name takes the complete private base URL of the intermediary service, not a SQL database or the final webhook path. EposNOW token takes the private Epos Now token. Confirm both with support before saving on exit; do not use credentials from another profile.

Verify the complete flow

Saving or a connected indicator does not prove event delivery, terminal mapping, payment methods or the cash outcome. Confirm scope and conditions with support before enabling it. If the outcome is uncertain, check both systems and actual cash before repeating, resynchronising or restarting.

See the EposNow API profile

Integration ready to move forward

If this integration matches your software, the next step is moving into real operation

We can help you validate the scope, confirm compatible hardware and prepare the next implementation step.