Test your integration

You have built your handler and enrichment code and want to test it before production. There is no sandbox processor account yet, so this page covers what works today and how to test safely without one.

Test your webhook handler with a mock payload

Send a sample dispute.created payload to your own endpoint. The full payload shape for each event is in Webhook events.

curl -X POST http://localhost:3000/webhooks/dispute-created \
  -H "Content-Type: application/json" \
  -d '{
    "type": "dispute.created",
    "data": {
      "id": "66e6ea9ecd94925a9f8060d9",
      "source": "stripe",
      "source_id": "du_123456789",
      "reason": "fraud",
      "amount": 100,
      "currency": "USD",
      "status": "needs_response",
      "stage": "Chargeback"
    }
  }'

You should see your handler reply 200 and store the ID mapping row. If your handler verifies the X-Chargeflow-Hmac-Sha256 signature, compute it over the mock body with your key, or bypass verification in your local environment only. See Webhooks.

Test enrichment on your live account

Keys act on your live account, so test with real disputes, carefully:

• Reads have no side effects. List disputes and fetch them with expand freely.
• Enrichment does not trigger immediate action. Disputes have a response window (due_by), and sending data with PATCH or uploading evidence adds to the case without submitting it on the spot. Pick a dispute that is still open, enrich it, and check the result with a GET.
• Start small. Enrich a handful of disputes and review them before you turn the integration on for every dispute. See the Go-live checklist.

Get testing support

Email support@chargeflow.io with what you are testing and the requestId from any failing response. The team can review your first enriched disputes with you. See Support.

Next step