Welcome to Zuora Product Documentation

Explore our rich library of product information

How Stripe RTAU Works with Zuora

Stripe RTAU updates supported credit card payment method details using metadata returned in the PaymentIntent response.

The following workflow applies to the currently supported tokenized Stripe v2 credit-card path:

  • For supported Stripe v2 credit card payment flows, Zuora reads the masked card number, card brand, expiration month, and expiration year from the PaymentIntent response. Zuora does not read these details from webhook events. It updates only the fields whose values differ from the payment method in Zuora. The PaymentIntent response does not include the full card number. Zuora does not update the fingerprint through this flow.
  • Zuora’s Collect‑RTR service listens for these Stripe webhook events and converts them into normalized Payment Method Update (PMU) messages that billing applies to the corresponding credit card payment methods.
  • Supported Stripe event types:

    • payment_method.automatically_updated (modern Stripe PaymentMethod API)
    • customer.source.updated (legacy Card/Source API)
  • When a valid RTAU event is received, Zuora updates the existing credit card payment method record with the new card metadata (such as expiration date, last 4 digits, card brand, and fingerprint).
  • Stripe Customer ID and PaymentMethod/Source ID are stored on the existing payment method in Zuora to allow Zuora to reliably match future webhook updates to the correct record.
  • For the currently supported Stripe RTAU path, Stripe tokenization must be enabled so Zuora can store and use the Stripe identifiers required to match webhook-driven updates to the correct payment method.

  • When Zuora receives a supported Stripe RTAU webhook event for an eligible tokenized credit-card payment method, Zuora updates the existing payment method metadata in place.

RTAU complements existing PMU batch jobs by providing real‑time updates, while batch PMU can continue to cover cards and scenarios that are not eligible for RTAU.

Payment-response updates

For supported Stripe v2 credit-card payment flows, Zuora can compare the last four digits and expiration date in a successful PaymentIntent response with the payment method used for the payment. If these values differ, Zuora updates the payment method metadata. This response-based path complements the existing webhook-based update path.

This path addresses guest and inline payment flows that do not benefit from the existing asynchronous Stripe-vaulted payment-method update path. Stripe does not return the full card number in the PaymentIntent response, so Zuora updates only the card metadata Stripe provides.

Limitations

  • Credit card only - Stripe RTAU in Zuora currently applies only to credit card payment methods configured with supported Stripe gateways. Other payment method types and reference‑transaction–only payment methods are not in scope.
  • Card network and regional coverage - As with other RTAU implementations, coverage is defined by Stripe and the underlying card networks. RTAU is typically available for Visa and Mastercard in supported regions; it is intended to complement, not fully replace, PMU batch jobs.
  • No mandate updates - Stripe RTAU updates card attributes but does not update mandate IDs; mandate changes, if applicable, must follow Stripe’s mandate flows.
  • PMU coexistence - Batch PMU and Stripe RTAU are designed to work together. RTAU handles real‑time webhook‑driven updates, while PMU can continue to update cards via batch where RTAU is not available or not triggered.

By enabling Stripe RTAU in Zuora, you can significantly reduce failed payments due to stale card details, improve authorization success rates, and simplify ongoing payment operations with minimal configuration effort.