Merchant Configuration Docs

Auto-generated navigation index. To regenerate: acd index

Start Here: Find Your SKU

Use this page to find the SKU that matches your gateway and business use case. If you already know the SKU, jump straight to the generated SKU page. If you are new to the model, start with the SKU Naming Convention and then use the gateway and product pages for the specific implementation.

Current direction: Microservice-based integrations are the preferred target state. SPF variants remain documented for backward compatibility, reference, and transition planning, and are clearly marked as legacy/transitioning.

Industry Adyen MPGS Elavon Freedompay
FNB — Food & Beverage (Infrasys Complex) FNB-ALL-0001-A-110000 (SPF) FNB-ALL-0006-A-110000 (SPF) ~~FNB-ALL-0002-A-110000~~ SPF, deprecated
C2C — C2C Ecommerce C2C-ALL-0006-A-010010 (SPF) C2C-US-1003-B-010010 (MS)
C2C-US-1003-A-010010 (MS)

Not seeing your gateway? It may not yet have schema coverage. Check Coverage Matrix for generation status.

Customer / Property Deployment Catalog

Author required (Class C). This section maps customer/partner names (e.g. Alliants, Asiapay) to their assigned SKU and environment. Populate data/deployments.yaml to generate this table automatically.

Template: yaml deployments: - customer: Alliants property_type: LOD gateway: mpgs sku: LOD-EU-0006-A-100000 # replace with real SKU region: EMEA notes: "European lodging properties"

Gateway Documentation

Gateway Catalog Capabilities
Adyen Adyen Catalog Capabilities
MPGS MPGS Catalog Capabilities
Elavon Elavon Catalog Capabilities
Freedompay Not yet published Not yet published

Reference

Page Description
SKU Naming Convention Start here to decode the SKU that drives the schema and gateway selecti