Key Considerations
Following are the consideartions to use payment surcharges:
- Payment surcharges are supported for payments generated from payment runs and payment retries (OOTB and CPR) only. Payments generated via Zuora UI/API orHPM are not considered for surcharge evaluation.
- Payment run must be configured to take one payment against one invoice as surcharge is not evaluated in scenarios where a single payment is collected for multiple invoices/debit memos.
- Surcharge configuration is available via API only.
- Surcharge integration is supported via the Chase orbital payment gateway.
- Journal Run and Trial balance generation are supported. Revenue Recognition is supported through Zuora finance (and legacy Revenue), not Zuora Revenue (formerly known as Revpro).
- Journal Run, Trial Balance, and legacy Revenue (upon posting of Debit Memo) are supported. Detailed data source for Journal Run doesn’t contain surcharge.
- Zuora Advanced Custom Fields are not supported. For more information, see Manage custom fields with the Object Manager. P
Other key considerations
- Surcharges cannot be discounted.
- Order preview doesn’t support surcharge (that is, surcharge is not evaluated during the checkout process).
- Surcharge is not associated with the Accounts, Subscriptions, or Orders.
- Invoice preview doesn’t evaluate surcharge as the surcharge is only evaluated during Payment Request generated through Payment Run.
- Evaluation of the surcharge at the time of payment request has the potential to slow the payment run performance down due to the inclusion of tax calculation on surcharge and debit memo creation.
- In case of a failure in Surcharge evaluation or tax calculation (for example, Customer Sold to Contact does not provide the postcode leading to tax calculation failing), the payment request will fail. This will manifest as “unprocessed” invoices on the payment run page with the appropriate error messages. The user can execute an ad hoc payment run for these invoices or the subsequent payment run will automatically pick these up.
- If surcharge configuration is completed while certain payments are in retry via OOTB retry or CPR, and such payments are evaluated to be eligible for a surcharge, a surcharge will be included in the total payment amount processed by the retry.
- If a particular attribute combination is not found in the configuration, then that combination (hence payment) is considered ineligible for a surcharge.
- BIN Lookup must be enabled in your environment prior to surcharges enablement. Zuora will rely on BIN values (card brand, card class, card product type, Issuer, Issuing Country) to determine surcharge eligibility for a payment method.