ZenotiHelp

Fiserv credit card processor

ZTZenoti Docs Team Updated September 17, 2026 6 min readGuide

Zenoti supports Fiserv as a payment processor for credit card operations, including authorization, capture, tokenization, and recurring charges. This article explains how each Fiserv payment flow works and how to use them in your organization.

Audience: Administrators and finance staff who configure or manage Fiserv payment processing.

Before you begin

  • Your organization must have Fiserv configured as a payment processor. For payment processor setup, see the Integrations category.

  • You need the following permissions:

    Permission: Configure Payment Settings (under Payments) — Required to configure processor onboarding settings, modify processor rate configurations, and initiate card migration between processors. Manage Payment Settings (under Payments) also opens this page.

  • Confirm with your Fiserv account representative which flows are enabled for your region. The card-save-only flow is required in markets where a $0 authorization is not supported (for example, Mexico).

Steps

Understand the Fiserv payment flows

Zenoti supports three distinct Fiserv payment flows. Review the table below to determine which flow applies to your use case before proceeding.

The following table compares the three flows:

Flow When to use How it works
Standard authorization and capture Most credit card transactions Authorizes the card for the transaction amount, then captures the funds at checkout
Card-save-only (tokenization without authorization) Markets where $0 authorization is unsupported (for example, Mexico), or when migrating cards from another vault where CVV is unavailable Tokenizes the card via the Fiserv payment token endpoint without a monetary authorization
Payment-plus-save When you want to collect payment and store the card in a single step Attaches a token-creation instruction to the sale request so the token is returned in the payment response

Note: For stored payment account management, see the Integrations category.

Process a standard credit card payment

Standard authorization and capture is the default flow for Fiserv credit card transactions. Zenoti authorizes the card for the transaction amount and captures the funds when the invoice is closed.

  1. Open the invoice at the point of sale.
  2. Select the credit card payment method.
  3. Present the card to the terminal or enter the card details.
  4. Zenoti sends an authorization request to Fiserv. When approved, the authorization hold is placed on the guest's card.
  5. Close the invoice. Zenoti captures the authorized amount from Fiserv.

Tip: For processing payments at the point of sale, see Point of Sale.

Save a card without a monetary authorization (card-save-only flow)

Use this flow when your region does not support $0 authorization, or when you are migrating cards from another vault where CVV is unavailable. The card is tokenized directly without charging the guest.

  1. Open the guest profile.
  2. Navigate to the payment details section and select the option to add a card on file.
  3. Enter the card details. Zenoti sends the card information to the Fiserv payment token endpoint.
  4. Fiserv returns a token. Zenoti stores the token against the guest profile without placing any authorization hold.
  5. Confirm that the card appears as saved in the guest's payment details.

Important: Because no authorization is performed, card validity is not confirmed at the time of saving. Verify the card is valid before relying on it for recurring collections.

Collect payment and save the card in a single step (payment-plus-save)

Use this flow when you want to collect payment and store the card for future use without making a second API call. Zenoti attaches a token-creation instruction to the sale request, and Fiserv returns the token in the payment response.

  1. Open the invoice at the point of sale.
  2. Select the credit card payment method.
  3. Present the card to the terminal or enter the card details.
  4. Zenoti sends the sale request to Fiserv with a token-creation instruction included.
  5. Fiserv processes the payment and returns both the payment confirmation and the card token in a single response.
  6. Close the invoice. The card is automatically saved to the guest profile for future use.

Note: The payment-plus-save flow reduces API calls compared to saving the card separately after payment. This is the recommended approach when both payment and card storage are required in the same transaction.

Charge a stored card for recurring payments (MIT flow)

Fiserv recurring charges use stored credentials to comply with Visa and Mastercard network rules. The first charge must be a guest-initiated, card-present or card-entry transaction (ECOM). Subsequent charges use the scheme transaction ID from that first transaction.

  1. Confirm that the guest has a card on file saved through either the card-save-only or payment-plus-save flow.
  2. When a recurring collection is triggered (for example, a membership billing cycle), Zenoti sends a merchant-initiated transaction (MIT) request to Fiserv.
  3. The request includes the stored credentials sequence indicator set to subsequent, along with the scheme transaction ID from the original guest-initiated charge.
  4. Fiserv processes the recurring charge and returns a confirmation.
  5. The transaction status updates automatically in the payment dashboard.

Important: The scheme transaction ID from the first ECOM charge is required for all subsequent MIT charges. If this ID is missing or invalid, Fiserv will decline the recurring transaction. Ensure the initial guest-initiated charge completes successfully before scheduling recurring collections.

Note: For membership billing configuration, see the Memberships category.

Tips

  • Use payment-plus-save for new guests at checkout. When a guest pays for the first time and you anticipate future recurring charges, use the payment-plus-save flow to capture the card token in a single step. This avoids a separate card-save step and ensures the scheme transaction ID is available for future MIT charges.
  • Use card-save-only when migrating from another processor. If you are moving stored cards from a different vault and CVV data is unavailable, the card-save-only flow lets you tokenize cards without requiring a $0 authorization. For stored payment account management, see the Integrations category.
  • Verify the scheme transaction ID after the first ECOM charge. Before scheduling recurring collections, confirm in the payment dashboard that the initial guest-initiated transaction completed and that the scheme transaction ID was captured. A missing ID will cause all subsequent MIT charges to fail.
  • Check regional support before selecting a flow. The card-save-only flow is required in markets where $0 authorization is not supported. Confirm your region's requirements with your Fiserv account representative before configuring payment flows.

Troubleshooting

Problem Likely cause Resolution
Recurring charge is declined by Fiserv The scheme transaction ID from the first ECOM charge is missing or was not stored correctly Verify that the initial guest-initiated charge completed successfully in the payment dashboard. If the ID is missing, the guest must complete a new card-present or card-entry transaction to generate a valid scheme transaction ID before recurring charges can resume.
Card-save-only fails with a tokenization error The card details entered are invalid, or the Fiserv payment token endpoint is unreachable Confirm the card number, expiry date, and billing details are correct. Check the payment dashboard for error details. If the endpoint is unreachable, verify your Fiserv processor configuration in the Integrations category.
Payment-plus-save completes payment but does not save the card The token-creation instruction was not included in the sale request, or Fiserv returned an error for the token portion Review the transaction details in the payment dashboard. If the card was not saved, ask the guest to add the card on file separately using the card-save-only flow, or retry the payment-plus-save flow.
MIT charge fails with a stored credentials error The subsequent sequence indicator or scheme transaction ID is incorrect Confirm that the stored credentials sequence is set to subsequent and that the scheme transaction ID matches the original ECOM charge. Contact your Fiserv account representative if the error persists.
Was this article helpful?
Your feedback helps us improve our documentation.