customBilling
The customBilling
element allows you to specify custom billing descriptor information for the transaction. This billing descriptor is used instead of the descriptor defined as the default billing descriptor. If you do not define this element, the system uses the default. Mastercard Installment Payment Providers and Discover Installment transactions also use the child element to provide additional information about the underlying retailer selling the goods.
If you submit a captureGivenAuth
transaction with a customBilling
element and Worldpay finds a matching Authorization (see Capture Given Auth Transaction), the system uses the customBilling
information from the Authorization and discards the information from the captureGivenAuth
.
Parent Elements:
authorization, captureGivenAuth, credit, echeckCredit, echeckSale, forceCapture, sale
Although the schema includes the customBilling
element as a child of echeckCredit
and echeckSale
, Worldpay does not support its use in these instances.
Attributes:
None
Child Elements:
Required for card-not-present transactions: phone, or url
Please consult your Relationship Manager prior to using the <url> element. The contents of this element are discarded unless Worldpay specifically enables to use it in your cnpAPI submissions.
Required for card present transactions: city
Optional for either: descriptor
Example: customBilling Structure - Card-Not-Present (using phone child)
<customBilling>
<phone>Telephone Number</phone>
<descriptor>Billing Descriptor</descriptor>
</customBilling>
Example: customBilling Structure - Card-Not-Present (using url child)
<customBilling>
<url>retail.url</url>
<descriptor>www.retail.com</descriptor>
</customBilling>
Example: customBilling Structure - Card-Present
<customBilling>
<city>City</city>
<descriptor>Billing Descriptor</descriptor>
</customBilling>
Example: customBilling Structure - Discover Installment
<customBilling>
<phone>Retailer Telephone Number</phone>
<city>Retailer City</city>
<descriptor>Retailer Billing Descriptor</descriptor>
</customBilling>
Example: customBilling Structure - Mastercard IPP
<customBilling>
<descriptor>IPP Name*Retailer Billing Descriptor</descriptor>
</customBilling>
For a Mastercard IPP transaction, include the merchantCategoryCode elemnt in the transaction, specifying the MCC of the underlying retailer.