Choose a payment processor
Choose a payment processor
To start accepting payments, you need to activate a default payment processor. Peoplevine supports a variety of payment processing providers to facilitate transactions.
Please note that Peoplevine offers two core front-end products:
Enterprise
React
If you're unsure which product you are using, please ask your Sales representative or Account Manager for clarification.
Authorize.net (Enterprise only)
Start by setting up an Authorize.net account here.
With Authorize.net you can accept payments via ACH / eCheck
Follow the steps here once your account is approved.
Card Connect (Enterprise only)
Visit https://peoplevine.com/payments to start the process
Rates at 2.75% or less
Double tokenization for utmost security
Stripe (React and Enterprise)
Visit www.stripe.com to sign up
When in Stripe, choose "integrated by another platform" and put Peoplevine
Stripe supports credit card payments only
They are integrated strictly as a processor and no customer data or other info is shared with them. Peoplevine is the platform to manage all your billing, customers, etc. Follow the steps here once your account is live.
GoCardless (React and Enterprise)
Visit https://gocardless.com to sign up
Make sure that your GoCardless account is a Pro account so that you can leverage the full white-labelled experience.
In the Developers tab, create a new access token for Peoplevine and choose "read-write access"
Follow the steps here once your account is live.
Adyen (EU (Enterprise only)
Visit https://www.adyen.com/ to sign up
To get your API Key, login to Adyen, click on Account and then API Credentials under Configure.
Follow these steps once your account is live.
PayPal (Enterprise only)
currently only available for eCommerce checkout (you must also have one of the providers enabled too) Follow the steps here to configure PayPal in Peoplevine.
Link your payment processor to Peoplevine
Link your payment processor to Peoplevine
Once you have setup your payment processor, log into Peoplevine, and navigate to the control panel by click the ⚙ cog icon on the right hand side.
Select Payment Processors under Settings and Tools.
From this panel you will be able to select your payment processor and connect it to your Peoplevine account to begin processing payments.
Use multiple payment processors
Use multiple payment processors
Peoplevine allows you to use multiple payment processors by assigning a processor to a specific area of your business. In order to setup a second payment processor you will need to follow the above steps.
Default payment provider = all payments will be processed via this processor
Membership dues & house account = subscriptions/ renewals and any open checks closed from a 3rd pty platform as an invoice to a house account (charged either on the 5th of the follkowing month or when you choose to manually).
3rd Party = POS, PMS, Spa and other integrations that close checks to a customers CRM profile
Additional = allows you to capture additional payment methods and use as a back up in case the default fails.
Additional settings
When using the 'Force Payment' option, it will route all payments to that processor (therefore if it's on a Default it will force everything to that one processor). So ONLY check this box if you have multiple payment processors but want to redirect all payments to one. E.g. "I want all F&B to go to Stripe." or "I want all Dues to go to GoCardless", otherwise please keep the box unchecked.
Split Payments
Split Payments
Leverage split payments to automatically split the payment to be processed amongst multiple processors. This can be useful if you have a smaller business within a larger entity or an agreement between two different departments in your business.
Once you've setup the main processor, you can link to it below. Contact our Support team for further information
PCI compliance
PCI compliance
If you are enabling payments within Peoplevine you will need to become PCI compliant with your payment processor. They will setup a monthly scanning to ensure you achieve this status.
When they scan, you may fail due TLS v1.0 Supported, which is something that is fairly common these days. This is because most web servers and SSL certificates must work with older browsers. According to PCI 3.1 guidelines, you are able to get an exception until June 30th of 2018. To apply for that exception, please follow these steps: (please note these directions may be different depending on who is scanning your web site).
Login to the PCI Compliancy portal
Click on Documents and upload a word document on your company's letter head with the following letter (below). Call the document PCI Compliancy Risk Plan.
Then click on Scanning and then Scan Results to see your last results
Select the TLSv1.0 Supported vulnerabilities and click on Dispute Finding
Select I am disputing this finding for another reason.
Mention that you have uploaded your PCI Compliancy Risk Plan.
Dear Sir or Madam:
Please accept this as the Risk Mitigation and Migration Plan for PCI DSS 3.1 for . A description of where and how we are currently using SSL and/or early versions of TLS, how we intend to mitigate the risks with these technologies, and our migration plan are listed below. 1. Where are SSL/TLS 1.0 currently used in your environment?We are not aware of any pages in our platform that is using TLS 1.0. All of our transactional pages in our platform and user authentication are being routed through our https version which uses a Go Daddy SSL Certificate and TLS 1.2.2. How are you mitigating risks with SSL/TLS 1.0?We have ensured that our SSL certificate and server settings in Microsoft Azure are using the latest SSL/TLS protocols. As you can see in our SSL certificate settings, the connection uses TLS 1.2.
3. How are you monitoring for new vulnerabilities associated with SSL/TLS 1.0? We receive alerts when our platform is penetrated via Azure Monitoring.4. How are you ensuring that SSL/TLS 1.0 are not introduced into your cardholder data environment? (Meaning, how can you verify that new or upgraded systems connected to your cardholder data environment don’t contain SSL/TLS 1.0?)We have complete control over the software and what is integrated into our software.5. When will your migration plan from SSL/TLS1.0 be completed? We are dependent on Microsoft Azure removing this from their environment. In the event they don’t remove it for Azure Apps by 2018 we do have the ability to migrate to virtual machines. Sincerely,