A payment gateway is required in order to accept credit and debit card payments within Vega and through widgets on your website. The payment gateway will process the credit card details and settle funds into your bank account.
Before setting up a gateway for the first time, we recommend reviewing the knowledge base article for your gateway to confirm the correct settings and requirements are set. Stripe is the preferred gateway for Vega and they offer a non-profit rate on their fees.
You can connect to a gateway from Admin > Payment Gateway. Please note that you will need an administrator to set this for your organisation.
For New Zealand customers, the main suppliers are:
If you don't currently have a gateway, you may apply for one by clicking on the links above.
To set up your payment gateway:
- Go to the ‘Admin’ Section in Vega (If you cannot see this on your main top menu bar, you may not have the authorisation to access it, and will need to seek permission from your System Administrator)
- Click ‘Payment Gateway’ from the menu on the left-hand side
- Select the provider from the dropdown and click Add
- Depending on your chosen gateway, different information will need to be entered to set this up.
If your organisation is using a payment gateway not listed above, please contact us at email@example.com to discuss how we can help.
Changing payment gateways
Multiple payment gateway credentials can be saved within Vega however only one gateway can be used for all payment processing.
Vega stores tokenised card data only, with the credit card details being stored with your payment gateway provider. If you have saved cards or recurring payments which you would like to maintain, you will need to contact your payment gateway provider regarding your options.
Vega does not store, transmit or process credit card details, rather credit card details are tokenised by your payment gateway. These tokens are the way that the payment gateway identifies the credit card to charge. Vega does not 'save' the credit card details rather it saves the token provided by the payment gateway. When we want to charge the card we give them the token & they charge the card.
The only detail we store in the Vega database is the token generated by the payment gateway and the snapshot or mask they send back to us you see in both, the add payment form and the payment method within the Contact dashboard.
The mask or snapshot from the payment gateway is displayed in two different forms:
XXXX XXXX XXXX 5555 OR Visa5586
We hold this info so if the supporter queries the payment we have some info to go on, overall for users with no Admin access to the Payment Gateway portal. The token id is also an efficient way to find the payment in your payment gateway.