Skip to main content

Stored credential profiles in payments and payment runs

Zuora

Stored credential profiles in payments and payment runs

  1. Last updated
  2. Save as PDF

Each time a payment method is used in a payment, Zuora checks whether the payment gateway supports stored credential transactions:

  • Gateway supports stored credential transactions

    If the payment gateway supports stored credential transactions, Zuora checks whether the payment method contains a stored credential profile:

    • If the payment method contains an Active stored credential profile, the payment complies with the relevant stored credential transaction framework.
    • If the payment method contains an Agreed stored credential profile, Zuora attempts to validate the stored credentials with the payment gateway. If the validation succeeds, the status of the stored credential profile changes to Active.

      Typically, Zuora validates the stored credentials by sending an MIT without a transaction ID to the payment gateway (see Migrate an existing payment method). However, if the payment gateway does not support MITs without transaction IDs, Zuora sends a cardholder-initiated transaction (CIT) instead. This behavior does not necessarily comply with the relevant stored credential transaction framework.

    • If the payment method does not contain an Active or Agreed stored credential profile, Zuora processes the payment as usual. In this case, the payment does not comply with the relevant stored credential transaction framework.
  • Gateway does not support stored credential transactions

    If the payment gateway does not support stored credential transactions, Zuora processes the payment as usual. In this case, the payment does not comply with the relevant stored credential transaction framework.