Understanding Hosted Payment Forms
Hosted Payment Forms allows associations to reduce their PCI liability. The credit card data is entered by Staff Users and Community Hub users on payment forms securely hosted by BluePay. This provides a higher level of security, reduces merchant liability and makes sure that credit card data never touches the Nimble AMS system infrastructure. Using Bluepay Hosted Payment Forms makes PCI compliance much easier than before, as the credit card data never touches the system and is directly passed to and handled by BluePay.
Note
As of now, Nimble AMS does not support Hosted Payment Forms with CardPointe Payment Gateway Integration.
With Hosted Payment Forms, Staff Users in Nimble AMS and Constituents in Community Hub enter Bank Account or Credit/Debit Card details on the BluePay hosted payment pages to process electronic payments.
Users can also save payment details to save time in placing orders in future. As per the PCI Compliance Statement, the payment details will be stored on BluePay gateway and not on Nimble AMS.
When the Hosted Payment Forms are enabled by an Administrator:
- All Staff View credit/debit card and Bank Account transactions will go through BluePay Hosted Payment Forms.
- All Community Hub credit/debit and card Bank Account transactions will go through BluePay Hosted Payment Forms.
- There is the ability to store Bank Account or Credit/Debit Card details on the Store Payment Methods and can be used during the checkout process for later purchases.
On Staff View
User experiences the Hosted Payment Forms at the below scenarios:
Create a New Stored Payment Method
Select a Payment Method while paying for an Order
On Community Hub
User experiences the Hosted Payment Forms at the below scenarios:
Create a New Stored Payment Method
- Select a Payment Method while paying for an Order
Ready to Enable Hosted Payment Forms?