Learn how to enable Level 2 and Level 3 card data processing by configuring necessary settings in your CyberSource gateway instance.

1. Select the Enable Level 2 Processing or Enable Level 3 Processing checkboxes to enable Level 2 or Level 3 processing. Note that if both checkboxes are selected, then Level 3 is enabled.
2. For the Processor list, select the processor your CyberSource account is using.
3. For Chase Paymentech Solutions or FDC Nashville Global processor, the ShipFrom Postal Code Custom Field API Name field must be included for each payment request. ShipFromPostalCode must be configured in Zuora as an Account level custom field. Enter the API name for this custom field as a gateway setting. The postal code consists of 5 to 9 digits.

   • If the billing country is the U.S., the 9-digit postal code must follow this format: [5 digits][dash][4 digits]. For example, 12345-6789.

   • If the billing country is Canada, the 6-digit postal code must follow this format: [alpha][numeric][alpha][space][numeric][alpha][numeric]. For example, A1B 2C4.

4. If you do not specify the settings described in Step 5, enter the CommodityCode API name and ProductCode API name in the CommodityCode Custom Field API Name and ProductCode Custom Field API Name fields, respectively. CommodityCode and ProductCode must be configured in the Zuora product catalog as ProductRatePlanCharge level custom fields. These two fields are required to qualify your merchant account for Level 2 and Level 3 interchange rate. You should enter the custom field API names without the __c suffix. If you want to populate the preceding custom fields to existing subscriptions, you must set up the custom fields using identical API names on the Product Rate Plan Charge and Subscription Rate Plan Charge objects. Then you need to update the existing subscription rate plan charges with the custom field values you want to use.
5. If you specify the following fields, you do not need to configure the preceding charge level custom fields: Zuora will then use the specified values for all invoice charges, and level 2 and level 3 capture requests, instead of getting values from charge level custom fields. You can also choose to specify only one field, or leave both fields empty. If you do not specify a static value, you must configure a corresponding charge level custom field and enter the API name for this custom field in the gateway settings described in Step 4, to avoid payment failures.

   • Static Value for commodityCode

   • Static Value for productCode

6. Enter the Invoice Items Limit gateway setting for Level 2 and Level 3 requests. Currently, CyberSource documents this limit as 98. Therefore, you need to enter 98 in the Invoice Items Limit field in the gateway instance configuration page.