Orchestration settings control the single orchestration record attached to your account - the default payment gateway, the return URLs used after checkout, the notification URLs used for transaction and payment link webhooks, and the transaction signing key. There is only one orchestration record per account; new records aren't created from the dashboard, only edited.
Switching to the Perno Orchestration context
- Click the Context switcher in the top navigation bar.
- Select Perno Orchestration from the list.
The dashboard now shows live data for the Perno Orchestration context.
Opening Orchestration settings
- Click Perno Orchestration in the left sidebar.
The Orchestration settings page shows the Record panel on the right, confirming the account's Orchestration ID and when the record was created.
Configuring orchestration settings
- Fill in the orchestration settings fields:
| Field | Description |
|---|---|
| Default Payment Gateway | The gateway orchestration uses by default: Stripe, Autopay, PayU. |
| Default Return URL | Where customers land after checkout when no more specific return URL applies. |
| Success Return URL | Where customers land after a successful payment. |
| Cancel Return URL | Where customers land if they cancel payment. |
| Transaction Notification URL | The webhook URL that receives transaction status updates. |
| Payment Link Notification URL | The webhook URL that receives payment link-related notifications. |
| Transaction Signing Key | The secret used to sign payment transaction data. It is not your API authentication token. |
| Send multiple webhooks | A checkbox that controls whether multiple webhook notifications are sent per event. |
How the Transaction Signing Key is used
The Transaction Signing Key is a secret used to sign transactions and payment links - it's not used to authenticate API requests. When you create a transaction or payment link through the API, you build a trx_hash with this key:
trx_hash = SHA256("|" + amount + "|" + trx_id + "|" + transaction_signing_key)
The Perno API recalculates the same hash and checks it matches. If it doesn't, the request is rejected with a Wrong hash error.
Transaction Signing Key vs. API Token
| Credential | Purpose |
|---|---|
| API Token | Authenticates you as a user. Sent as Authorization: Token YOUR_API_TOKEN. |
| Transaction Signing Key | Used only to build the trx_hash. Never sent in the request itself. |
Most endpoints only need the API Token. Creating a payment link also needs a valid trx_hash, built with the Transaction Signing Key.
Saving settings
The Cancel and Save Settings buttons stay accessible near the top of the page as you scroll through the fields. Click Save Settings to apply the changes, or Cancel to discard them.
