> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/admin-overview/link-payment-processor.md).

# How to Link a Payment Processor (Stripe/GoCardless)

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, or **Support**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Processor Account**: You need an active Stripe or GoCardless account.
  * **Stripe**: Sign up at stripe.com. When setting up, choose "integrated by another platform" and enter Peoplevine.
  * **GoCardless**: Sign up at gocardless.com. Your account must be a **Pro account** to leverage the full white-labelled experience.

### Instructions

1. In the Control Panel, navigate to [**Settings > Payment Processors**](https://control.peoplevine.com/admin_processors.aspx).
2. Click **Register a Payment Processor**.
3. Select the processor type: **Stripe** or **GoCardless**.
4. Enter your API credentials:
   * **Stripe**: Paste your **Publishable Key** and **Secret Key** from the Stripe Dashboard.
   * **GoCardless**: In your GoCardless account, go to the **Developers** tab, click **Create**, then **Access Token**. Enter "Peoplevine" as the name and choose **Read-write access**. Paste the token into Peoplevine.
5. Set the processor as **Default** if it should handle all standard charges.
6. Click **Save**.

**Multiple Processors**: Peoplevine allows you to use multiple payment processors by assigning a processor to a specific area of your business. When staff process a payment, they see a radio button selector ("Activate a Payment Processor") with these options:

| Slot                                         | What It Handles                                                                                     |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Default Payment Provider**                 | Required. All payments unless a more specific slot is assigned                                      |
| **Membership Billing**                       | Subscriptions, renewals, and membership dues billing                                                |
| **Virtual POS + 3rd Party POS Integrations** | Third-party POS integrations (Toast, Micros, Lightspeed) and the Control Panel's Virtual POS screen |
| **3rd Party PMS Integrations**               | Property management charges (Opera, Mews)                                                           |
| **3rd Party Spa/Activity Integrations**      | Spa integration charges (Book4Time)                                                                 |
| **Additional Payment Provider**              | Backup processor — captures additional payment methods and acts as fallback                         |

> **Note**: When processing house account payments, payments not designated for POS, PMS, or Spa are routed according to the **House Account Routing** setting — either to the Default Processor or the Membership Billing Processor. See: [How to Configure House Account Billing](/products/control-panel-overview/admin-overview/configure-house-account-billing.md).

> **Payment method assignment**: When staff add a payment method to a CRM profile, the "Use For" selector assigns the card to one of these processor categories. This only applies in staff-side and automated flows — Member Portal checkout shows all saved cards regardless. See: [How to Update a Member's Payment Method](/products/control-panel-overview/charging-payments-overview/update-member-payment-method.md).

> **Pre-selection behavior**: When staff charge through Virtual POS, the system pre-selects the POS processor, but staff can switch to any other processor on the payment screen.

> **Force Payment**: When checked on a processor, all payments in that slot are routed to that single processor regardless of other assignments. Only check this if you want to redirect all payments in a category to one processor (e.g., "all dues to GoCardless" or "all F\&B to Stripe"). Supported on POS, PMS, and Spa slots — not on Default.

**Transaction Resync**: If transactions show different statuses between Peoplevine and your payment processor (e.g., declined in Stripe but processed in PV), you can resync to correct the records.

**GoCardless Sync Options**: After connecting GoCardless, you can manage transaction syncing from the processor edit page. The sync options are:

| Option                             | What It Does                                                                                        |
| ---------------------------------- | --------------------------------------------------------------------------------------------------- |
| **CRM Profiles + Payment Methods** | Syncs customer data and stored payment methods (default)                                            |
| **Re-sync Transactions**           | Re-syncs transaction statuses for a specified date range — use when transactions appear out of sync |

**Stripe Resync**: Stripe transactions can also be resynced when payment status is out of sync between Peoplevine and Stripe.

> **GoCardless Currency**: GoCardless payments default to the company currency configured in your Peoplevine settings. Ensure your company currency is set correctly under **Settings > Company** before processing GoCardless payments.

### What Happens Next

* **On the billing side**: The platform can now process charges. Membership enrollment, subscription renewals, and manual invoices will route through the assigned processor.
* **Next step**: Configure your tax groups so charges include the correct tax rates. See: [How to Configure Tax Groups](/products/control-panel-overview/admin-overview/configure-tax-groups.md).

*Last updated: 2026-05-24*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.peoplevine.com/products/control-panel-overview/admin-overview/link-payment-processor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.