Failed Payments API Endpoint

When a recurring payment fails in your billing system, notify Churn Buster to start a recovery campaign.

Two-step setup

1. Add a trigger in your in-house logic, or subscribe to a webhook from your payment processor or subscription management tool, that fires when a recurring payment fails. Skip one-off payments; Churn Buster doesn't need those.
2. When the trigger fires, send this request:

curl -X "POST" "https://api.churnbuster.io/v1/failed_payments" \
    -H "Content-Type: application/json" \
    -u "ACCOUNT_ID:API_KEY" \
    -d '{
  "payment": {
    "source": "in_house",
    "source_id": "ch_abc123",
    "amount_in_cents": 2900,
    "currency": "USD",
    "properties": {
      "error_code": "insufficient_funds",
      "error_message": "Your card does not have sufficient funds"
    }
  },
  "subscription": {
    "source": "in_house",
    "source_id": "sub_abc123",
    "properties": {
      "product_name": "productA"
    }
  },
  "customer": {
    "source": "in_house",
    "source_id": "cus_abc123",
    "email": "sarah@example.com",
    "properties": {
      "first_name": "Sarah",
      "last_name": "Doe",
      "phone_number": "+1111111111",
      "country_code": "US"
    }
  }
}'

Verify your requests

• Test mode: view requests in the test debugger.
• Live mode: view recent requests in the live debugger.

About source and source_id

• source: set it to "in_house", or another consistent name that identifies your subscription management system. Use the same value in every request.
• source_id: the record's ID in your system. Use unique IDs for each customer, subscription, payment method, and payment.