Skip to content
Moviie

Integrations and migration

How to connect a checkout and configure sales postbacks

Create a sales integration, install its URL in your checkout, preserve attribution, and validate the first postback.

Updated on October 23, 20265 min read

Connect your checkout so that each confirmed purchase can return to Moviie and be matched to the video involved in the sale. The integration uses a unique URL and, when required by the platform, a signature secret.

Before you begin

You need access to the checkout's webhook or postback settings. Also confirm that your video CTA points to the payment page used by this integration.

When an integration is active, Moviie adds an attribution key to a compatible checkout URL. It does not overwrite a value that is already present in the same parameter.

Create the integration

  1. Open Sales in Moviie's main navigation.
  2. Select New integration. If this is your first one, you can also select Start setup.
  3. Under Choose the platform, select your checkout. Use Generic webhook, Zapier, Make, or n8n when you need to define the event contract.
  4. Enter a name that identifies the product or operation, such as “Main product.”
  5. Keep the suggested Attribution parameter. Change it only when the checkout setup requires a different field.
  6. Enter the requested secret, such as a Hottok or Secret Key, when the field appears.
  7. Select Create integration and wait for test.

Moviie generates the unique URL after creation.

Configure the postback in your checkout

Copy the Postback URL from the integration card. Then:

  1. Open the platform's webhooks, notifications, or postbacks area.
  2. Create a configuration and paste the Moviie URL.
  3. Select approved purchase and renewal. Include refund and chargeback when the platform offers those events.
  4. Preserve Moviie's attribution parameter on the way to checkout.
  5. Save the configuration.

The Connect checkout screen provides platform-specific instructions and links to the official documentation when a guide is available.

Run both tests

Select Test on the integration card. This confirms that the internal URL receives the event and validates Moviie's signature. The test remains visible in health but never counts toward the funnel or revenue.

Next, send a test from the checkout itself. This second test validates the external path, including the URL, secret, and selected events. If the platform has no test action, use a controlled transaction and confirm the result before considering the integration ready.

Confirm the first attributed sale

  1. Open Health on the integration card.
  2. Confirm that the delivery is Processed.
  3. Return to Sales and check Attribution found.
  4. Open Funnel by video to find the sale and revenue in the correct period.

A purchase enters the funnel only after approval, within the 30-day window, and with an attribution key from a valid session.

Use any payment platform

When Other platform is available for your account, your server or automation can send JSON without a gateway-specific integration. Existing integrations retain their earlier mapping until an explicit configuration change.

Choose Default format to send order_id, event_type, amount_cents and currency. All four are required. Amounts are integers in minor units and currencies must be supported. The starter example includes test: true: keep this marker during testing to avoid recording revenue.

Choose My own payload to reuse your JSON. Load a synthetic sample and enter paths such as sale.id and sale.amount. Currency and event can use a path or an explicit fixed value. Select the amount unit and translate your system's event values. Unknown values never automatically mean approved payment. Use a fixed approved-purchase event only when every notification sent represents a confirmed payment.

Paste a sample or send it to a temporary capture URL, valid for ten minutes and one capture. The sample expires after 24 hours. Samples and previews never create sales. Review the preview and publish the configuration. Copy the sales notification URL and configure server-side POST requests with JSON. Treat the URL as a credential and keep it out of public website code.

Include conversion_key in default format or map the session key in your payload. Without it, a valid sale can remain unattributed to the VSL. For embedded payments, web code can obtain the key from the relevant player instance with getConversionKey() and pass it to the server with the order. Do not block payment if the key is unavailable.

Event time, test marker, email and items are optional. If event time is absent, receipt time is used; an explicitly supplied invalid date must be corrected. Select the date format explicitly in mapped mode. See the technical integration guide for fields, currencies and limits.

Refunds and chargebacks

Send the cumulative refunded or disputed amount for the same order. If refunded value rises from 30 to 50, send 50, not the additional 20. Combined refunds and chargebacks cannot exceed the purchase. A reversal received before its purchase waits for that purchase and inherits its attribution.

Pause, rotate, or remove the integration

  • Pause keeps the setup, but new deliveries are ignored until reactivation.
  • Rotate URL creates a new address. The previous URL remains accepted for 48 hours so you can update the checkout without interrupting collection.
  • Remove stops new deliveries. Existing sales and postbacks remain in history.

Do not publish the unique URL or share the signature secret.

Keep learning

Keep going

Guides that help with the next step.

HUMAN SUPPORT

Still need help?

Tell us what is happening. Our team will help you find the next step.