Every money-moving API call is checked against your business's processing status before it reaches the processor.

What it checks POST /v1/charges, POST /v1/charges/{id}/capture, POST /v1/refunds and the subscription, invoice and arrangement paths that create charges verify that the business behind your API key is onboarded and enabled for processing. The check is the same for every processor.

When processing is disabled

• Onboarding is not complete.
• An administrator deactivated the business for risk or compliance reasons.
• The business paused processing.

The error

{
  "error": {
    "type": "invalid_request_error",
    "code": "processing_disabled",
    "message": "Processing is not enabled for this merchant. Contact support or complete onboarding."
  }
}

HTTP 403. A business that never finished onboarding gets 403 with code: "merchant_not_onboarded" instead.

Refunds on a business that was moved to another processor remain allowed, so a charge made on the old processor can still be refunded there.

No action is needed on your side; if you receive this error unexpectedly, contact support at info@hlhunt.org.