Enable Address Verification Service (AVS)
Address Verification Service (AVS) checks the billing ZIP code provided at payment time against the ZIP code on file with the cardholder's bank. Enabling AVS reduces fraud, supports dispute defense, and (in the United States) avoids a higher AVS-failed processing fee for transactions where AVS data is missing or invalid.
Note: For conceptual background on the platform these settings sit in, see Zenoti payments platform.
Important β fee impact (US only). When a US transaction is processed without a valid AVS ZIP, the AVS-failed fee replaces the standard processing fee for that transaction (it does not add to it). The amount varies per processor contract β review your processor agreement for your specific rate. UK and Canada support AVS for fraud reduction without a fee penalty.
On this page
- Enable the AVS toggles
- Configure AVS fee and downgrade fee settings per processor
- Verify AVS behavior after enabling
- What AVS does
- Settings β four toggles
- Per-context guidance
- Skipping AVS at POS
- Saved-card AVS labels
- Saved-card AVS policy states
- Fee impact (US only)
- Country support
- Split payments and payout timing
- AVS Details for Saved Card report
- Interaction with other fraud-prevention layers
- Troubleshooting
Before you begin
Permission: Configure Payment Settings (under Payments) β Required to enable AVS and set the toggle behavior.
Who can do this. Org-admin and center-admin roles with payment-configuration permissions.
Availability: AVS is available in the United States, the United Kingdom, and Canada. See Country support.
- AVS is supported in the United States, United Kingdom, and Canada.
- The AVS toggles are on the Other payment settings tab of your processor's configuration, opened from Configuration > Payments > Process payments > Payment processor onboarding.
- Your center must already be onboarded to a supported payment processor. For payment processor setup, see the Integrations category.
Steps
Enable the AVS toggles
- Go to Configuration > Payments > Process payments > Payment processor onboarding, open your processor's configuration, and select the Other payment settings tab.
- Open Payment processor onboarding and select the Other Settings tab.
- Turn on the toggles that match the policy you want. Each toggle acts independently:
- Make AVS mandatory in POS β Front-desk staff must enter a billing ZIP code before completing a card payment in POS. This toggle does not decline mismatched ZIP codes on its own.
- Decline Transactions with Incorrect Zipcode in POS β Rejects a POS card transaction when the ZIP code entered does not match the issuer's records.
- Decline Transactions with Incorrect Zipcode in Webstore and Mobile App β Rejects online card transactions when the ZIP code does not match.
- Decline Transactions with Incorrect Zipcode for Recurring Transactions β Fails a recurring collection when the saved card's AVS state is invalid.
- Click Save.
Important: Zenoti always requests AVS for online transactions, even when AVS is turned off for the center. There is no override for this behavior.
Worked example: A single-center medispa in Texas wants strong in-store protection and low online friction. The center turns on Make AVS mandatory in POS and Decline Transactions with Incorrect Zipcode in POS, leaves Decline Transactions with Incorrect Zipcode in Webstore and Mobile App off, and turns on Decline Transactions with Incorrect Zipcode for Recurring Transactions. A guest who gives the wrong ZIP at the front desk is stopped at the terminal and can correct it on the spot. An online guest with a stale ZIP still completes checkout, and that transaction is billed at the AVS-failed rate because the ZIP did not match. A membership card whose address no longer matches the issuer fails at the next collection and appears in the AVS Details for Saved Card report with the label Incorrect ZIP code.
Configure AVS fee and downgrade fee settings per processor
AVS fee settings and downgrade fee settings are maintained separately for each payment processor your organization uses. The amounts, and the conditions under which each applies, come from your agreement with that processor.
- For each processor your organization uses, review the AVS fee and downgrade fee values recorded for that processor against your processor agreement.
- If your organization uses more than one processor, confirm the values for each processor separately. A change to one processor's fee settings does not carry over to another processor.
- Ask your account manager to correct any value that does not match your agreement.
Tip: For where processor rates are maintained and how they are applied, see Configure payment rates and fees.
Verify AVS behavior after enabling
- Run a card transaction at the POS to confirm the new behavior. For guidance on which card to use and how to clean up afterward, see Perform a test transaction.
- If Make AVS mandatory in POS is on, confirm the billing ZIP field is required before the payment can be completed.
- If a decline toggle is on, enter a ZIP code that does not match the card, and confirm the transaction is rejected. Then complete the transaction with the correct ZIP code.
- Void or refund the test charge so it does not remain on the guest's record or in your reporting.
- Open the guest's saved card and confirm the AVS label shown against it (see Saved-card AVS labels).
- Open the AVS Details for Saved Card report and confirm the card appears with the expected address availability.
What AVS does
When AVS is enabled and a card transaction is initiated, Zenoti requests a billing ZIP code (alongside the card number and CVC) and sends it to the processor. The processor's response includes an AVS result indicating whether the ZIP matched the issuer's records.
The AVS result is reflected on the saved-card record as one of four states (see Saved-card AVS labels). Each AVS toggle decides what happens to the in-flight transaction based on that result.
Settings β four toggles
The AVS configuration exposes four independent toggles on the Other Settings tab. Each governs a specific transaction context.
| Toggle | Effect when ON | Effect when OFF |
|---|---|---|
| Make AVS mandatory in POS | Front desk must enter a billing ZIP code before completing a card payment in POS. Does NOT itself decline mismatched ZIPs (declining requires the next toggle). | Front desk can skip AVS entry; the transaction proceeds without ZIP. The AVS-failed fee may apply (see Fee impact). |
| Decline Transactions with Incorrect Zipcode in POS | A POS card transaction with an invalid ZIP (the ZIP is provided but does not match the issuer's records) is rejected by Zenoti before processor authorization. | Zenoti does not block on AVS mismatch; the transaction proceeds. The processor still records the AVS result and the fee impact may apply. |
| Decline Transactions with Incorrect Zipcode in Webstore and Mobile App | Online (Webstore + Customer Mobile App) card transactions with invalid ZIPs are rejected. | Online transactions proceed regardless of AVS result. |
| Decline Transactions with Incorrect Zipcode for Recurring Transactions | Membership and other recurring card collections fail when the saved card's AVS state is invalid per the most recent check. | Recurring collections proceed regardless of AVS result. |
Note β toggle independence. Each context (POS / Webstore / Recurring) decides independently. Skipping the POS decline does not affect the Webstore or Recurring decline policies.
Toggle interaction examples
The four toggles produce a 16-combination matrix. The most-confusing pairings:
| Combination | What happens |
|---|---|
| Make-AVS-mandatory-in-POS = ON; Decline-incorrect-ZIP-POS = OFF | Front desk is forced to type a ZIP, but a wrong ZIP still goes through. The AVS-failed fee is avoided (because a ZIP was provided, even if wrong) but fraud-reduction is weak β the transaction completes regardless of AVS result. |
| Make-AVS-mandatory-in-POS = ON; Decline-incorrect-ZIP-POS = ON | Front desk types a ZIP; if wrong, the transaction is rejected at the POS before the processor sees it. Strongest in-store fraud prevention. The guest is present and can correct the ZIP. |
| Decline-incorrect-ZIP-Webstore = ON | Guest checking out online sees an error if their ZIP is wrong. May increase cart abandonment in exchange for better fraud control. |
| Decline-incorrect-ZIP-Recurring = ON | Membership payments fail silently when the saved card's AVS becomes invalid (e.g., guest moved). The guest discovers the issue at next checkout or member-portal interaction, not in real time. |
Per-context guidance
The four contexts (POS / Webstore / Recurring) have different operational implications even though the toggle UI looks similar.
POS
- Customer is present. A wrong-ZIP decline is recoverable in the moment β the guest can provide the correct ZIP or use a different payment method.
- Recommended for centers prioritizing fraud reduction and dispute defense.
- The "Skip AVS" path (when the mandatory toggle is off) lets front-desk staff bypass ZIP entry for trusted regulars; the AVS-failed fee may apply on those transactions.
Webstore and Customer Mobile App
- Customer is online. A wrong-ZIP decline is harder to recover from β the guest sees an error and may abandon the purchase.
- Zenoti always requests AVS for online transactions, even if AVS is disabled at the center level (Webstore-mandatory rule).
- Balance fraud reduction against checkout-completion rate; A/B test the toggle for centers with significant online volume.
Recurring
- Customer is not present. A wrong-ZIP decline fails silently; guest discovers at next checkout or via the member portal.
- Use cautiously: recurring failures may produce involuntary churn that's avoidable. Consider pairing with proactive notification and the Hard-decline flagging feature for end-to-end recovery.
Skipping AVS at POS
When Make AVS mandatory in POS is OFF, front-desk staff can skip the ZIP entry: leave the field blank and proceed with the payment. Zenoti does not currently surface a confirmation dialog warning that skipping may incur the AVS-failed fee β the consequence is documented but not surfaced in real time.
When the mandatory toggle is ON, the field is required; front desk must enter a ZIP value to proceed.
Saved-card AVS labels
Once a saved card has been used, the saved-card record displays its current AVS state.
| State (ZipCodeStatusEnum) | Display string |
|---|---|
| Valid | ZIP code available |
| Missing | ZIP code unavailable |
| Invalid | Incorrect ZIP code |
| Unknown | ZIP code unknown |
Use these labels to identify cards that need a ZIP refresh (e.g., the guest moved and the issuer's records updated).
Note. PM-attested labels such as "No ZIP code" are not in the product UI; the four labels above are the only ones used.
Saved-card AVS policy states
Alongside the ZIP code label shown on the card, Zenoti records an AVS policy state for each saved card. The policy state reflects the outcome of the address check applied to that card, and is what recurring collections evaluate when the recurring decline toggle is on.
| Policy state | What it means |
|---|---|
| Unknown | No address check result has been recorded for the card yet. |
| Accepted | The address check passed. |
| Declined | The address check failed. |
| Pending | An address check has been requested but no result has returned yet. |
| Partially accepted | Some, but not all, of the address elements matched the issuer's records. |
A card can show a policy state of Declined while the ZIP code label reads Incorrect ZIP code β the two describe the same underlying result from different angles: the policy state records the decision, the label records what is known about the ZIP code itself.
Fee impact (US only)
In the United States, transactions processed without a valid AVS ZIP are subject to an AVS-failed fee. This fee replaces the standard processing fee β it does not add to it. So the cost of a no-AVS US transaction is the AVS-failed rate, not the standard rate plus AVS-failed.
This is meaningful for cost calculation:
- Skipping AVS on a single transaction: the cost of that transaction is the AVS-failed fee.
- Enabling AVS but not declining mismatches: most transactions process at the standard rate; only those without a ZIP value at all incur the failed-rate.
- Enabling AVS and declining mismatches: mismatched transactions are rejected (no fee); valid-ZIP transactions process at the standard rate.
The actual AVS-failed fee amount varies per processor and per merchant contract. Refer to the Payments rate table for your processor or contact your account manager for the specific number. The fee replaces (not adds to) the standard processing fee and applies only in the US; UK and Canada have no AVS-failed-fee penalty.
In the United Kingdom and Canada, AVS is supported for fraud reduction; there is no AVS-failed-fee penalty for transactions without a valid ZIP. The fraud-prevention benefit (AVS data on the dispute record helps win disputes) still applies, so enabling AVS in these regions is recommended even without the cost incentive.
What counts as valid? "Valid" means the ZIP code was entered AND it matched the issuer's records. A ZIP that was entered but did not match the issuer (ZipCodeStatusEnum.Invalid) is not valid for fee-avoidance purposes β it is treated as failed.
Country support
AVS behavior differs by country. The table below summarizes where AVS is supported and where the AVS-failed fee applies.
| Country | AVS support | AVS-failed fee |
|---|---|---|
| United States | Full support, including all four toggles | Yes β the AVS-failed fee replaces the standard processing fee for transactions without a valid ZIP |
| United Kingdom | Supported for fraud reduction | No fee penalty |
| Canada | Supported for fraud reduction | No fee penalty |
Split payments and payout timing
AVS fee and downgrade fee settings are maintained per processor. Two related behaviors come up when reviewing those fees against an invoice: how a payment is divided across merchant accounts, and when the funds become available for payout.
How an invoice payment is split across merchant accounts
Where a center pays contractors through their own merchant accounts, Zenoti splits each invoice payment between the host business merchant account and the contractor merchant accounts, based on how the items on the invoice are attributed:
- Service items performed by a contractor route to that contractor's Stripe Express account.
- Service items performed by an employee route to the host business.
- Non-service items β products, classes, workshops, gift cards, and packages β route to the host business, regardless of the employee or contractor who performed any associated service.
- Tips on a contractor's service line route to the contractor.
The split is computed at the line-item level, not at the invoice level. For setup, see Configure split payments and Set up contractor (self-employed) payments.
Transaction availability date and payout timing
Zenoti tracks changes to a transaction's availability date β the date on which its funds become available for payout. When the availability date for a transaction changes, payout timing follows the updated date, so a transaction can land in a later payout than the one you first expected. See Payout speeds in Zenoti Payments and View and manage payouts.
AVS Details for Saved Card report
A dedicated AVS Details for Saved Card report (under the Reports module) shows AVS state across saved cards in your organization. Use it to identify cards with missing or invalid addresses and drive proactive guest outreach.
Prerequisite β email template required. The Request address for saved card email template must be configured before you can use the Email Guests feature in this report. Set up the template under Configuration > Notifications > Templates for email and text.
Filters
| Filter | Description |
|---|---|
| Centers | Filter results to one or more centers. |
| Last Transaction Date | Restrict to cards last used within a date range. |
| Payment Provider | Filter by processor (Adyen, Stripe, etc.). |
| Card Brand | Filter by card network (Visa, Mastercard, Amex, etc.). |
| Address Availability | Filter by address status (Valid, Missing, Invalid, Unknown). |
Columns
| Column | Description |
|---|---|
| Center Name | The center where the card is on file. |
| Guest Name | The guest who owns the saved card. |
| Guest Email | Guest email address (used for the Email Guests workflow). |
| Card Brand | Card network (Visa, Mastercard, etc.). |
| Card Ending | Last 4 digits of the saved card. |
| Card Type | Card category (credit, debit, prepaid). |
| Last Transaction Date | Date of the most recent transaction using this card. |
| Last Transaction Status | Status of the most recent transaction. |
| Membership Linked | Whether the card is linked to a membership for recurring collection. |
| Address Availability | Current AVS state of the card (Valid / Missing / Invalid / Unknown). |
| Address Updated On | Date when the address was last updated on the card. |
| Is Address Valid | Yes/No indicator based on the most recent AVS check. |
| Last Email Status | Status of the most recent email sent via the Email Guests button. |
Email Guests
The Email Guests button sends the Request address for saved card email template to guests whose saved cards are missing a billing address.
- Filter the report to Address Availability = Missing (or a date range where addresses lapsed).
- Select the guest rows to contact, or select all.
- Click Email Guests.
- Confirm the send. Zenoti sends the configured email template to each selected guest.
After sending, the Last Email Status column reflects the delivery outcome for each row.
Interaction with other fraud-prevention layers
AVS is one of several fraud-prevention signals Zenoti supports. Common pairings:
- 3D Secure (3DS) β issuer-side authentication challenge for online transactions; layers with AVS.
- CVC verification β the 3- or 4-digit code on the card; verified during authorization.
- Hard-decline flagging β see Flag payment accounts for hard declines.
The orchestration order between AVS, 3DS, CVC, and hard-decline flagging is processor-specific; consult your processor documentation for the exact sequence.
For a fraud-prevention strategy, enabling AVS, 3DS, and hard-decline flagging together provides defense in depth: AVS reduces card-not-present fraud, 3DS shifts liability for authenticated online transactions, hard-decline flagging stops repeat attempts on closed cards.
Tips
- Turn on Make AVS mandatory in POS together with Decline Transactions with Incorrect Zipcode in POS for the strongest in-store protection. The guest is present, so a mismatch can be corrected at the terminal.
- Before turning on Decline Transactions with Incorrect Zipcode in Webstore and Mobile App, note your current online checkout-completion rate so you can compare it afterward. Online guests cannot ask a staff member for help when a ZIP is rejected.
- Run the AVS Details for Saved Card report monthly, filtered to Address Availability = Missing, and use Email Guests to collect addresses before the next recurring collection cycle.
- Review AVS fee and downgrade fee settings for every processor whenever you add a processor or renegotiate rates β the values do not carry over between processors.
- Pair Decline Transactions with Incorrect Zipcode for Recurring Transactions with hard-decline flagging so failed recurring collections are surfaced and worked rather than retried indefinitely.
Troubleshooting
Use this table to diagnose the most common AVS issues.
| Symptom | What to check |
|---|---|
| A POS card payment is rejected with an address error. | Decline Transactions with Incorrect Zipcode in POS is on and the ZIP entered does not match the issuer's records. Ask the guest for the ZIP code on their card statement, or take payment with a different method. |
| Online checkout fails with an address error even though the AVS toggles are off for the center. | Zenoti always requests AVS for online transactions, regardless of the center's toggles. Confirm the guest's billing ZIP matches the address their bank has on file. |
| A recurring membership collection keeps failing and the guest reports no error. | Open the saved card and check its label. Incorrect ZIP code or ZIP code unavailable with the recurring decline toggle on will fail every attempt. Ask the guest to update the card's billing address, then retry the collection. |
| Transactions are billed at a higher rate than expected (US). | AVS data was missing or did not match, so the AVS-failed fee replaced the standard processing fee. Turn on Make AVS mandatory in POS to stop staff skipping ZIP entry, and confirm the AVS fee value for that processor against your agreement. |
| Email Guests produces no emails, or Last Email Status shows a failure. | The Request address for saved card email template is not configured or not enabled, or the selected guests have no email address on file. Configure the template, then re-run the send. |
| A transaction settled into a later payout than expected. | The transaction's availability date changed after authorization. Check the payout the transaction was included in β see View and manage payouts. |