jonasbark

The postal code is indeed a requirement for united states, so I'm wondering why you are setting enablePostCode: false then? I'm not surprised that the complete is false when the...

Indeed the card form has to still be displayed on the screen in order to use its data.

Indeed the library (or the react native library for that matter) only supports a single instance at a time. Though we may be able to support multiple ones with a...

Are you using the handleURLCallback from 5.0.1?

@asaarnak it's been merged, but not released as of yet. We will release a new version once they do.

Something like the mentioned snippet could also improve authorization with Spring security e.g. like this: ```kotlin POST("/api/todos") .withValidBody() .withRole("ADMIN") // could internally adjust ServerHttpSecurity rules ... ```

Thank you @kueblc - it works very well!

if anyone stumbles upon this: the token needs to be the combination of the region (e.g. EU) + token + secret, as described in https://github.com/ct-Open-Source/tuya-convert/blob/master/scripts/smartconfig/smartconfig.py#L47

> Any idea why CI is failing with these changes? I honestly wish I would have an idea.

Couldn't this cause [PCI compliance](https://stripe.com/docs/security/guide#validating-pci-compliance) issues, as sensitive data is sent through the React Native wrapper? With Flutter we developed a similar functionality, but we hid it behind a `dangerouslyUpdateFullCardDetails`...