> ## Documentation Index
> Fetch the complete documentation index at: https://codebeans-payment-rules-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer Tag Payments Organizer

> Group payment methods by the tags on the customer account.

**Create customization → Customer Payments Organizer → Organize payment methods by customer's tags**

Groups payment methods by the tags on the customer account. The zone model again: each zone holds a set of tags and its own payment method list.

Typical uses: `wholesale`, `vip`, `net30`, `cod-blocked`, `fraud-watch`.

## Building one

1. **Title** — internal.
2. **Zones** — add the tags that belong together. Tags are matched against the logged-in customer's account.
3. **Payment methods per zone** — remove the ones that zone should not see; **Edit** to rename or set priority.
4. **Status** → **Save**.

## The logged-out problem

> [!WARNING]
>
> A customer who checks out as a guest has no account, therefore no tags, therefore matches no zone — and sees the default payment list.

This matters when the rule is restrictive. "Only `wholesale` customers see bank transfer" does not work as a tag zone alone, because guests fall through to the default list and see it too. Two ways to close the gap:

* Create a catch-all zone with no tags for everyone else, and remove the method there; or
* Use an [Advanced customization](https://codebeans-payment-rules-pro.mintlify.site/rule-types/advanced-customization.md) combining **Customer logged in** with **Customer tag**.

## Tags change nothing retroactively

Tags are read at checkout. Tag a customer today and their next checkout reflects it; orders already placed are untouched.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.