Virtual cards can be offered to communities through Hosts. Hosts authorise and create virtual cards, assigning them to a Community administrator. Anyone with access to that card can then use it to make payments on behalf of the Community.
When a payment is made, an expense is automatically created for the Community; the owner is then notified to attach a receipt.
Virtual Cards are particularly useful for recurring payments like hosting a website.
Virtual Cards created using Donate PR will authorise transactions against the Community's balance in real-time. Cards additionally be configures with a number of spending controls to de-risk abuse.
Donate PR uses Stripe Issuing to manage virtual cards. We have extended support for Stripe that enables hosts to create, edit, pause, resume and cancel cards, including the option to automatically pause and resume cards with missing receipts.
Go to the above page, contact the Issuing sales team to get set up with Stripe Virtual Cards.
Ensure Stripe is connected to your account.
Stripe Issuing uses an Issuing Balance that is separate from currency balances held within Stripe. Virtual Cards use this balance when processing transactions. Be sure to add to your issuing balance regularly.
To access your virtual card settings and policy, go to your host's admin panel and open select 'Virtual Cards Settings' under your Fiscal Host Settings section:
It is possible to create and assign virtual cards to Communities without enabling users to request them.
Toggle the 'allow communities to request a card' option to allow Communities to request a card. Communities can request a Virtual Card by clicking Request a card from their profile page:
Hosts are notified of virtual card requests by email.
You can toggle this option to automatically send a reminder for charge expenses that were created but are still missing their receipts. These reminders are sent after 15 and 29 days the expense was created.
Hosts have complete control over when, how, and to who they provide Virtual Cards. Hosts can define their own policy in the 'Virtual Card Policy Information' area.
Virtual card policies are provided to users when requesting a card. They can contain a binding agreement if needed.
You can view all cards assigned to Communities from the Virtual Cards settings page. Here you can filter cards by Community:
Each card shows the name, status, assigned community, when the card was assigned and any limits set. The last four digits of the card are also shown. To view the full details of a card click 'view card details'.
Be aware of your surroundings when viewing a card's details as others may be able to see them.
Cards can be created from within Donate PR with Stripe Issuing. Read more about Stripe Issuing. Once connected, cards can be created from your Host Settings (Select 'Virtual cards' and 'create card') or from the 'actions' panel on a hosted community's profile page:
Select the Community to assign the card to (this is automatically filled if creating from a Community's profile page), the assignee, a name for the card and limit:
Virtual Cards issued with Stripe can be limited on a daily, weekly, monthly or yearly basis. They can also be limited on a per-transaction basis or assigned a total spending limit (all time). Read more about Stripe's spending controls.
Hosts can toggle this option from the Virtual Card Settings if they wish to automatically pause virtual cards after an expense is missing its receipt after 31 days. Cards will resume once all missing expenses are submitted.
Cards issued with Stripe Issuing's details, including 'assignee', name, and spending limits can be edited from the Virtual Card View. It is not possible to re-assign a virtual card to another Community.
Cards issued using Stripe Issuing can also be paused, resumed and cancelled from the Virtual Card View. Cards paused, resumed and cancelled directly through Stripe will be synchronised. \
Card transactions appear in the assigned Community's expenses.
Expenses that are authorized will debit the community's balance and appear as PROCESSING until the card is charged, at which time the expense will be marked asPAID. Assignees are able to upload a receipt to expenses that are still processing.
If the authorization is cancelled before there's an actual charge, we simply delete the expense. If the purchase is refunded, a new refund transaction to be added to credit the amount back to the community and the charge expense will be set to "CANCELED".
Last updated
