Our Cards UI is a white-label solution that allows you to present card information to the user without the need to store or transmit card information directly. This provides the benefit of handling stringent PCI Compliance standards for you.
At your backend, where you have stored
client_secret securely, issue a public key with scope
Issue an Issue OAuth Key for the user, with scopes
You can learn more about User Authentication on this page.
Next step is to go to the Cards UI and see if everything is rendering appropriately.
GET Params needed in the URL
OAuth key of the user who needs to link new card node
Your public key
Synapse ID of the node
If you are using debit card user interface with CARD-US nodes, the final URL would look like this:
If you are using debit card user interface with SUBNETS, the final URL would look like this:
If you are rendering this component inside an Android webview, please make sure that you have DOM storage enabled
You can update the color with any hex value. By default it uses our colors
Any landscape logo (recommended: 1388 × 367 pixels). By default it uses our logo
The link where the user will be redirected if actions are unsuccessful. Must follow Hypertext Transfer Protocol Secure (HTTPS) or Hypertext Transfer Protocol (HTTP).
Page Title for Unsaved Progress Warning
What title should go back warning page have
If the UI should display transactions associated with the card or not
If the UI should display the balance of the card or not
Cash In / Out Controls
If UI should allow the user should be allowed to add or withdraw funds out of the card or not
Card Number Controls
If the card number should be visible by default or hidden
If the UI should display the card preferences controls. This includes card status, card pin update, and foreign transaction controls.
If you wish to change any of these fields, please go to Client Manager on the dashboard to do so. (FAQ on how to get to the Client Manager).