Pervasive DataSolutions Logo
Welcome GuestLogin
RSS

Navigation





Quick Search
»
Advanced Search »

PoweredBy



Remote Site Authorization

Without authorizing Pervasive DataCloud, Integrated Credit Card Processor will not be able to authorize credit cards.

While logged into Salesforce, click on 'Setup' located at top-right of screen.
Image


Within the left hand sidebar (towards the bottom), find a header titled 'Administration Setup' then below, find and click the expandable menu called 'Security Controls' and click 'Remote Site Settings' near bottom of the list
Image

Within the main content area, click 'New Remote Site'
Image


Enter the 'Remote Site Name' as 'DataCloud' and enter Remote Site URL: 'https://datacloud2.pervasive.com' then click 'Save'
Image



Integrated Credit Card Processor(ICCP) Configuration

Click on the '+' tab, then click the 'ICCP Configuration' link
Image


You will be presented with the ICCP configuration screen which is comprised of 3 sections:

    * Step 1 - Obtaining a Connection ticket with Intuit Merchant Service
    * Step 2 - Pasting the Connection ticket for Pervasive to user
    * Step 3 - DataCloud Credentials


Image


Step 1 - Click "Create New Connection Ticket."  A new window will open requiring you to enter your login information for Intuit Merchant Service.
Image


Step 1 (continued) - You will be presented with a connection ticket. Copy the connection ticket and navigate back to the ICCP Configuration tab in Salesforce
Image


Step 2 - Paste the ticket value into the box provided in the ICCP Configuration tab in Salesforce.com
Image


Step 3 - Enter your Pervasive/DataCloud username and password(you received this when signing up for ICCP) and click on "Show Settings."
Image


The service will log you into Pervasive DataCloud and you will be presented with an area to enter your Salesforce.com Username and Password. Enter a Salesforce.com admin's credentials and click "Save Settings."
Image


The DataCloud and Intuit Merchant Service are now configured.  Next we'll modify Salesforce a bit to display the buttons and objects necessary


Click on 'Setup'
Image

Within the left hand sidebar, find a header titled 'App Setup' then below, find and click the expandable menu called 'Create' and click 'Objects' from within that list.
Image

In the main area, click the 'Payment' link
Image



Navigate down to the 'Standard Buttons and Links' section which resides between 'Triggers' and 'Custom Buttons and Links.'

Next to 'View,' click the 'Edit' link
Image

Confirm the 'View' Label and Name at the top.  Select the 'Visualforce Page' radio button.  Then select 'ProcessPayment' and click 'Save'
Image


In the same 'Standard Buttons and Links' section, next to 'New,' click the 'Edit' link
Image

Confirm the 'New' Label and Name at the top.  Select the 'Visualforce Page' radio button.  Then select 'NewPayment' and click 'Save'
Image

Confirm that you have Overridden the View and New buttons properly
Image



We've made the proper overrides to the Payment Object, now we need to do so for the Recurring Payments Object

Within the left hand sidebar, find a header titled 'App Setup' then below, find and click the expandable menu called 'Create' and click 'Objects' from within that list.
Image


In the main area, click the 'Recurring Payment' link
Image


Navigate down to the 'Standard Buttons and Links' section which resides between 'Triggers' and 'Custom Buttons and Links.'
Image

Next to 'New,' click the 'Edit' link
Image


 Confirm the 'New' Label and Name at the top.  Select the 'Visualforce Page' radio button.  Then select 'NewRecurringPayment' and click 'Save'
Image

The configuration is now complete. Please refer to the User Guide for details on how to use the product.
Previous←Installation Next→User Guide


Copyright © 2009 Pervasive Software, Inc. All Rights Reserved. All Pervasive brand and product names are trademarks or registered trademarks of Pervasive Software Inc. in the United States and other countries. All other marks are the property of their respective owners. Your transaction secured by high-grade AES-256 encryption.