Payment Provider Setup & Webhook Guide - Help Center

While the general concept of connecting a payment provider remains the same, the exact steps differ depending on which platform you use to process payments.

In this guide, we provide a high-level overview of the most common setup flows. For detailed, step-by-step instructions with screenshots, please navigate to the specific provider in the Integrations section of this Help Center.

Standard Setup Process

Regardless of your provider, the setup generally follows this pattern:

1. Generating an API Key

Most integrations require an API Key so we can verify transaction details.

Go to your provider's Developer or API settings.
Create a new API Key with Read-Only access.
Paste this key into the Integrations tab of your Discover Mac Apps dashboard.

2. Creating a Webhook Endpoint

Webhooks are how your provider tells us a sale has occurred in real-time.

In your Discover Mac Apps dashboard, you will see a unique webhook URL generated for your program (e.g., https://discovermacapps.com/api/affiliate/webhooks/stripe).
Copy this URL.
Go to your provider's Webhook settings and click "Add Endpoint".
Paste the URL.

3. Selecting Events

You do not need to send us every single event that happens in your store. We typically only need to listen for successful payments.

When configuring the webhook, select events like checkout.session.completed, charge.succeeded, or order_created.
(See your specific provider's integration guide for the exact event names).

4. Saving the Webhook Secret

To ensure hackers cannot send fake sales data to your webhook, your provider will generate a "Webhook Secret" or "Signing Secret".

Copy this secret from your provider.
Paste it into your Discover Mac Apps dashboard.
This allows us to cryptographically verify that every incoming webhook is authentic.

Troubleshooting Common Webhook Issues

If commissions aren't showing up after a test transaction, check the following:

Did the webhook fire? Check your payment provider's webhook logs. Look for a 200 OK response. If it failed with a 4xx or 5xx error, there is a configuration issue.
Is the secret correct? If the Webhook Secret you pasted in Discover Mac Apps doesn't perfectly match the one in your provider, we will reject the webhook for security reasons (returning a 401 Unauthorized).
Was an affiliate cookie present? If you are testing, make sure you actually clicked an affiliate link before checking out, otherwise there is no affiliate to attribute the sale to!

[!TIP] Always perform a test transaction (using test mode or a 100% discount code) after setting up your integration to ensure end-to-end attribution is working perfectly.