Stores connected to X-Payments Cloud can be configured to use payment processing via Intuit QuickBooks Payments.

Features of Intuit QuickBooks Payments

Feature

Supported?

Description

Sale

Supports transactions of 'Sale' type (Authorization and capture actions are completed simultaneously at the time of payment processing)

Auth

Supports transactions of 'Auth' type (An authorization hold is placed on the amount approved by the buyer to ensure the availability of funds for capture)

Capture

Partial transactions supported

Allows capturing the previously authorized amount (The authorized amount is moved from the buyer's account to the account of the merchant)

Void

Allows removing an authorization hold from the buyer's account by the merchant

Refund

Partial transactions supported

Allows issuing refunds (The money is returned to the buyer's account)

Get Status

Can provide information about the status of a transaction to X-Payments Cloud

Get Card

Can provide new/updated information about a saved credit card. For example, if a credit card gets re-issued, it is possible to get the renewed expiration date. If any other information changes, like the credit card number or the billing address, it is possible to access this updated credit card information as well.

Accept

Allows accepting transactions with a higher likelihood of risk

Decline

Allows rejecting transactions with a higher likelihood of risk

Test

Can test whether the merchant account details entered in X-Payments Cloud are valid

3D-Secure via
Cardinal Commerce

Supports 3-D Secure payer authentication via Cardinal Commerce. Best for PSD 2 in the European Union.

Tokenization

Supports tokenization (Allows billing a customer's credit card again - without X-Payments Cloud storing cardholder data).

Account Updater

Supports Account Updater service

Apple Pay

Supports Apple Pay

Google Pay

Supports Google Pay

Other payment methods supported by X-Payments Cloud are listed in the section X-Payments Cloud: Supported Payment Methods.

Configure Intuit QuickBooks Payments

Prerequisites:

  • You need to have an account with Intuit QuickBooks Payments.

  • You need to have an account with X-Payments Cloud.

  • Your X-Cart store needs to be connected to your X-Payments Cloud account. The connection can be made using the X-Payments Cloud connector add-on. Detailed information on setting up the connection is available here. Getting Started info for X-Payments Cloud is available here.

To enable payments via Intuit QuickBooks Payments in X-Payments Cloud, complete the following steps:

  1. On the X-Payments Cloud settings page, select Settings > Payment processing.

  2. From the 'Add a payment gateway' dropdown box, select "Intuit QuickBooks Payments".

  3. Click Add.

  4. On the page that opens, adjust the settings for your Intuit QuickBooks Payments payment configuration.

    You will need to obtain some credentials on the Intuit QuickBooks Payments end (Client ID, Client Secret, Refresh Token and Access Token). See further below on this page for instructions.

  5. After adjusting the settings as required, save your changes. Make sure the payment configuration you have added is active (enabled).

How to obtain the credentials needed to configure Intuit QuickBooks Payments in X-Payments Cloud:

  1. Go to https://developer.intuit.com/app/developer/myapps and click the + Create an app button in the top right-hand corner of the screen.

  2. On the page that opens, choose the platform "QuickBooks Online and Payments".

  3. Give your app a name. In the field "Select a scope", select the check box for "Payments".

    Your app management panel opens.

  4. On the app management panel, locate your Client ID and Client Secret. Copy and paste these credentials into the appropriate fields of the Intuit QuickBooks Payments configuration in X-Payments Cloud.

  5. Use the "OAuth 2.0 Playground" to obtain your Access Token and Refresh Token. Follow the instructions from https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/oauth-2.0-playground#get-the-access-token

Did this answer your question?