In some cases it's not possible to retrieve the charge list. If one charge cannot be decoded the entire request will be canceled and an error will be thrown. One reason for this is that we expect too many infos for some payment methods. This PR should fix this issue. In addition, the framework should become more fault tolerant. If one charge cannot be decoded, all other charges should still be returned.
2. Description of change
Changed the associated payment infos for the following payment methods to optional:
PromptPay
PayNow
Alipay Barcode
TescoLotus Bill Payment
Changed the decoding of source infos to optional
Changed the behavior when decoding the charges list to skip faulty charges
3. Quality assurance
Failed charges with no payment infos should still be decoded
In a list of charges only faulty charges should be skipped; all other charges should be decoded
1. Objective
In some cases it's not possible to retrieve the charge list. If one charge cannot be decoded the entire request will be canceled and an error will be thrown. One reason for this is that we expect too many infos for some payment methods. This PR should fix this issue. In addition, the framework should become more fault tolerant. If one charge cannot be decoded, all other charges should still be returned.
2. Description of change
3. Quality assurance
4. Operations impact N/A
5. Business impact N/A
6. The priority of change Normal