update address info in card tokenization

[chadwhitacre]

Reticketed from #2372 (comment).

The original tokenization payload you sent through looks like

{
...
      "address": {
        "state": "VD",
        "postal_code": "1807",
        "line1": "<REMOVED>"
      }
...
}

what you want it to look like would be (documentation)

{
...
            "address": {
                "city": null, 
                "country_code": "CHE", 
                "line1": "<REMOVED>", 
                "line2": null, 
                "postal_code": "1807", 
                "state": "VD"
            }, 
...
}

looks like the country code field is the only thing missing. alternatively you can omit the address data entirely. i'm not sure if that would increase the likelyhood of verifying the card but i do think it will work better than passing (inadvertently) incorrect address data. maybe balanced should not default the country code to USA as well.

[seanlinsley]

Leaving this open for now, to discuss whether we still need to send up address info as part of meta.

[chadwhitacre]

@seanlinsley The issue is that we pull info out of meta when repopulating the form. If we change that class around then we would want to either migrate the address to the new location for all old accounts, or write the class to support both access patterns.

[seanlinsley]

Going through the code... can we delete the Stripe stuff already?

[seanlinsley]

@whit537 to ensure that I do the migration correctly, could you provide an anonymized JSON dump for a CC and bank account from Balanced that use the old scheme(s)?

[chadwhitacre]

[C]an we delete the Stripe stuff already?

That's #173. We have one participant still on Stripe, because they fell through the cracks when migrating data to Balanced. We charged them on Stripe as recently as this last payday.

[chadwhitacre]

Closing as stalled.

[chadwhitacre]

Blech, sorry. Meant that for #2450.