Using CardPointe

To allow you to accept and account for payments, administrators can set up the CardPointe payment gateway for an entity in your org.

If you are migrating from another Payment Gateway (such as BluePay) and currently use Saved Payments or Scheduled / Recurring Payments then you will need to migrate those Saved Payment tokens to the new CardPointe gateway. Please reach out to our Customer Success Team to plan this activity.

Prerequisites

This feature requires a CardPointe account. Customer CardPointe accounts are provided through the Community Brands Payments Team.
The CardPointe Gateway requires the installation of the CardPointe package. If it is not available, contact Nimble AMS Support.

Once a CardPointe Account has been created, you should have access to the following information:

CardPointe Transaction Key
CardPointe Account ID
Merchant ID

Configure CardPointe

To view the CardPointe Payment Gateway record type, assign Nimble AMS Cardpointe permission set to the user(s) who will be configuring it.
Ensure that the Page Layout Assignments have a Card Pointe Layout.

See how to do this

Click on Setup (gear icon) from the top-right of the page.
From Setup, navigate to the Object Manager, and enter Payment Gateway in the Quick Find box.
Select "Payment Gateway" from the search results.
From Page Layouts, select Page Layout Assignment.
Click on the Edit Assignment option.
Choose the cell that crosses the System Administrator profile and Card Pointe record type.
Select Card Pointe Layout from the Page Layout To Use dropdown.
Click Save to apply the changes.

Repeat the above steps if you want to apply this layout to other profiles as well.

In the tab bar, click the App Launcher, or in Salesforce Classic, click +.
Click Payment Gateways.
Click New.
Select the Record Type, as Card Pointe.
Enter information:
1. In Gateway Implementation, enter namz.CardPointePaymentGateway.
2. In Merchant ID, enter the CardPointe Merchant ID.
3. Login Id, enter the CardPointe login ID/Account ID.
4. Transaction Key, enter the Transaction key for the CardPointe account.
5. In Endpoint URL, enter http://fts.cardconnect.com/
Set Status to Active.
If you want to use Level 2 or Level 3 credit card processing, in Additional Processing Level, select the level you want to use.
If you want to require the CVV (Card Verification Value) code when making a credit card payment in Staff View, select Require Credit Card Security Code.
If you want to prompt staff to enter the address of the account when entering a payment, select Display Credit Card Address.
Click Save.

Step 2: Verify the Remote Site URL

The user must ensure that the Remote Site URL matches the Cardpointe Endpoint URL.

From Setup, enter Remote Site Settings and in the Quick Find box.
Select Remote Site Settings.
Click CardPointe.
1. Remote Site URL: Ensure that the Remote Site URL matches the Cardpointe Endpoint URL.

Step 3: Linking the Payment Gateway with the Entity

From a payment gateway, in the Entity Payment Gateway Links related list, click New Entity Payment Gateway Link.
Payment Gateway is set to the name of the payment gateway.
In Entity, enter the name of the entity that receives payments using the payment gateway, click, and select the entity.
Select Default to use the selected payment gateway when making payments, refunds, and managing stored payment methods.
Click Save.

Testing

CardPointe does not support a Test Mode. If you wish to test functionality while using CardPointe, you must use the Nimble AMS UAT Account. This Account information will be provided to you after you are onboarded to CardPointe.

IMPORTANT - Ensure Transactions are <$1000 or >$2000

The Cardpointe UAT Account used for testing has “Amount Driven Response Codes” enabled.

This means that any transaction between $1,000 and $2,000 can result in a declined transaction due to CardPointe returning a specified Response Code.

Learn More: Amount Driven Response Codes