We’ve been busy evolving our products here at Ding and want to let you know of the changes we are making in our DingConnect & V3 API to support Bill Payments.
Don’t worry, these are non-breaking changes. We always advise our partners to use a parser (available for all modern programming and scripting languages) to parse the JSON response. This allows us to add new fields to responses, and evolve our API over time without breaking conforming parsers.
Just make sure that your parser (serialisation / deserialisation) library does not include optional parameters. See our API documentation for more info.
Our Bill Payment product will continue to evolve, so if you are interested in selling Bill Payment products, please contact us and we will be happy to help.
The full API changes will be released Wednesday July 29th.
Changes in GetProviders:
- Provider:
- (NEW) PaymentTypes (Array[string]): Indicates the supported payment types for all the products in this provider. Current possible values are: Prepaid and Postpaid
Changes in GetProducts:
- Product:
- (NEW) PaymentTypes (Array[string]): Indicates the supported payment types for this product. Current possible values are: Prepaid and Postpaid
- (NEW) LookupBillsRequired (boolean, optional) If true, it indicates to consume this product you must call LookupBills first and send the BillRef during the SendTransfer
Changes in SendTransfer:
- SendTransferRequest
- (NEW) BillRef (string, optional): Bill reference. Required when product has “LookupBillsRequired” set to true.
(NEW) LookupBills: Method to Search available bills.
