In this use case, you have a customer who wants to update billing contact and payment information.
Example: a customer moves to a new home and/or wants to use a different credit card to pay for a product.
In the example shown below, we will update only billing contact information and replace an existing payment method with a new one using the update_payment_method_m API. You can use the update_acct_complete_m API to change account and statement contact information if necessary.
Note: The sample call shown below contains a few key fields needed to successfully update billing contact and payment information. You may choose to pass in additional values based on your business requirements.
Example: you may want to validate the new payment method by using fraud protection.
Please see the update_payment_method_m API documentation for detailed information about additional available fields.
<lit:client_no>12345_sample_client_no</lit:client_no> <lit:auth_key>AbCdEfG_sample_auth_key</lit:auth_key>
Note: The primary and secondary payment methods in a billing group must be of the same <pay_method_type> (examples: credit card, direct debit, or electronic check).
Example: If Billing Group 1 has 2 different credit cards set up as the primary and secondary payment methods and you try to change the primary or secondary payment method to direct debit, you will get an error message.
The new payment method will be associated with the billing group previously linked to the disabled payment method. This means that payments for the plan(s) associated with that billing group will be made using the new payment method.
Notes:
You can check the customer's account in the Aria application to confirm that the billing contact and payment information were updated created correctly for the right billing group as described in the use case above.