Fix Rapyd error on billing address

[jherreraa]

OPPS-397

Summary:

Fix Incorrect Handling of Phone Number in Customer Address Object Leads to Address Validation Errors in Rapyd

Unit Tests:

Finished in 0.067795 seconds.
54 tests, 254 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
796.52 tests/s, 3746.59 assertions/s

Remote Tests:

Finished in 71.616667 seconds.
55 tests, 140 assertions, 18 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
67.2727% passed
0.77 tests/s, 1.95 assertions/s

** Failing tests are not related to change, several payment methods are not available anymore, need to be validated with rapyd support **

[naashton]

I think this change is a good candidate for a unit test that validates the presence or absence of fields, based on what we expect should happen.

[naashton]

A couple of suggestions for you.

I also see now we have 2 different methods for handling the address, def address and def add_address. Do you think there is an opportunity to refactor this to consolidate the logic of adding address details in the requests?

[jherreraa]

I think this change is a good candidate for a unit test that validates the presence or absence of fields, based on what we expect should happen.

Understood! Unit test added