Stripe automatic troubleshooting

Use this guide for a product configured with Stripe automatic. First check the product’s Stripe state, the deployment mode and the selected Payment Link. For the complete prerequisites, see Stripe automatic payments.

The product says no Stripe account is connected

Open the product editor and select Stripe automatic, then Connect Stripe. Authorize the Stripe Standard account that owns the Payment Link.

If the account is already connected to another product, select the same account only when it is in the deployment’s configured mode. Development uses Stripe test; production uses Stripe live. A test product cannot use a live Payment Link, and a live product cannot use test data.

If Connect Stripe does not complete, try again from the product editor and confirm that the Stripe account authorization is still valid. Do not paste a secret key or OAuth token into a support request.

The Payment Link is missing or unavailable

AffiHQ lists the account’s Payment Links, but only a supported active link can be selected. Check the link in Stripe:

• it is hosted at https://buy.stripe.com/...;
• it contains exactly one fixed-price line item;
• the quantity is 1 and the amount is positive;
• the line uses one currency;
• it is either one-time or a subscription;
• a subscription uses a monthly or annual interval;
• it belongs to the same Test mode or Live mode as the connected account.

Inactive links and links with unsupported pricing, quantity, cadence or URL stay unavailable. If the chooser has more results, use Load more before concluding that the link is absent.

The product is connected but not ready

A connected account is not enough. The product must also have one selected Payment Link. In the product editor, choose a compatible link and select Use this Payment Link. Confirm that its amount, currency and cadence are the values you intend to sell.

If the selected link was deactivated or changed in Stripe, select another supported link and choose Use this Payment Link. A product uses one Payment Link at a time.

A payment is not credited

Native payments are credited only when AffiHQ can match the payment to all of the following:

• the connected Stripe Standard account;
• the product’s selected Payment Link and its saved amount/currency/cadence snapshot;
• an AffiHQ /r/ click;
• the customer and the product’s affiliate attribution.

Recheck that the customer used the generated affiliate /r/ link and that the link opened the selected Payment Link. Confirm that the product was not switched to API/SDK advanced and that the deployment is using the same Test or Live mode as Stripe.

Payments that cannot be matched are not credited automatically. Correct the link, product or account configuration, then use API/SDK advanced when your customer journey needs custom pre-Checkout attribution or another flow.

The Stripe account was revoked or disconnected

If the product says Reconnect Stripe, or automatic payments are paused, the connected application no longer has usable access. Reconnect the same Standard account in the expected mode, then select and save a supported Payment Link again.

Removing the connected application from Stripe stops native processing. Switching the product to API/SDK advanced is not the same action: it leaves the Stripe account connected and only changes this product’s payment path.

A payment is still processing asynchronously

An immediate payment can create a commission when Checkout succeeds. For an asynchronous payment method, Checkout may establish the click and attribution first; the commission is created only when Stripe reports asynchronous payment success. An asynchronous failure does not create a commission.

For subscriptions, the Checkout locks the subscription attribution and each successful invoice.paid creates a recurring payment. The selected link’s monthly or annual cadence controls the recurring period. An unpaid or failed invoice is not a successful payment.

A refund or dispute did not change the commission

AffiHQ applies only a successful refund status. A pending, action-required, failed or canceled refund does not correct financials yet.

Partial and repeated refunds are cumulative, with a deterministic tax allocation and a cap at the original payment amount. An open dispute can reserve or correct the related amount at most once. A won dispute resolves without another correction; a lost dispute applies the correction, and the terminal result is applied once.

The correction may first affect a commission in validation or reduce what is ready for payout. If the original commission was already paid, AffiHQ records the resulting negative balance for future commissions; it does not pull money from the affiliate automatically.

The affiliate link opened the historical site instead

When native Stripe state is invalid or unavailable, /r/ safely uses the product’s historical destination with affihq_ref. That fallback keeps the click reference available, but it does not create a Stripe-native payment automatically.

Your server must follow the API/SDK advanced flow: capture affihq_ref, create the attribution before or during your customer journey, and report verified payments. If you do not want that fallback path, restore a connected account and a supported selected Payment Link before sending traffic.

What to send support

Provide only non-secret context:

• product name;
• whether the deployment is Test or Live;
• Stripe account display name, if available;
• Payment Link URL;
• amount, currency and one-time/monthly/annual cadence;
• the affiliate /r/ URL and the approximate time with timezone;
• the visible product state or error message;
• a non-sensitive Stripe Checkout, invoice, refund or dispute reference if support asks for one.

Never send API keys, fingerprint keys, OAuth tokens, webhook signing secrets, card data, customer email addresses or complete provider payloads. The integration overview explains which path to use when the native path does not fit.