There are multiple ways to programmatically integrate Chargeblast. This guide is intended for resellers, SaaS tools, payment aggregators, and other merchant of merchant businesses. If you are a merchant yourself, please see our webhooks, which should be sufficient for most use cases. If you are using only payment processors that are supported via our integration directory, you can integrate directly via our integrations page and use our workflow builder to set up refund rules—including branching for Ethoca / CDRN (issuer) alerts and, where supported (for example Stripe), EFW (early fraud warning) rules for auto-refunding or filtering low-ASP transactions. See Stripe integration for more on EFW rules. The integration path depends on whether you’d like to use our matching algorithm, or handle alert to transaction matching yourself.Documentation Index
Fetch the complete documentation index at: https://docs.chargeblast.com/llms.txt
Use this file to discover all available pages before exploring further.
Step 1. Handling of the alerts
Client-side matching
- Implement webhook to receive alert
- Perform alert to transaction matching internally, refunding cardholder if desired and then update the alert via the /update/alert endpoint
Chargeblast matching
- Implement
/orders/uploadendpoint to push order data to Chargeblast- Optionally, if using PSPs we support, integrate account via our integrations directory.
- Expose your-domain.com/chargeblast/refund endpoint to Chargeblast to implement refunds & subscription cancellations
Step 2. Passing down costs to merchant
- Poll
/alertsendpoint (or receive alerts via webhook) and associate each alert with a merchant in our system. - Bill your merchant accordingly