Looks like your website has a bug - try entering a house number which is non integer (Like say B-123) Submission fails with error:
```
{"statusCode":400,"error":"Bad Request","message":"ValidationError","data":{"errors":{"houseNumber":["houseNumber must be a `number` type, but the final value was: `NaN` (cast from the value `\"B-123\"`)."]}}}
```
It's wrong to assume that a house number is always an integer. My address has an alphanumeric house number. I have been in apartments without a house number (Instead they may have an alphabetical name. Something like XYZ House)
Thanks for this comment. I had a similar problem with email verification assuming particular email formats. I really appreciate your pointing this out, I would not have found it on my own.
I removed the "house number" section in favour of on the "recipient address" section, and your comment makes me think it might be better to simply have text fields for Name / address / city / province / postal code rather than fields that are more complicated, because unless they are executed very well they might end up being barriers.
Looks like your website has a bug - try entering a house number which is non integer (Like say B-123) Submission fails with error: ``` {"statusCode":400,"error":"Bad Request","message":"ValidationError","data":{"errors":{"houseNumber":["houseNumber must be a `number` type, but the final value was: `NaN` (cast from the value `\"B-123\"`)."]}}} ```
It's wrong to assume that a house number is always an integer. My address has an alphanumeric house number. I have been in apartments without a house number (Instead they may have an alphabetical name. Something like XYZ House)