Use Hoko with Stripe

Stripe attribution currently supports a manual signed-webhook recipe in test mode. The Apps card opens this guide; it does not create a Stripe connection or accept provider credentials. Hoko accepts payment and refund events and attributes a payment only when the event contains valid Hoko click metadata and consent. Live-mode payments are not supported by this path.

Before you start

  • Use your Stripe test account's test key and webhook signing secret.
  • Run a customer-owned HTTPS webhook runner that keeps those credentials private.
  • Keep the test configuration separate from your normal profile.
  • Use Stripe test cards. Do not use live mode.

Send test events

  1. Open the Stripe guide from Dashboard → Integrations → Apps. In your customer-owned HTTPS webhook runner, configure your Stripe test key and signing secret; do not enter them in Hoko's Apps page.
  2. Configure the runner to verify Stripe's signature and forward the signed test events to the Hoko callback.
  3. Create a test payment with hoko_click_id, hoko_consent=granted, and a recent hoko_click_at.
  4. Create a partial test refund.
  5. Inspect the payment and refund in Hoko.

Verify the result

Confirm livemode=false, the payment identity, exact money, and the click attribution. A payment without valid click metadata stays unattributed. This path does not provide Stripe Connect or live payment support.

Troubleshoot and clean up

A signature error means the raw body, secret, or timestamp is wrong. An account or mode mismatch means the connection does not match the event. Delete test customers and endpoints, then remove local credentials.

Open Apps · Technical reference · All app guides