GoPay

Payment gateway integration for GoPay — API docs: https://doc.gopay.com

Connection: Client ID, Client Secret and GoID from GoPay administration → API access, plus the environment those credentials belong to.

Sandbox and production are separate worlds. gate.gopay.cz and gw.sandbox.gopay.com don't share credentials or GoIDs, so a mismatch fails every call at authentication. That's why the environment lives on the connection rather than being a per-action toggle.

Actions

Create Payment, Get Payment Status, Refund Payment.

Create Payment returns the payment object including gw_url — the gateway link to send the customer to. The connection's GoID is filled in as the payment target automatically, so a flow never carries it.

Amounts are integers in the smallest unit

10000 means 100.00 CZK. Sending 100 charges one koruna. This is the easiest way to charge a customer 1/100th of what you meant, so both amount fields say so explicitly.

No triggers

GoPay notifies per payment via the notification_url you supply when creating it — a per-payment callback, not a subscription an onEnable/onDisable pair could register and tear down. Point that URL at a TaskMagic webhook trigger to have a flow react to the outcome; the Create Payment field description says so.

Auth note

The token endpoint is form-encoded (grant_type=client_credentials&scope=payment-all) with HTTP Basic over clientId:clientSecret. Sending JSON there returns a credentials error that reads like a wrong key. Tokens are cached per credential set and keyed by environment plus a digest of the secret, so a rotated secret or an environment switch can't reuse the wrong token.