Scenarios:
1)
Authorization was processed with billing descriptor 'A'
We then changed the billing descriptor to 'B'
Will capture for that authorization works?
2)
Capture was processed with billing descriptor 'B'
We then changed the billing descriptor to 'C'
Will refund for that capture works?
Hi Tom,
The merchant did a re-branding and changed its name. We had to reflect this on the Vantiv platform.
This will occur if the Auth was sent in with the Billing Descriptor 'A' and before the Deposit was sent in the billing descriptor was changed in the system to 'B' due to re-branding of the merchant.
We don't send billing descriptor for capture. So, if a merchant does not send a billing descriptor, the hardcoded billing descriptor which is this case is 'B' would have been used and the Deposit would have received an Invalid Billing Descriptor response as the Auth was processed with billing descriptor 'A' before.
A change in the billing descriptor should not impact your ability to capture or refund. Having said that, I'm a bit mistified why you would want to change the billing descriptor on each transaction. The billing descriptor is what appears on the customer's bank statement and is intended to help the customer recognize the transaction and (among other things) reduce the chance the customer will enter a chargeback, because they don't recognize the change. Also, while I am not an expert in card network regulations, I don't believe you are allowed to change the descriptor on each transaction in a stream, as you describe. In fact, on the eComm platform, you cannot change the billing descriptor on a credit (refund) transaction. The customBilling element is not part of that transaction structure.
Tom