Example apps

Keep the order API key and OAuth client credentials out of the browser. Each order creates one hosted checkout with a stable idempotency key, so retrying the same request returns the same checkout.

The payer comes back through a private, unguessable link. The pending, confirming, succeeded, failed, canceled, and support pages all read the original payment; a browser return never fulfills the order or shows internal IDs.

Check the signature over the raw webhook body and delivery ID. Store the event ID, object version, and pending work before you acknowledge the event, and expect redelivery and secret rotation.

Read the payment again from your server and check that the order, amount, currency, environment, and succeeded status all match. A temporary failure keeps the event pending for a retry; a mismatch is investigated, never fulfilled.

The Node server exchanges your credentials and keeps the one-time signing secret in local storage that only it can read. The browser gets only a short-lived checkout secret tied to your site's origin.

The page loads PerionPayments.js at a fixed version with its SHA-384 integrity value. The browser's completion event updates the page, but never fulfills the order or starts a new checkout.

After the sandbox approval, the server verifies the signed event, reads the payment again and checks the amount, and fulfills the order once. Only then does the single refund button become available.

A private link keeps the order after a reload or a return from the provider. If creating the checkout has an unknown outcome, the Integration lab keeps the original attempt for you to check instead of creating a new payment.