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:
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.
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.
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
Say you run a program of mostly individual creators with a handful of agency partners. You need two methods:
Enable PayPal. Keep its single required field — PayPal email. This covers the majority of creators, including international ones.
Enable Bank transfer for agency partners. Require bank name, account name, and account number; leave agency code and BIC optional unless a partner's country needs them.
Disable Debit cash and Google pay. PayPal already covers the lightweight case, so turn them off so no affiliate is offered a method you can't pay through.
Trim required fields. If you can complete a bank transfer with name and account number, leave the rest optional.
Result: a creator fills in one field; an agency fills in three. No partner sees a dead-end option, and you reconcile exactly two payout flows. When it's time to pay, every detail you need is already on the profile — see Affiliate payouts.
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.
You can edit each template to match your brand voice. Open affiliate email notifications to view and update them.
Send a test email
Before launching, send yourself a test of any affiliate email to check wording and formatting:
Open the email you want to test.
Enter one or more recipient addresses.
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.
Assuming disabled emails are sending. The "declined," "denied," and owner-notification emails are off by default. Enable them and set a recipient if you need them — see Affiliate email notifications.
Skipping test sends. A partner receiving an email with a placeholder still showing is avoidable. Test every active template first.
Mismatched field labels. Use labels that match what the partner copies from their bank app to prevent mistakes.
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 — every email type, variables, and editing.
Getting started with affiliates — program overview and onboarding.
Affiliate payouts — where payment methods are used.
Managing affiliates — registration and statuses that trigger emails.
Recruiting affiliates — getting the right partners into a program that's ready to pay them.
Last updated