WooCommerce Chase Paymentech Certification Mode

#user-single .entry ol.questionnaire {margin-left: 1em;} ol.questionnaire li { margin-bottom: 10px; } .entry ul li img, .entry ol li img { margin: 15px auto; }This documentation provides a guide to the Orbital Certification for the Hosted Pay Page (HPP) process required by Chase Paymentech. In order to be certified to use this plugin and to receive production API credentials from Chase, you must complete the certification document Chase provides and submit it to Chase for review. Before getting started: If you don’t yet have a Chase Paymentech account, please follow this link to sign up for Chase Paymentech, which can speed up the on-boarding process for your account by indicating you use WooCommerce. Once you have received your test credentials from Technical.Implementations@Chase.com, be sure to configure both your Chase Paymentech account, and plugin as described in the plugin setup guide.

Certification Notes & Requirements

↑ Back to top

• To complete the certification process, you must ensure your site is publicly available, and that you’ve received the Orbital Certification document from your Chase representative.
• Ask your representative which sections are required for your account, as there are several versions of the test document and requirements differ.
• You must also be familiar with how WooCommerce payment gateways work, so you may want to review the plugin documentation if you’ve not used WooCommerce before.
• WooCommerce will assist with questions or issues specific to this plugin’s settings while completing the certification guide. Chase Paymentech will assist with questions or issues related to test cases or your Virtual Terminal account while completing the certification process.

As certification is a requirement imposed by Chase Paymentech, they are best suited to handle most issues about the process itself.

Certification Timeline

↑ Back to top

Once you’ve signed up for Chase Paymentech or notified them of your desire to integrate with WooCommerce using the Chase Paymentech extension, you’ll begin to receive information for testing your environment. The timeline we’ve been given by Chase for this process is as follows:

• Time to get Orbital Test Environment set up and get credentials from Chase so merchant can begin testing: up to 5 business days
• Time to complete test cases: approximately 45-60 minutes for basic transactions. For the advanced setup that allows your customers to securely save their credit card information of future checkout (required for full WooCommerce Subscriptions support), expect an additional 60-80 minutes of testing.
• Time for Chase to review test transactions when submitted: 5 to 7 business days
• Time until merchant is provided with production Orbital Connection Username following successful testing: within 5 business days

Below is contact information for Chase Paymentech Orbital Certification in case you have not received the relevant information 5 business days after signing up: Orbital Certification Support: Technical.Implementations@Chase.com

Enable Certification Tool

↑ Back to top

The plugin has a certification tool that helps you complete the Chase Paymentech test cases for Orbital certification. This tool has been updated in version 1.8 to provide broader support for the test documents Chase provides. The tool is not specific to a certain certification document version, so this requires you to manually set up and complete the transactions your document outlines. To use this tool, please:

1. Ensure the “Chase Paymentech” gateway is enabled at checkout.
2. Put the plugin in the “Test” environment
3. Enter the test credentials you’ve received from Chase. You only need a “Secure Account ID”, but if you want to allow customers to save cards (necessary for Subscriptions support), you’ll need the other credentials as well.
4. Enable “Certification Mode”

(The Pay Form Style URL can be left blank, this is not required.)

Ensure your store has a simple product for which you can submit test purchases. The price of this product does not matter, but your shop currency should be in USD. You’re now ready to use the certification tool, which adjusts the checkout form so that you can change the required transaction type, transaction amount, and add a test label easily.

Preview Test Cases

↑ Back to top

Chase Paymentech will provide you with a version of their Orbital Certification Document, which lists the test cases and responses you’ll have to submit for certification. You’ll go through your own checkout process and test different card numbers, transaction types, and amounts, then record responses from the plugin to submit to Chase. It is important that you familiarize yourself with this document before beginning test cases, and ask any clarification questions of your Chase rep. For example, if you do not plan to allow tokenization / saving cards, you can skip “Customer Profile” sections of the document. The test cases in the document may list a payment method type, transaction amount, address, or other information about the transaction that you will need to enter in the checkout process. You will then then process the transaction to get the required response information. Your test cases may look different than any screenshots in this document. In order to complete each section of the test cases, you must be familiar with some terms.

• Authorization – This means that a transaction is sent to Chase Paymentech, but funds are not immediately requested or transferred (until the charge is captured). Within the plugin, this is referred to as an “Authorization”, while transactions that settle funds immediately are called “Charges”. Chase Paymentech typically refers to authorizations as “store_auth”, “auth_only”, or “Authorization”. Chase typically refers to charges as “auth_capture” or “Auth/Capture”.
• Customer Profiles – When Chase Paymentech documents ask you to create a “Customer Profile”, this means that a WooCommerce customer with a saved payment method should be created. To do so, you’ll save the card to the account during checkout.
• Customer Ref Num – Chase refers to saved payment methods via Customer Ref Numbers, so this data will be shown on the “My Account” > “Payment Methods” page when the certification tool is in use (but not during normal test or production usage). This allows you to add the Customer Ref Num for transactions and test cases as needed.

You should also review all test cases that your Orbital Certification representative has specified as required before beginning the certification process to ensure you are familiar with requirements.

Perform Test Cases

↑ Back to top

You are now ready to perform your test cases. Please read through this entire section before beginning test cases. Each required test case will require you to run a transaction through the Chase gateway in your site’s checkout process. You must use the payment method, card number, amount, address info, and CVV supplied in the test case document for each transaction. You’ll then record the information displayed for you after checkout in the case document, such as AuthCode or Order ID. Regardless of which sections you do, there are some areas of the document that are not supported and should be skipped in your test cases:

• ChaseNet and electronic Check payments are not supported
• PinLess Debit and Gift Cards are not supported
• Bill Me Later is not supported
• Refunds, voids, and updating customer profiles require version 1.9 of the plugin or newer.
• You should be able to skip “Delete a Customer Profile” sections as well.

Testing Your Checkout

↑ Back to top

1. Open your store in a different browser or incognito window, and add your test product to your cart.
2. Proceed to the checkout.
3. You should log in as an existing customer, or create a new customer account with a US-based address for testing purposes.
4. When you get to checkout, enter the address specified for the test case in the checkout.
5. Select the Chase Payment method to use the certification mode tool.
6. If the test case is “Authorization” or auth-only, use this transaction type. If the transaction should be a charge or auth/capture, ensure that this transaction type is selected.
7. Enter the transaction amount for this case from your Chase test cases document.
8. Enter the test case identifier. If you’re in section A, on test case 1, we recommend entering A1 or A-1 in case you need to refer back to this order within your WooCommerce admin (the label you add here will be shown for reference).
9. Click “Continue” to go the payment form.
10. Enter the credit card number and CVV specified for the test case, and select the appropriate card type. The expiration date can be any future date. Click “Complete”.
11. When the payment is processed, the test case response values will be listed on the “Order Received” page. Paste the appropriate values into your test case document.
12. You can now click “Next Test” to move onto the next test case. This re-adds the previous product to the cart and takes you back to checkout immediately.

You can complete your test cases in any order. However, we recommend following a few tips, as you can combine efforts for some sections.

Test Cases Tips

↑ Back to top

While merchants can get several different versions of test case documents, there are some general tips that can be followed.

Test Case Order

You’ll typically begin your document under the “Test Cases” page. While the order can differ for the test case sections, we typically recommend using this rough sequence:

• Authorization transactions (store_auth, auth_only, or Authorization) – the first set is typically $0.00 or $0.01, we recommend doing these tests to start.
• Authorization again – this typically involves transactions of real values, like $100. These tests can be done, then the following section.
• Capture – When you move onto capturing tests, you can capture the charges from the previous authorization section in the admin rather than running through new transactions. See our notes here.
• Auth/Capture – These tests will require you to change the transaction type and charge the transaction. We recommend doing these test with the test cases on “Creating a Customer Profile” since they can be completed together. See our notes here.
• Refund – You can refund some pre-existing (already captured / charged) transactions to process refund tests, as WooCommerce lets you enter the refund amount before processing it.
• Authorization to Void/Reversal Testing – You can use the WooCommerce “refund” workflow to void transactions that have been authorized, but not captured. You’ll likely need to do some new “Authorization only” transactions for this.
• Create a Customer Profile Testing – For these tests, you can do them while doing the Auth/Capture transactions; you’ll need to enable “Securely save to account”. See our notes here.
• Using Customer Profile Testing – While doing this section, you can use the saved card from the previous step for the next transaction, provided you stay logged into this test customer account.
• Updating Customer Profile – This means you can add a card for an existing customer account via the account section’s “Add Payment Method” workflow.
• Negative Testing – These settings should use auth/capture (charge) for the transaction type.

Capturing Transactions Tests

↑ Back to top

There are some tests where you’ll capture previously authorized transactions. To perform a charge capture, you’ll view the order in your WooCommerce admin (the test case labels should help you identify the right one). Use the “Capture Charge” action under the order actions to perform this capture. This will perform the capture and add an order note for you with the response details to copy into your test cases document.

Refund and Void Tests

↑ Back to top

Both refunds and voids use the WooCommerce refund workflow to modify transactions. You can click the “Refund” action for an order, enter the required amount, and click “Refund via Chase Paymentech”. If the order was authorized, a void will be performed. If the order was already charged or captured, a refund is processed. You’ll see order notes that reflect this change:

Customer Profile Tests

↑ Back to top

To create customer profiles with Chase for testing, you’ll need to enable “Securely Save Card to Account” while completing the test case transaction. When saving a card (or using a saved card), the “Customer Profile ID” / “Customer Ref Number” will be shown in the response details to copy into your test case document. If you find that you need a customer reference number later, you can also see the reference number for each saved card from My Account > Payment Methods. To use the “Update Customer Profile” workflow, you can add a saved card to an existing account using the “Add Payment Method” action.

Inapplicable Tests

↑ Back to top

As we outlined above, some test cases may not be available; simply mark these as “N/A” in the certification test document. You can also do this for test cases that do not apply to you. For example, tokenization / saving cards may not be applicable to your store, and thus “Customer Profile” tests can be skipped.

Concluding Test Cases

↑ Back to top

Once you’ve finished the appropriate sections, you’ll be ready to submit these test cases to your Chase representative. Save your document with test case responses and disable the payment gateway. The document with test case responses must be sent to Chase for review – email this to the Orbital Certification Support: Technical.Implementations@Chase.com. Include your test merchant number for reference. Test orders will remain in your shop. We recommend leaving these until your live credentials come back from Chase in case there are issues, then bulk deleting these orders. If you leave certification mode enabled, these orders will remain marked with the test case for easy identification (even with the gateway disabled) so long as the plugin is active. You can trash, then permanently delete them, then move to production mode and re-enable your gateway.

Orbital Certification Questionnaires

↑ Back to top

Once you’ve submitted your test cases to Chase, you may need to fill out their questionnaires: “Technical Profile Questionnaire for Hosted Payment Solution (US) to Tandem” and “Technical Profile Questionnaire for Orbital Gateway to Tandem”. For each questionnaire, you’ll enter your store or business’s information. However, there are a couple fields you may not be sure about:

1. What is the physical location of your computer system and associated connectivity? List the IP of your shop’s server. You can ask your webhost for this if you’re not sure.
2. What Hosted Payment Solution will be used? [x] Hosted Pay Form (HPF)
3. List Production MIDs You receive this from the Chase team
4. List applicable test MID information You receive this from the Chase Integration team
5. Will order Abstraction (uID) be used? No
6. Will you create customer Profiles? Answer yes to this if you want to allow customers to securely save their credit card details for easy future checkout. If yes, [ ] Company/Chain [x] Division/MID
7. If creating profiles, how will they be created? (post value = hosted_tokenize) [x] store_authorize [x] store_only
8. What Transaction Types will be processed (post value = trans_type) [ ] auth_capture (Select this if you’ve configured the plugin “Transaction Type” option to be “charge”) [ ] auth_only (Select this if you’ve configured the plugin “Transaction Type” option to be “authorization”)
9. What Methods of Payment (MOP’s) will be used? Choose the card types you accept
10. What functionality will you use? [x] Full AVS for Zip Code format: [x] US [x] Card Security Value for MOP: (Choose the card types you accept)
11. Will you have a separate direct to Orbital integration? Yes if you answered “yes” to number 6 above, no otherwise
12. How will you specify End of Day for settlement? This is your choice, Chase Merchant Services can help you with this one
13. Who will be the application testing contact? Supply your contact info
14. Who is the Test VT user for Hosted Pay Page Admin Rights? Supply your contact info
15. When will you be ready to being application testing? This is your choice
16. Production Contact Information Supply your contact info

If you are tokenizing credit cards or saving other customer information via Chase, you may also have some additional questions. Here are some hints to help you out:

1. What is the physical location of your computer system and associated connectivity? List the IP of your shop’s server. You can ask your webhost for this if you’re not sure.
2. List applicable production Merchant ID(s) (12 digit number) You receive this from the Chase team
3. List applicable test MID information You receive this from the Chase Integration team
4. Please identify the integration option that you will use to send transactions to the Orbital Gateway. [x] Third Party Software Software vendor name SkyVerge, Inc. / WooCommerce Software version (get this from your “Plugins” page)
5. What protocol will be used for on line processing? [x] Not Applicable (not sending online authorizations)
6. What security authentication will you use for online processing? [x] User Name & Password at MID level
7. What protocol will be used for batch processing? [x] Not Applicable (not sending batch files)
8. S-FTP requires IP Security Authentication Skip: not applicable to WooCommerce plugin integration
9. Additional, S-FTP requires RSA Key or User Name & Password authentication Skip: not applicable to WooCommerce plugin integration
10. For batch processing and CSV file uploads, which file encryption will be used? Skip: not applicable to WooCommerce plugin integration
11. For CSV file uploads only, which method will be used to upload the file? Skip: not applicable to WooCommerce plugin integration
12. For CSV file uploads only, how will you receive the Closed and Reject Batch reports: Skip: not applicable to WooCommerce plugin integration
13. For Reporting only, at what level will the SFTP User be set up at? Skip: not applicable to WooCommerce plugin integration
14. What Request/Response Transaction Type Messages do you intend to test: [x] New Order (if you’ve configured the plugin for Tokenization support) [x] Mark for Capture (if you’ve configured the plugin “Transaction Type” option to be “authorization” and wish to capture payment from the WooCommerce Order Admin) [x] Profile (if you’ve configured the plugin for Tokenization support)
15. What industry type will be used? [x] EC
16. What currency will be used? [x] US
17. If you checked off New Order in Request/Response Transaction Type Messages (Question #14) complete this section:

    Credit Card Methods of Payment

    Choose the card types you accept

    Message Type

    [x] A (Authorization) (if you’ve configured the plugin “Transaction Type” option to be “authorization”) [x] AC (Authorization and Mark for Capture) (if you’ve configured the plugin “Transaction Type” option to be “capture”, OR “Transaction Type” is “authorization” and you want to capture authorizations from the WooCommerce Order admin)

    Functionality

    [x] Full AVS for Zip Code Format: [x] US [x] Card Security Value for MOP: (Choose the card types you accept, if you’ve configured the plugin “Require Card Verification” option to be true) [x] Customer Profiles: [ ] at Chain (Company) level[x] at MID (Division) level

18. If you checked off Mark for Capture in Request / Response Transaction Type Messages, complete this section: Choose the card types you accept, if you checked the “Mark for Capture” option in Question 14
19. If you checked off Reversal in Request/Response Transaction Type Messages (question #14), complete this section: Not applicable to WooCommerce plugin integration
20. If you checked off Gift Card in Request/Response Transaction Type Messages (question #14), complete this section: Not applicable to WooCommerce plugin integration
21. If you checked off Inquiry in Request/Response Transaction Type Messages (question #14), complete this section: Not applicable to WooCommerce plugin integration
22. If you checked off Profile in Request/Response Transaction Type Messages (question #14), complete this section: Choose the card types you accept, if you selected “Profile” in question 14
23. How will you specify End of Day for settlement? This is your choice
24. Who will be the application testing contact? Supply your contact info
25. When will you be ready to being application testing? This is your choice
26. Production Contact Information Supply your contact info

Troubleshooting & Issues

↑ Back to top

Chase occasionally sends merchants a “Secure API Token” with instructions like, “Use the Secure Account ID and API Token to authenticate your transaction requests from your Hosted Solution. Please refer to your shopping cart module or integration guide for instructions on implementing these security credentials.” This is not needed. Our integration only accepts the “Secure Account ID” and thus the API Token can be ignored.

---

If you have questions about your Chase account, the certification process, test credentials, or test case responses, please contact the Orbital Certification Support: Technical.Implementations@Chase.com If you experience issues while enabling the certification mode or do not receive the expected response codes, first please ensure that maintenance mode is not enabled and that your site is publicly accessible, as Chase must be able to send responses back to your website. If you experience other issues while using certification, please contact our support desk.