Rize Route Configuration
Last updated
Last updated
Linker uses VGS integration with Rize to protect sensitive information over 2 endpoints: /baas/customer-enrollment and /baas/debit-cards/:id/activate.
For both endpoints, you have to configure the necessary route rules in VGS. To facilitate this process, VGS lets you import YAML files with rules.
To import the YAML files provided to you when you have Rize + VGS, you have to go to the VGS Routes section and select under the Manage button the "Import YAML file" option.
To test VGS locally you have to expose a public URL. For that, we will use Ngrok.
Run the Linker API and start Ngrok with ngrok http 3000. This command will expose port 3000, which is the one used by default on Linker.
Now go to the Routes section in VGS dashboard, and select the "rize - inbound" rules, which are in Inbound Routes. There you have to change the Upstream Host with the Ngrok forwarding URL, and finally save the changes.
Once done, go to the Log section in VGS dashboard, and press the "Record payloads" button to see more details about the requests.
Now, if you test the API in Postman using your VGS inbound URL instead of the base URL, the sensitive data from {{baseUrl}}/baas/customer-enrollment and {{baseUrl}}/baas/debit-cards/:id/activate should be tokenized by VGS, and our API will only see the tokenized version of the sensitive data.
/baas/customer-enrollment: for this endpoint, the SSN is tokenized.
/baas/debit-cards/:id/activate: for this endpoint, the CVV is tokenized.
