n-GoCardless's API Sets Up the Mandate. Here's What Still Has to React When a Payment Lands.
GoCardless's documented API lets you create mandates, trigger payments against them, and receive webhook events for things like a payment confirming, a payment failing, or a mandate getting canceled. Alongside standing direct debit mandates, GoCardless also offers a faster, one-off payment option built on open banking for when you don't want to wait on a mandate to be set up first. We don't set up your GoCardless account. We build what your other systems do the moment one of those API events actually fires.
What building on GoCardless's API actually involves
A mandate is the authorization a customer gives once, letting you collect direct debit payments from their account going forward. The API handles creating that mandate, then creating payments against it on whatever schedule your business needs, one-off or recurring.
GoCardless has a sandbox environment for testing this before any real bank account is involved, and a developer API reference documenting the endpoints and webhook event types. Beyond standing mandates, it also offers an open-banking-based payment option for collecting a single payment quickly without first setting up a recurring mandate, useful for a first payment or a one-time collection where speed matters more than building a standing authorization.
Webhooks are where the real integration work tends to concentrate: a payment confirming, failing, or getting charged back, or a mandate getting created, canceled, or failing to be set up, each fires an event, and whether anything useful happens with that event is entirely up to what's built to receive it.
What We Build on GoCardless's API
Payment and mandate events that update your own records automatically
We build the webhook receiver that takes a confirmed payment, a failed payment, or a canceled mandate from GoCardless and reflects it in your CRM or accounting system right away, instead of someone checking the GoCardless dashboard to see what actually went through.
Reconciliation that matches a payout to the right invoice automatically
For a business running GoCardless alongside Salesforce or an accounting system, we build the match between a GoCardless payout and the specific invoices it covers, so reconciling who's paid stops being a manual line-by-line check.
Collecting payments through GoCardless and still reacting to events manually?
Tell us which GoCardless events, confirmed payments, failures, canceled mandates, you're not acting on automatically yet.
Building on GoCardless's API and still checking the dashboard by hand for what happened?
A mandate or payment event firing correctly only matters if something downstream actually reacts to it. GoCardless is just this page's example; n-frames builds the same kind of event-driven automation for whatever API your business already has running.
Let's talk