What moves, and which way
Integrations run in both directions. What follows is what this connection is for.
En Garde to Openpay
- Nothing is written back to your processor. Payment connections are read-only in practice.
Openpay to En Garde
- Charges, refunds, payouts, currency, and the customer or payer records the processor exposes.
Connecting it
You generate a key in the platform and paste it into En Garde. The key is tested against the live API before it is stored, so a wrong or under-scoped key fails at setup rather than silently later.
- Generate an API key in the platform, with the permissions its documentation lists for third-party access.
- Open Integrations in your Brand Space and find the platform on the Integrations tab.
- Click Connect. Paste the key into the API key field — the eye toggle reveals what you pasted so you can check it.
- Click Test Connection. En Garde calls the platform with the key and reports whether it worked.
- Save. The Save button will not store an untested key, so a failing test has to be fixed first.