Define payment rules
Learn how to configure your company's payment policies, including credit balance adjustments, credit card expiration validation, and payment method cascading.
You can use the Payment Rules page to define your company's payment policies or rules around credit balance, payments, refunds, and so on.
Click your username at the top right and navigate to Payments > Payment Settings > Define Payment Rules to configure payment rules.
For payment rules applied only to integrations that are requested through the Specialized Payment Connections service, see the article for the specific payment gateway integration .
Enable future dated credit balance adjustment
This payment rule is only available if you have the Credit Balance feature enabled. If you want to have access to the feature, submit a request at Zuora Global Support .
Select whether to enable the capability of specifying a credit balance adjustment date to a future date and processing credit balance adjustments from or to a future dated invoice.
The following options are provided:
-
Yes (default) The Future Dated Credit Balance Adjustment feature is enabled. You can specify a credit balance adjustment date to a future date and process credit balance adjustments from or to a future dated invoice.
-
No You cannot specify a credit balance adjustment date to a future date or process credit balance adjustments from or to a future dated invoice.
This payment rule is only available if you have the Credit Balance feature enabled. After you set this payment rule to Yes , the Future Dated Credit Balance Adjustment feature is enabled. See Future Dated Credit Balance Adjustment for more information.
Validate credit card expiration date
Select whether to validate credit card expiration date. This setting is enabled by default, validating if the expiration month and year of the credit card are earlier than the current month and year.
If you need to migrate data of your existing credit card payment methods, you can disable this setting during migration. Ensure to enable this setting again after your migration is completed.
Payment Methods Cascading
Select whether to enable the Cascading Payment Method feature for dynamically retrying the payment with different payment methods in the order defined in a priority list. This feature is disabled by default.
This feature is in the Early Adopter phase. We are actively soliciting feedback from a small set of early adopters.
Enable 'Pending' statuses for delayed payment confirmations
Select whether to enable the Asynchronous Payment Statuses feature. When enabled, a Pending payment status is included in the asynchronous payment flow for electronic ACH and Bank Transfer transactions to indicate that transactions are awaiting settlement confirmation.
Select the source field for Soft Descriptors to appear on statements
Select the field that Zuora will use to populate the soft descriptor sent to supported payment gateways. The descriptor appears on your customers’ card or account statements and can help them recognize transactions more easily.
You can choose a standard or custom field from the following objects:
- Payment
- Account
- BillToContact
- SoldToContact
- PaymentMethod
- SubscriptionRatePlanCharge
For SubscriptionRatePlanCharge, Zuora supports these standard fields:
- Charge ID
- Charge number
- Subscription ID
- Subscription number
- Rate plan ID
- Product rate plan charge ID
You can also select supported custom fields on SubscriptionRatePlanCharge.
This option is useful when you want statement descriptors to include charge-level or subscription-level details, such as when a customer account contains multiple subscriptions.
If the selected SubscriptionRatePlanCharge field does not contain a value at payment time, Zuora uses the existing static soft descriptor instead.
- This feature is available only for gateways that support dynamic soft descriptors.
- Existing configurations continue to work. No migration is required.
- If a payment applies to multiple invoices or charges, only one charge value is used for the descriptor. It is only recommended to use the SubscriptionRatePlanCharge as the source object if your business has single charge invoices.
- To ensure the expected value appears on statements, test your selected field before using it in production.
- Gateway character limits still apply, so the final descriptor shown on the statement might be shortened.
The descriptor, containing the retrieved text, will be displayed on your customers’ card or account statements and help them identify transactions.
Supported Payment Gateway integrations
Stripe v2
PayPal Complete Payments
Checkout.com
Braintree v2.0
BlueSnap