AppFrontier

☰ Menu

Chase Orbital Salesforce Integration Chargent


Integrating Chase and Salesforce using Chargent


Overview

The Chargent Payment Processing for Salesforce application can connect Salesforce to both the Tampa and Salem versions of Chase Orbital, the payment gateway for Chase Paymentech, and process credit card and ACH payments through Chase directly from Salesforce.

1. Merchants with PCI DSS Attestation of Compliance (AOC)

Chase requires that merchants who have their own PCI DSS Attestation of Compliance (AOC) certify their individual integration with Chase Orbital, even though Chargent has a pre-built integration that is currently in use by many customers. The Chargent team can provide limited advice but is unable to assist with Chase certifications.

2. Merchants without PCI DSS Attestation of Compliance (AOC)

For merchants without their own AOC, you can connect to Chase Paymentech as your payment processor through other payment gateways, such as Authorize.net. Unfortunately certifying on the Chase Orbital gateway is not currently possible.


Chase Orbital Gateway Testing Cases for Salesforce certification


Certification Process


To get started on the Chase process, after signing an order form with AppFrontier for Chargent and the Chase Certification Setup Fee, you will just need to let your Chase Account Executive know that you are looking to connect Salesforce to the Chase Orbital gateway (Chase Paymentech processor) via Chargent. Chase requires that each of their merchants be certified, so let them know that we told you that you will need to do a merchant certification.

Chase will then send you a document to fill out called the Technical Profile Questionnaire for Orbital Gateway. We have completed many questionnaires for clients, and can send you back the document with many of the approximately 25 questions completed.

Once you return the completed document to Chase, they will send you back a document of some test cases to complete the certification, which basically involves sending a number of test transactions and recording the results.

Once all the test cases have been completed, Chase will certify your company and the Chase Integration Consultant will provide you with your Production Information Document, which will include credentials to send live transactions from Salesforce to Chase Orbital.

Setup for Certification

  1. Install both parts of Chargent Payment Processing for Salesforce into your Salesforce org.
    • Note that Chargent is a paid application, but it has a 30 day free trial.

  2. Configure Chargent according to the step by step documentation.

  3. Add a Gateway record for Orbital (Chase Paymentech) in Salesforce
    • Navigate to the Gateways tab in Chargent and click New

  4. Select Orbital (Chase Paymentech) as the record type from the list of pre-integrated payment gateway Salesforce integrations that Chargent offers.

  5. Chase Orbital Gateway configuration in Salesforce using Chargent


  6. Complete the Chase Orbital gateway record in Salesforce using the credentials supplied in the Chase Test Cases document.

    • Gateway Name: Any name you choose, for example "Orbital Certification"
    • Merchant ID: Connection Username
    • Merchant Security Key: Connection Password
    • Merchant Reference: Merchant ID Number (MID)

    • Orbital Platform: select BIN Number: 000001 or BIN Number: 00002 (this corresponds to the Chase Tampa or Salem systems)
    • Active should be checked
    • Test Endpoint should be checked
    • Click Save

  7. Create test records in Salesforce to run test credit card transactions
    (either Chargent Order, Opportunity, or Cases records depending on which Chargent Transaction package you have installed).

    • Billing First Name, Billing Last Name, Billing Address should match what Chase specifies
    • Total (or Amount if using Opportunities / Cases) should match what Chase specifies
    • Test Credit Card numbers should match what Chase specifies

  8. Alternately, you can also use a Salesforce data loader to create all the records needed for certification from a CSV file Contact AppFrontier support for sample CSV files with some sample test cases and column headings ready for import.

  9. Run the transactions as specified by Chase, and record the Auth Code, Decline Code and TxRefNum returned by Chase in the Certification document.
     
    These can be found in the Authorization Code, Response Message and Gateway ID fields respectively in the Salesforce transaction records.

  10. Note that Chase provides a large number of tests that need to be run, but you will only need to do certain sections of the tests, based on what Chase services you will be using (credit card, ACH, etc.). The beginning of the Test Cases document should specify which sections of testing your organization is required to complete.

    Endpoint Override for Chase Failover
    Chase requires a test of their failover server system, which requires a slight configuration change to run the certification tests. The normal server endpoints that Chargent integrates to, which are already set up as Remote Sites in your Salesforce settings, are as follows:

    Chase Orbital Live - https://orbital1.paymentech.net
    Chase Orbital Test - https://orbitalvar1.paymentech.net

    Chase merchant certifications will require that you send transactions to failover servers, such as:

    https://orbitalvar2.paymentech.net
    https://wsvar2.paymentech.net

    To run certification tests using one or both of these endpoints, simply use Chargent's Endpoint Override feature.

  11. Go to Setup > Security Controls > Remote Site Settings
    • Click New Remote Site
    • Enter the Remote Site Name and Remote Site URL (Chase Failover URL)
    • Click Save
    • Go to the Gateway Record you have set up for Chase
    • Enter the URL in the Endpoint Override field
    • Uncheck the Test Endpoint checkbox

    Using Chargent's Endpoint Override to connect to Chase Failover servers


    Setup for Testing / Production

    Once you have completed the certification and your Chase Integration Consultant has provided you with your Production Information Document, you can proceed with additional testing or move into production with live transactions.

    If you have not been provided with Test Account credentials and Test Credit Card Numbers for Chase, please contact your Chase Account Representative for assistance.

  12. Complete the Chase Orbital gateway record in Salesforce using the credentials supplied in the Chase Production Information document.

    • Gateway Name: Any name you choose, for example "Chase Orbital Live"
    • Merchant ID: Connection Username
    • Merchant Security Key: Connection Password
    • Merchant Reference: Merchant ID Number (MID)

    • Orbital Platform: select BIN Number: 000001 or BIN Number: 00002
    • Active should be checked
    • Test Endpoint should be checked until you wish to run live transactions
    • Click Save

  13. If you wish to test one or two live transactions with your own credit card, you can void them immediately after, to prevent the transactions from settling and capturing funds. Just go to the transaction record in Salesforce and click the Void button.

  14. Please keep in mind that Test Account Numbers should only be sent to the Chase Orbital test environment (Test Endpoint field should be checked in the Gateway record in Salesforce). If test numbers or test transactions are sent to the production environment, you will be responsible for transaction fees.

    Tokenization

    Chargent's Salesforce integration with Chase Orbital supports tokenization, which helps you meet PCI compliance and increase security, by storing data such as credit card numbers on Chase's servers, and relating it to a token Chargent stores in Salesforce for use in future transactions.

  15. To set up Chase Orbital Tokenization in Salesforce:

    • Confirm with your Chase Account Representative that your account is enabled for tokenization.
    • Check the Use Tokenization checkbox in the Chargent Gateway record you have set up for Chase

    • Set the Credit Card Handling field (unless you are using Payment Console)
      • Never Clear: Chargent will not remove any card data automatically.
      • Clear After Successful Charge: Chargent will clear the credit card number, expiration dates and card security code only after a successful charge is run.
      • Clear After All Transactions: The credit card number, expiration date and card security code will be erased after any approved transaction (Charge, Void, Refund)
      • Clear When Token Present: Only when a token is present in the token field, will the credit card number, expiration date and card security code be cleared.

    • When your first successful charge goes through, the Credit Card Number field value will be deleted, and a token will be stored for future transactions (or if you are using Chargent's Payment Console feature, the card number was never stored during the generation of the token)

  16. Congratulations! You have successfully integrated Salesforce and the Chase Orbital Payment Gateway using the Chargent Payment Processing for Salesforce software. You can now process one-time or recurring credit card payments through Chase directly from Salesforce.
     
    If you have any questions or need assistance, please contact us.