> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/guides/feature-guides/billing-setup/guide-setting-up-gocardless-in-zuora.md).

# Setting up GoCardless in Zuora

To set up GoCardless payment gateways in Zuora, refer to Zuora's Knowledge Center article available at:<https://knowledgecenter.zuora.com/Billing/Billing_and_Payments/M_Payment_Gateways/Supported_Payment_Gateways/GoCardless_Gateway>

For additional insights beyond Zuora's documentation, PeakCommerce offers the following guidance:

1. To configure the GoCardless payment gateway in Zuora, you'll need an OAuth token. If you haven't set up an OAuth token yet, follow these steps:
   * Navigate to your username in the top right corner of Zuora and select Payments > Gateway Authentication.
   * Click "Create Authentication."
   * Provide a name, select GoCardless as the type, and choose "Use Gateway Test Environment" if it's for the Sandbox.
   * Upon saving, you'll be redirected to the GoCardless Merchant account login page. Log in to authenticate the token.
2. When testing bank transfers with a GoCardless gateway (not a test gateway), ensure specific requirements are met. Mandatory fields vary based on the payment method/country, and only GoCardless test bank numbers are valid. Ensure GoCardless-required fields are marked accordingly in the corresponding Hosted Page's settings to avoid payment processing issues.
   * For Direct Debit UK:
     * Account Number
     * Account Name
     * Bank/Branch Code
     * First Name
     * Last Name
     * Email
   * For SEPA:
     * Account Number (IBAN)
     * Account Name
     * First Name
     * Last Name
     * Email
     * (Country recommended but not required)
   * For ACH:
     * Routing Number
     * Account Number
     * Bank Name
     * Account Name
     * Account Type
     * Country
     * State
     * City
     * Postal Code
     * Street Address
     * Email
   * For PAD:
     * Account Number
     * Account Name
     * Branch Code
     * Bank Code
     * First Name
     * Last Name
     * Email
3. GoCardless offers basic test bank details, accessible at: <https://developer.gocardless.com/getting-started/developer-tools/test-bank-details>. Further information on required fields and test bank details per country can be found in the appendix: <https://developer.gocardless.com/api-reference/2015-07-06/#appendix-local-bank-details>.
4. Certain payment method types are exclusively available when GoCardless is set as the Default Payment Gateway on a Zuora account. For instance, PAD. You won't be able to add a PAD payment method directly in Zuora or via PeakCommerce unless GoCardless is the Default Payment Gateway on the account.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/guides/feature-guides/billing-setup/guide-setting-up-gocardless-in-zuora.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
