Skip to content
Connection Guide

Connect Shift4 Without Breaking the Audit Trail

Use this guide to connect Shift4 or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryFinance
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Shift4 and make sure the first collection lands cleanly.

  1. 1
    Register Aurora as a Shift4 interface and capture the approved InterfaceName, InterfaceVersion, CompanyName, and optional Client GUID values.
  2. 2
    Supply a dedicated AccessToken for steady-state reads, or a one-time Auth Token plus Client GUID if Aurora is responsible for the documented bootstrap exchange.
  3. 3
    Keep this integration scoped to the documented merchant information surface until vendor confirmation exists for additional read-only endpoints.
  4. 4
    Validate merchant information retrieval before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

access_tokenauth_token

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.