generated: '2026-07-19'
method: searched
source: https://developer.north.com/
docs:
- https://developer.north.com/supplemental-resources/epx-data-dictionary/transaction-request-fields
- https://developer.north.com/blog/tutorial-nodejs-browser-post-custom-pay-api
- https://developer.north.com/products/online/epx-hosted-checkout/integration-guide
summary:
  types:
  - apiKey
  notes: >-
    EPX uses proprietary merchant-credential auth rather than OAuth 2.0. Two
    documented models exist depending on the integration surface. There is no
    OAuth authorization server, OIDC discovery, or scope surface, so no
    scopes/ artifact is produced.
schemes:
- name: FourPartKey
  type: apiKey
  in: body
  description: >-
    Legacy four-part processing key that identifies the merchant on Browser
    Post API and Hosted Pay Page transaction requests. Composed of four
    numeric fields sent with each transaction.
  fields:
  - CUST_NBR
  - MERCH_NBR
  - DBA_NBR
  - TERMINAL_NBR
  used_by:
  - Browser Post API
  - Hosted Pay Page
  - Hosted Checkout
  source: https://developer.north.com/supplemental-resources/epx-data-dictionary/transaction-request-fields
- name: EPISignature
  type: apiKey
  in: header
  description: >-
    HMAC-style request signing for the North EPX Custom Pay REST API. The
    caller sends an identity header plus a computed signature over the request,
    provisioned by the North integrations team. Signature computation is
    documented in the "How To Authenticate" section of the Custom Pay API
    Integration Guide.
  headers:
  - EPI-Id
  - EPI-Signature
  - EPI-Trace
  used_by:
  - North EPX Custom Pay REST API
  source: https://developer.north.com/blog/tutorial-nodejs-browser-post-custom-pay-api
tokenization:
  name: BRIC
  description: >-
    Every transaction returns a unique BRIC token that represents the stored
    payment credential, so cardholder data is never handled by the merchant on
    subsequent operations (e.g. refund/{BRIC}).