Changelog 06.07.2022

Check before linking card if it is NOT blocked or in a non-ACTIVE state
Interledger same response as intra
Fixed invalid mobile number issue on sandbox - Mobile number is randomly generated despite what is input to ensure validity. On production these numbers are SMS validated.
Balances update immediately after a transaction
3DSecure handled separately, does not error out if enrol is unsuccesful. But cannot update 3DS settings if 3DS provider is down
Empty array returned when no cards have been created.
Single enrichment endpoint creates or returns created enrichment
Enrichments removed from get account endpoint
When external service providers are down, when accesing this resource, core attempts to recreate required objects. i.e. Create Card/Enrich should not fail if the external provider comes back up at a later time
Validate address country on create user to avoid invalid Alpha2 codes.
Update card 3DS does not use a mobile number anymore. Only the already verified mobile number can be used for 3DS
Address line 2 and state are optional in create/patch user
Physical cards cannot be activated unless they are dispatched first
Support for multiple IBANs per user. One user can have multiple EUR accounts and each of them enriched with a separate IBAN