Multiple Entities Using Different Payment Gateways This is common for a single entity implementation of Nimble AMS, where an association has 1 payment gateway. To do this, an administrator can set up a single payment gateway with an entity payment gateway linking to your association's single entity. Single Entity Using the Same Payment Gateway Configuration Options When setting up payment gateway(s) for your entity payment gateway(s), there are a few different ways you can configure them to meet the needs of your association. Learn more about Hosted Payment Forms (external) and PCI Compliance (external) with BluePay . Understanding Hosted Payment Forms will help you understand the usage of Hosted Payment Forms across Nimble AMS or Community Hub. For more information, see Enable Hosted Payment Forms. To use Hosted Payment Forms with BluePay, an Administrator will need to enable the Hosted Payment Forms feature in your payment gateway. For the organization, using BluePay Hosted Payment Forms makes PCI compliance much easier than before, as the credit card data is not captured/stored on the Nimble AMS or Community Hub, and is directly entered on the Hosted Payment Forms and handled by the BluePay payment gateway for processing the order payments. If you are using the BluePay payment gateway, you can use Hosted Payment Forms to make a payment from the Hosted payment gateway. Users can now save the Credit/Debit cards and Bank Accounts on the Hosted payment gateway, and can use them in future during the checkout process. The BluePay Hosted Payment Forms provide users (Staff Users in Nimble AMS and Constituents in Community Hub) an enhanced user experience when using Credit/Debit cards and Bank Accounts (ACH). Learn more about Level 2 Processing (external) and Level 3 Processing (external) with BluePay. To use Level 2 or Level 3 credit card processing with BluePay, contact Nimble AMS Support. Learn more about the Payment Step and the Additional Processing Health Validation Message that may display in the Staff View order process. Using Level 2 or Level 3 payment processing, the Payment step in the Staff View order process displays an Additional Processing Health section which displays to staff whether a payment has all the necessary information to process a Level 2 or Level 3 payment, and if not, each piece of missing information. If you are using the BluePay payment gateway, you can use Level 2 (L2) or Level 3 (元) payment processing to send additional transaction data from Community Hub and Staff View to the payment gateway and lower processing fees for MasterCard® and Visa® transactions. Level 2 and Level 3 Credit Card ProcessingĬredit card payments in Nimble AMS typically include a minimal amount of transaction data that is passed to the payment gateway this is known as Level 1 (L1) credit card processing. Learn more about BluePay AVS (Address Verification) Filter (external) and Authorize.Net Address Verification Service (external). To use billing address verification with BluePay or Authorize.Net, an administrator will need to activate the billing address verification service (AVS) in the payment gateway. You can set your org up to use the billing address when verifying credit cards to provide a more secure and cost-effective credit card verification. Learn more about how BluePay secures stored payment methods (external) and how Authorize.Net handles profiles and payment profiles (external). Learn more about External Payment Profiles. No page found for the specified scroll page id. Error rendering macro 'excerpt-includeplus'
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |