Virtual Cards

How to setup Virtual Cards in local development

This documentation is about development. To setup a production environment, see

Setup Stripe in development

On staging, is already configured to issue virtual cards. If what you're working on doesn't require any API changes, feeel free to use it directly.

The steps to configure Stripe issuing on your local setup are:

  1. Ask Stripe to enable Issuing on your account (if you're managing multiple accounts, make sure to pick the right account on top)

  2. Top Up the Issuing balance with a reasonable amount ($1000 ?, $10,000 ?)

  3. Create a generic Card Holder and make sure it's the only one (if you have more, let us know)

  4. Configure webhook and enable for all issuing_authorization.* and issuing_transaction.* (5 events)

  5. Configure default authorization process and webhook (deny or allow) (Optional)

  6. Create new dedicated Restricted Secret Key, select write for all Issuing features (Name: Restricted Issuing)

  7. Contact Open Collective Engineering team to configure Restricted Secret Key production (update-connected-account-stripe-token)

  8. Contact Open Collective Engineering team to configure Webhook Signing secret to connected account (stripeEndpointSecret)

  9. Ask Open Collective Engineering team to enable feature in Collective settings (privacyVcc)

Setup privacy in development

Privacy is deprecated and shouldn't be used for new developments

  1. Create an account on

  2. Go to, scroll down to "Enable API", toggle the switch, click on Sandbox and copy the Sandbox API key (NOT THE PRODUCTION ONE)

3. Connect to the database with your favorite tool (psql, DBeaver, Postico, etc.) and search for the host you want to enable Privacy for. Edit its settings to set features.privacyVcc to true

4. Open the host settings and go to the "Fiscal host settings" > "Sending Money" section

5. Paste your API Key in the "API Key" field and click on "Connect Privacy".

Last updated

Ⓒ Open Collective 2024