Merchant Descriptor Logic

 

Some of the logic described in this section might not apply to your implementation depending on which parts of the merchant descriptor functionality are enabled in your CyberSource account.

 

You are responsible for ensuring that all the merchant descriptor location information that CyberSource sends to the processor is compatible. For example, if a request message includes one merchant descriptor location field, CyberSource might use the information in your CyberSource account to populate the remaining merchant descriptor location values that it sends to the processor. CyberSource does not check the merchant descriptor values to ensure that the combination of values from the request message and from your CyberSource account are compatible. To avoid a mismatch of merchant descriptor location values, CyberSource recommends that you include all the merchant descriptor location fields in a request or do not include any merchant descriptor location fields in a request.

For authorizations, CyberSource provides merchant descriptor information to FDC Nashville Global only when you include merchant descriptor information in the authorization request. For each merchant descriptor, when you do not include the merchant descriptor value in an authorization request, CyberSource does not send a merchant descriptor value to FDC Nashville Global.

For captures, CyberSource provides merchant descriptor information to FDC Nashville Global when you provide merchant descriptor information in the capture request, authorization request, or your CyberSource account. For each merchant descriptor, when you do not include the merchant descriptor value in a capture request, CyberSource uses the value from the authorization request. If you did not include the merchant descriptor value in the authorization request, CyberSource uses the corresponding value from your CyberSource account. If the value is not included in your CyberSource account, FDC Nashville Global uses the value from your First Data merchant master file.

For follow-on credits, CyberSource provides merchant descriptor information to FDC Nashville Global when you provide merchant descriptor information in the credit request, capture request, authorization request, or your CyberSource account. For each merchant descriptor, when you do not include the merchant descriptor value in a follow-on credit request, CyberSource uses the value from the capture request. If you did not include the merchant descriptor value in the capture request, CyberSource uses the value from the authorization request. If you did not include the merchant descriptor value in the authorization request, CyberSource uses the corresponding value from your CyberSource account. If the value is not included in your CyberSource account, FDC Nashville Global uses the value from your First Data merchant master file.

For stand-alone credits, CyberSource provides merchant descriptor information to FDC Nashville Global when you provide merchant descriptor information in the credit request or your CyberSource account. For each merchant descriptor, when you do not include the merchant descriptor value in a stand-alone credit request, CyberSource uses the corresponding value from your CyberSource account. If the value is not included in your CyberSource account, FDC Nashville Global uses the value from your First Data merchant master file.

To add a merchant descriptor value to your CyberSource account, contact CyberSource Customer Support.