> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sellauth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Zelle

> Accept Zelle payments on SellAuth by forwarding your bank's Zelle notification emails so payments are detected and orders process automatically.

Zelle payments land directly in your bank account. SellAuth has no connection to Zelle or to your bank and detects payments by reading the "you received money with Zelle" emails your bank sends you. Once forwarding is set up, orders process automatically.

<Warning>
  Zelle offers no purchase protection and banks can restrict accounts that show a commercial pattern. Keep a second payment method enabled so a restriction does not stop the shop taking payments.
</Warning>

## Settings

**Zelle recipient.** The e-mail address or U.S. mobile number enrolled with Zelle. Shown to buyers on the payment page so they know where to send money.

**Recipient name.** The full name registered with Zelle. Shown to buyers and embedded in the QR code. Banks often ask the sender to confirm it before the transfer goes through, so showing it avoids abandoned payments.

**Notification e-mail.** The address your bank sends Zelle notifications to. It must be the same address you forward from, since that is how forwarded mail is recognised.

**Bank notification sender.** The address your bank sends Zelle notifications from, for example `alerts@notify.wellsfargo.com` for Wells Fargo. Open a real notification and copy the sender. Only emails from this address are read for your shop.

**Show QR code only.** Hides your e-mail address or phone number on the payment page. Buyers scan the QR code with their banking app instead; on a phone they save the QR image and open it from the app's Zelle scanner. The recipient name stays visible. The QR code still encodes the e-mail or phone number, so this keeps it out of sight rather than secret.

**Verification hints.** Optional text shown on the payment page for the checks some banks run before sending, usually the last 4 digits of the phone number enrolled with Zelle.

**Override memos.** SellAuth gives each buyer a memo to attach to the transfer so the payment can be matched to an invoice. You can replace the generated memos with your own comma-separated list. Memos that resemble ordinary personal transfers draw less attention than memos that read like a purchase. If you supply fewer memos than are needed, SellAuth combines them to produce more. Business plan only.

## The payment page

Buyers see a QR code in Zelle's own format, which banking apps scan to fill in the recipient, plus the recipient details as text unless you enabled **Show QR code only**. The amount and the memo cannot be prefilled by Zelle, so the page shows both with copy buttons and tells buyers to send the exact amount with the memo.

## Which banks work

Every bank sends its own Zelle notification email. SellAuth reads the emails from the bank sender you configure and looks for the amount and the memo in them. If your bank's email does not include the memo, payments cannot be matched automatically and have to be processed from the invoice page.

## Set up email forwarding

Payments are not detected until this is done. The steps below are for Gmail, and other providers have the same features under different names.

<Steps>
  <Step title="Add the forwarding address">
    In Gmail, open **Settings > See all settings > Forwarding and POP/IMAP** and click **Add a forwarding address**. Enter `payments@sellauth.com`.
  </Step>

  <Step title="Confirm the forwarding request">
    Gmail emails a confirmation to that address. SellAuth returns it to you automatically. Check your spam folder if it does not appear, then click the link inside to confirm.
  </Step>

  <Step title="Create a filter">
    Back in **Forwarding and POP/IMAP**, create a filter. In the **From** field enter your bank notification sender, the same address you entered in the method settings (`alerts@notify.wellsfargo.com` for Wells Fargo). Click **Create filter**.
  </Step>

  <Step title="Forward matching mail">
    Tick **Forward it to** and choose `payments@sellauth.com`. Create the filter.
  </Step>

  <Step title="Fill in the method settings">
    Enter your Zelle recipient, the recipient name, the same email address you forward from, and the bank notification sender, then save.
  </Step>
</Steps>

<Note>
  Use a filter rather than forwarding everything. A blanket rule sends your entire inbox to `payments@sellauth.com`, which is far more mail than the detection needs.
</Note>

## Test it

Buy something cheap from your own shop and pay it with Zelle, attaching the memo shown at checkout. The order should complete within a couple of minutes of the bank email arriving. If it stays at **Pending**, the forwarded email is not arriving or could not be read.

## Troubleshooting

**Orders never process.** Forwarding was never confirmed, or the filter does not match. Check that Gmail lists `payments@sellauth.com` as a confirmed forwarding address, and that the filter's From value matches the sender on a real Zelle notification from your bank.

**Some orders process, others do not.** Check the amount and the memo on the payment. A payment whose memo does not match the order is not matched automatically, and has to be processed from the invoice page. Partial payments are added up, and the order completes once the total covers the invoice.

**The email address does not match.** The address in the method settings must be the mailbox the forwarding comes from. Another address on the same account is not recognised.

**The bank restricted the account.** This cannot be resolved from SellAuth. Enable another method, and see [How to accept card payments](/guides/accept-cards).

## Next steps

<CardGroup cols={2}>
  <Card title="Cash App" icon="dollar-sign" href="/guides/payment-methods/cash-app">
    The same forwarding setup for Cash App.
  </Card>

  <Card title="Supported payment methods" icon="credit-card" href="/guides/payment-methods">
    A second method to run alongside this one.
  </Card>
</CardGroup>


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