> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/affiliate-program/settings.md).

# Program Settings

Affiliate settings control how you pay partners and how the program communicates with them. Getting these right before you recruit matters — an affiliate who earns a commission but can't be paid, or never gets a clear confirmation email, quickly loses trust. This page covers payment methods and email notifications, plus how to test emails before going live.

> **Best practice:** Offer the payout methods your affiliates actually use. A familiar method removes friction; one they can't receive money through adds it. Require only the fields you genuinely need to complete a payment. Then test every active affiliate email so the first message a real partner sees is exactly what you intend.

### Payment methods

Payment methods define how you pay affiliates and what details you collect. Configure them under **Branding → Payments**.

Bloop ships with four methods enabled by default:

| Method        | Default fields collected                                                                |
| ------------- | --------------------------------------------------------------------------------------- |
| Bank transfer | Bank name, account name, account number (required); agency code and BIC code (optional) |
| PayPal        | PayPal email (required)                                                                 |
| Debit cash    | Name, debit card number (required)                                                      |
| Google pay    | Email (required)                                                                        |

For each method you can:

* **Enable or disable** it — only enabled methods are offered to affiliates.
* **Edit the fields** it collects, including each field's label, key, type, and whether it is required.

Details an affiliate enters here are stored on their profile and shown when you [pay them out](/affiliate-program/payouts.md).

#### Choosing which methods to offer

More payout options means more decisions for the affiliate and more reconciliation for you. Enable the one or two methods that cover your partners and disable the rest.

| Method        | Best for                                                 | When to offer it                                                       | Friction to watch                                                    |
| ------------- | -------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------- |
| PayPal        | Individual creators, influencers, international partners | Most creator-led programs — fast, familiar, and crosses borders easily | Requires a PayPal account; fees may apply on their end               |
| Bank transfer | Businesses, agencies, higher-volume or local partners    | Larger or recurring payouts and partners who prefer direct deposit     | Most fields to collect and verify; details vary by country           |
| Google pay    | Partners in the Google Pay ecosystem                     | A lightweight email-based option alongside PayPal                      | Narrower availability and reach than PayPal                          |
| Debit cash    | Programs that pay directly to a card                     | Niche cases where a card payout is how you settle                      | Card-number fields are sensitive; only enable if you actually use it |

A creator-led program can often run on PayPal alone; a B2B or agency program leans on bank transfer. Offering all four forces every affiliate to choose and leaves you reconciling four payout flows for no benefit.

#### Editing a method's fields

Each field has a **label**, a **key**, a **type**, and a **required** flag. Two principles keep payouts smooth:

* **Require only what you can't pay without.** For bank transfer you genuinely need account name and number; agency code or BIC may be optional depending on the country. Marking a "nice to have" as required delays the partner from finishing their profile.
* **Label fields the way the partner's bank or wallet does.** Matching labels mean a partner copying details from their bank app won't second-guess which number goes where.

### A worked example: a creator program's payout setup

For a program of mostly individual creators with a handful of agencies: enable **PayPal** (its one required field covers most creators), enable **Bank transfer** for agencies (require bank name, account name, account number; leave agency code and BIC optional), and disable Debit cash and Google pay so no affiliate sees a method you can't pay through. A creator fills in one field, an agency fills in three, and you reconcile exactly two payout flows — see [Affiliate payouts](/affiliate-program/payouts.md).

### Email notifications

Bloop sends affiliates transactional emails at key moments — registration (pending), approval or decline, sale approval or decline, coupon assignment, and payout. Default templates are created during setup.

Some templates ship **disabled** — the "declined" and "denied" templates, and both owner-facing notifications — so they won't fire until you turn them on. If you want alerts on new registrations, enable that owner notification and set a recipient. The full list of types, triggers, and default on/off states is in [Affiliate email notifications](/affiliate-program/emails.md).

You can edit each template to match your brand voice. Open [affiliate email notifications](/affiliate-program/emails.md) to view and update them.

### Send a test email

Before launching, send yourself a test of any affiliate email to check wording and formatting:

1. Open the email you want to test.
2. Enter one or more recipient addresses.
3. Send the test.

Bloop renders the template with your store's details and delivers it to the addresses you entered. Test sends are rate-limited, so send in small batches.

Test every enabled email — especially the approval and payout messages, since those are what partners read most carefully. A test send is the only way to catch an unfilled variable or broken button before a real partner sees it.

### Common mistakes to avoid

* **Offering every payment method.** Enable the one or two that fit your partners; disable the rest.
* **Over-requiring payout fields.** Require only what you need to complete a payment. Optional details stall a partner mid-setup.
* **Skipping test sends.** A partner receiving an email with a placeholder still showing is avoidable. Test every active template first.

### When to revisit these settings

* **Your partner mix shifts** (more creators or more agencies) → revisit which payment methods are enabled.
* **You expand to new countries** → bank-transfer fields may need adjusting (agency code, BIC) for partners' regions.
* **You change your brand voice or program name** → re-edit the email templates so messages still sound like you.
* **Payouts feel slow to set up** → trim the required-fields list; partners complete profiles faster with fewer required fields.

### Related

* [Affiliate email notifications](/affiliate-program/emails.md) — every email type, variables, and editing.
* [Getting started with affiliates](/quick-start/getting-started-1.md) — program overview and onboarding.
* [Affiliate payouts](/affiliate-program/payouts.md) — where payment methods are used.
* [Managing affiliates](/affiliate-program/affiliates.md) — registration and statuses that trigger emails.
* [Recruiting affiliates](/best-practices/recruiting-affiliates.md) — getting the right partners into a program that's ready to pay them.


---

# 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://docs.bloop.plus/affiliate-program/settings.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.