Process a payment

This is a guide to creating an eCommerce integration with QuickBooks Online and Payments APIs, showing:

• End-to-end payment processing via credit card or eCheck
• Automatic payment transaction and fee reconciliation
• Customer and inventory list management

This guide is for developers who want to implement an eCommerce app. The QuickBooks Online entities used in this exercise are Sales Receipt, Customers, and Items for QuickBooks Online API and Charges and Tokens for Payments API. To get the most out of this information, you need the following:

• An app on developer.intuit.com enabled for both QuickBooks Online and Payments APIs.
• A QuickBooks Online sandbox company. See Sandboxes.

For this scenario, your sandbox serves as the QuickBooks company that manages the transaction where Pye’s Cakes buys twenty sprinkler pipes from the merchant. All moving parts for this transaction are explored for both credit card and eCheck processing.

For the complete cycle of a merchant service credit card or eCheck transaction, corresponding QuickBooks sales transactions, and settlement reconciliation to work properly, it is critical that the Payments connection and QuickBooks connection be on the same companyId. This is typically accomplished by ensuring that when you request an OAuth access token and secret you provide the complete picture of what your user expects your app to be doing with QuickBooks data sources. In your OAuth authorization implementation, make sure your call to setup() enables both quickbooks and payments data sources.

When your user changes their settings to turn on a new part of your integration with QuickBooks, initiate a subsequent request for a set of OAuth access token and secret to ensure that the correct services are set up on the company for your application. The worst possible situation would be for you to transact using a payments account set up for one company, while syncing the corresponding business transaction to a completely different QuickBooks company. Reconciliation will fail at best, and at worst, you are transacting for one business using the payments account of another business (albeit owned by the same user), which is fraudulent use of the QuickBooks payments service and can lead to service disruption for the merchant.

The following steps describe how to process a credit card transaction. The figure below shows the overall merchant ordering process:

Accept the order from the customer and request credit card details.

Order: 20 sprinkler pipes at $4 each = $80.00

Use customer information once or save, based on the merchant’s business model. To save, create an account and store details in the Customer object and credit card details in the Payments API Cards object (opaque to merchant).

This section shows how to submit a credit card charge to QuickBooks Payments via the API, without the need to swipe the physical card. There are three steps:

1. Create a token: Your app’s browser code collects credit card information on behalf of the merchant and sends the token request, resulting in an opaque container to use in the subsequent charge request. In this way, your servers are immune from seeing or storing any credit card information.
2. Authorize the purchase: The first half of the credit card transaction. Before shipping the product, the merchant receives authorization from the credit card issuer that the merchandise will be paid. The card has not been charged yet.
3. Capture the transaction: The second half of the credit card transaction. After authorization, you ship the product and then submit the charge for processing. This is called “capturing the charge.”

First, create a token to keep CC info opaque from you, the developer. Become informed about handling payment information.

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16

{
   "card": {
      "expYear": "2017",
      "expMonth": "03",
      "address": {
         "region": "NJ",
         "postalCode": "07079",
         "streetAddress": "350 Mountain View Dr.",
         "country": "US",
         "city": "South Orange"
      },
         "name": "Pye's Cakes",
         "cvc": "123",
         "number": "4111111111111111"
   }
}

View Sample Response

1
2
3

{
   "value": "4ALvl3ZJZESJwjiQr6vQQCfDz74="
}

Now create a charges authorization using the token created in the last section. Lifetime of a token is 15 minutes and is for one time use. This is the first half of a credit card transaction, with the charges.capture attribute set to false, and is used to get authorization that the merchandise will be paid by the card issuer.

Sample Request

1
2
3
4
5
6

{
   "amount": "80.00",
   "currency": "USD",
   "capture": "false",
   "token": "4ALvl3ZJZESJwjiQr6vQQCfDz74="
}

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

{
   "created": "2015-04-23T19:51:48Z",
   "status": "AUTHORIZED",
   "amount": "80.00",
   "currency": "USD",
   "token": "4ALvl3ZJZESJwjiQr6vQQCfDz74=",
   "capture": false,
   "id": "ECZG9D8YZ2WY",
   "authCode": "817677"
}

At fulfillment time, capture the charge.

Sample Request

1
2
3

{
   amount: 80.00
}

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

{
   "created": "2015-04-23T19:51:47Z",
   "status": "CAPTURED",
   "amount": "80.00",
   "currency": "USD",
   "card": {
      "number": "xxxxxxxxxxxx1111",
      "name": "Pye's Cakes",
      "address": {
         "city": "xxxxxxxxxxxx",
         "region": "xx",
         "postalCode": "xxxxx",
         "streetAddress": "xxxxxxxxxxxxxxxxxxxxx"
      },
      "expMonth": "03",
      "expYear": "2017"
   },
   "capture": false,
   "id": "ECZG9D8YZ2WY",
   "context": {
      "tax": null,
      "recurring": false,
      "deviceInfo": {}
   },
   "authCode": "817677",
   "captureDetail": {
      "created": "2015-04-23T19:53:43Z",
      "amount": "80.00",
      "context": {
         "tax": "0.00",
         "recurring": false,
         "deviceInfo": {}
      }
   }
}

The following steps describe how to process an eCheck transaction. The figure below shows the overall merchant ordering process:

Accept the order from the customer and request eCheck details.

Order: 20 sprinkler pipes at $4 each = $80.00

Use customer information once or save, based on the merchant’s business model. To save, create an account and store details in the Customer object and bank account details in the Payments API Bank Account object (opaque to merchant).

Submit an eCheck transaction to QuickBooks Payments via the API. There are two steps:

1. Create a token: Your app’s browser code collects eCheck information on behalf of the merchant and sends the token request, resulting in an opaque container to use in the subsequent charge request. In this way, your servers are immune from seeing or storing any eCheck information.
2. Submit the payment for processing. This is called “capturing the payment.”

First, create a token to keep eCheck info opaque from you, the developer. Become informed about handling payment information.

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

   {
      "bankAccount": {
         "name": "My Test Bank ",
         "accountNumber": "11000000333456781",
         "phone": "6501234567",
         "routingNumber": "322079353",
         "accountType": "BUSINESS_CHECKING"

      }
   }

View Sample Response

1
2
3

{
   "value": "45cceb7b-8efc-47fd-9d83-202c0aa8d8d9"
}

At fulfillment time, capture the charge.

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

{
   "amount":"0.99",
   "token":"98873340-d51a-4d44-91dd-e073d388fcc0",
   "context":{
      "deviceInfo":{
         "id":"1",
         "type":"type",
         "longitude":"longitude",
         "latitude":"",
         "phoneNumber":"",
         "macAddress":"macaddress-intuit",
         "ipAddress":"test124"
      }
   },
   "paymentMode":"WEB",
   "checkNumber":"01102025",
   "description":"Sandbox test ACH/echeck"
}

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

{
   "id": "a9xtnkyl",
   "authCode": "769-357",
   "created": "2025-01-10T20:16:06Z",
   "status": "PENDING",
   "amount": "0.99",
   "token": "98873340-d51a-4d44-91dd-e073d388fcc0",
   "bankAccount": {
      "name": "My Test Bank",
      "routingNumber": "xxxxx9353",
      "accountNumber": "xxxxxxxxxxxxx6781",
      "accountType": "BUSINESS_CHECKING",
      "phone": "6501234567",
      "inputType": "KEYED"
   },
   "context": {
      "deviceInfo": {
         "id": "1",
         "type": "type",
         "macAddress": "macaddress-intuit",
         "ipAddress": "test124",
         "longitude": "longitude"
      }
   },
   "paymentMode": "CCD",
   "checkNumber": "01102025",
   "description": "Sandbox test ACH/echeck"
}

After receiving and processing the charge create response, create the sales receipt.

• The minimal sales receipt request must include a Line.SalesItemLineDetail sub-object.
• Include a reference to the Customer object corresponding to the customer, according to your business process. The same code below creates objects for the sandbox customer, Pye’s Cakes.
• The app must have the Payments data source enabled.
• Do not create two sales receipt objects with the same CreditCardPayment.CreditChargeResponse.CCTransId.

When creating the sales receipt, set up the sale to be automatically reconciled with the QuickBooks company account register. After the transaction settles from merchant services, QuickBooks Online automatically creates a deposit in the merchant’s company file.

In order to take advantage of automatic reconciliation, set the following parameters in the salesreceipt create request:

• CreditCardPayment.CreditChargeResponse.CCTransId to the value returned in the original QuickBooks Payments charge response.
• CreditCardPayment.CrecitChargeInfo.ProcessPayment to true. This triggers QuickBooks Online services to store the credit card or eCheck charge response information, in particular the CCTransId field that is fundamental to credit card and eCheck transaction reconciliation. This triggers the notation Transaction has been processed for the sales receipt on the QuickBooks Online user interface.
• TxnSource to IntuitPayment. This inserts the transaction into a list of pending deposits to be automatically matched and reconciled with the merchant’s checking account.

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

{
   "Line": [{
      "Id": "1",
      "LineNum": 1,
      "Description": "Sprinkler Pipes",
      "Amount": 80.0,
      "DetailType": "SalesItemLineDetail",
      "SalesItemLineDetail": {
         "ItemRef": {
            "value": "17",
            "name": "Sprinkler Pipes"
         },
         "UnitPrice": 4,
         "Qty": 20
      }
   }],
   "CustomerRef": {
      "value": "15",
      "name": "Pye's Cakes"
   },
   "CreditCardPayment": {
      "CreditChargeInfo": {
         "ProcessPayment": "true"
      },
      "CreditChargeResponse": {
         "CCTransId": "EKFOR97XK9UD"
      }
   },
   "TxnSource": "IntuitPayment"
}

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

{
"SalesReceipt": {
 "domain": "QBO",
 "sparse": false,
 "Id": "192",
 "SyncToken": "0",
 "MetaData": {
    "CreateTime": "2015-04-15T12:59:52-07:00",
    "LastUpdatedTime": "2015-04-15T12:59:52-07:00"
 },
 "DocNumber": "1053",
 "TxnDate": "2015-04-15",
 "Line": [
    {
       "Id": "1",
       "LineNum": 1,
       "Description": "Sprinkler Pipes",
       "Amount": 80.0,
       "DetailType": "SalesItemLineDetail",
       "SalesItemLineDetail": {
          "ItemRef": {
             "value": "17",
             "name": "Sprinkler Pipes"
          },
          "UnitPrice": 4,
          "Qty": 20,
          "TaxCodeRef": {
             "value": "NON"
          }
       }
    },
    {
       "Amount": 80.0,
       "DetailType": "SubTotalLineDetail",
       "SubTotalLineDetail": {}
    }
 ],
 "TxnTaxDetail": {
    "TotalTax": 0
 },
 "CustomerRef": {
   "value": "15",
   "name": "Pye's Cakes"
       },
 "BillAddr": {
      "Id": "15",
      "Line1": "350 Mountain View Dr.",
      "City": "South Orange",
      "CountrySubDivisionCode": "NJ",
      "PostalCode": "07079",
      "Lat": "40.7633073",
      "Long": "-74.2426072"
 },
 "TxnSource": "IntuitPayment",
 "TotalAmt": 80.0,
 "ApplyTaxAfterDiscount": false,
 "PrintStatus": "NeedToPrint",
 "EmailStatus": "NotSet",
 "Balance": 0,
 "CreditCardPayment": {
    "CreditChargeInfo": {
       "ProcessPayment": true
    },
    "CreditChargeResponse": {
       "CCTransId": "EKFOR97XK9UD",
       "Status": "Completed",
       "CardSecurityCodeMatch": "NotAvailable",
       "AvsStreet": "Fail",
       "AvsZip": "Fail"
    }
 },
 "DepositToAccountRef": {
    "value": "4",
    "name": "Undeposited Funds"
 }
},
"time": "2015-04-15T12:59:53.035-07:00"
}

If you attempt to create this sales receipt without having enabled the Payments data source in your app, you receive the following error.

View Sample Error Response

1
2
3
4
5
6

 {
       "Fault" => {
             "Error" => [{
                   "Message" => "Feature Not Supported Error", "Detail" => "Feature Not Supported Error : true", "code" => "5030", "element" => "ProcessPayment"
             }], "type" => "ValidationFault"
       }, "time" => "2015-04-17T12:53:32.542-07:00"

After the transaction settles, QuickBooks Payments deposits funds into the merchant’s checking account and withdraws the transaction fee. A deposit object and purchase object, respectively, are created on his behalf. You, the developer, do not create these objects. This has the effect of automatically reconciling the transaction in the QuickBooks company account register.

To determine if a deposit object has been created, query deposit objects and parse the response to locate the deposit whose Line.LinkedTxn.TxnId matches that of the subject salesreceipt object created in the last section.

View Sample Deposit Object

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

{
    "Deposit": [
       {
          "DepositToAccountRef": {
             "value": "35",
             "name": "Checking"
          },
          "TotalAmt": 80.0,
          "domain": "QBO",
          "sparse": false,
          "Id": "200",
          "SyncToken": "0",
          "MetaData": {
             "CreateTime": "2015-04-20T15:24:02-07:00",
             "LastUpdatedTime": "2015-04-20T15:24:02-07:00"
          },
          "TxnDate": "2015-04-20",
          "CurrencyRef": {
             "value": "USD",
             "name": "United States Dollar"
          },
          "PrivateNote": "System-recorded deposit for QuickBooks Payments",
          "Line": [
             {
                "Amount": 80,
                "LinkedTxn": [
                   {
                      "TxnId": "192",
                      "TxnType": "SalesReceipt",
                      "TxnLineId": "0"
                   }
                ]
             }
          ]
       }
    ],
 "time": "2015-04-20T15:25:28.184-07:00"
}

A Purchase object is created on the merchant’s behalf to represent the corresponding fee paid to QuickBooks Payments for the transaction.

View Sample Purchase Object

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

{
    "Purchase": {
       "AccountRef": {
          "value": "35",
          "name": "Checking"
       },
       "PaymentType": "Cash",
       "EntityRef": {
          "value": "135",
          "name": "QuickBooks Payments",
          "type": "Vendor"
       },
       "TotalAmt": 0.28,
       "PurchaseEx": {
          "any": [
             {
                "name": "{http://schema.intuit.com/finance/v3}NameValue",
                "declaredType": "com.intuit.schema.finance.v3.NameValue",
                "scope": "javax.xml.bind.JAXBElement$GlobalScope",
                "value": {
                   "Name": "TxnType",
                   "Value": "54"
                },
                "nil": false,
                "globalScope": true,
                "typeSubstituted": false
             }
          ]
       },
       "domain": "QBO",
       "sparse": false,
       "Id": "958",
       "SyncToken": "0",
       "MetaData": {
                "CreateTime": "2015-04-20T15:24:02-07:00",
                "LastUpdatedTime": "2015-04-20T15:24:02-07:00"
       },
       "CustomField": [],
       "TxnDate": "2015-04-20",
       "CurrencyRef": {
          "value": "USD",
          "name": "United States Dollar"
       },
       "PrivateNote": "System-recorded fee for QuickBooks Payments. Fee-name: DiscountRateFee, fee-type: Daily.",
       "Line": [
          {
             "Id": "1",
             "Description": "System-recorded fee for QuickBooks Payments. Fee-name: DiscountRateFee, fee-type: Daily.",
             "Amount": 0.28,
             "DetailType": "AccountBasedExpenseLineDetail",
             "AccountBasedExpenseLineDetail": {
                "AccountRef": {
                   "value": "79",
                   "name": "Bank Service Charges"
                },
                "BillableStatus": "NotBillable",
                "TaxCodeRef": {
                   "value": "NON"
                }
             }
          }
       ]
    },
    "time": "2015-04-20T13:15:47.19-07:00"
}

There are two parts to refunding a transaction:

1. Issue a refund request to QuickBooks Payments to reverse the charge and to give the customer his funds.
2. Create a QuickBooks refundrequest object so that the QuickBooks company file can reconcile the refund once settled with Payments.

The figure below shows the overall merchant refund process:

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

{
  "amount": 5.0,
  "description": "first refund",
  "id": "",
  "context": {
    "deviceInfo": {
      "macAddress": "",
      "ipAddress": "",
      "longitude": "",
      "phoneNumber": "",
      "latitude": "",
      "type": "",
      "id": ""
    },
    "tax": 0,
    "recurring": false
  },
  "created": ""
}

Note the ID that is returned in this response. You use it in the subsequent request to create a refund receipt.

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

{
 "created": "2021-03-10T21:24:05Z",
 "status": "ISSUED",
 "amount": "5.00",
 "description": "first refund",
 "id": "XXXXXXXXXXX",
 "context": {
  "tax": "0.00",
  "reconBatchID": "420210310 1Q13249999999977036129AUTO04",
  "mobile": false,
  "paymentGroupingCode": "5",
  "txnAuthorizationStamp": "1615411445",
  "clientTransID": "amyxswe7",
  "deviceInfo": {
   "longitude": "",
   "latitude": "",
   "id": "",
   "type": "",
   "phoneNumber": "",
   "macAddress": "",
   "ipAddress": ""
  },
  "recurring": false
 },
 "type": "REFUND"
}

Now, create the refund receipt request. In order to take advantage of automatic reconciliation later when the payment refund transaction settles from merchant services, set the following parameters in the request:

• CreditCardPayment.CreditChargeResponse.CCTransId to the value returned in the original QuickBooks Payments refund response.
• CreditCardPayment.CreditChargeInfo.ProcessPayment to true. This triggers QuickBooks Online services to store the credit card charge response information, in particular the CCTransId field that is fundamental to credit card transaction reconciliation. This triggers the notation Transaction has been processed for the refund receipt on the QuickBooks user interface.
• TxnSourcetoIntuitPayment. This inserts the transaction into a list of pending refunds to be automatically matched and reconciled with the merchant’s checking account.

In addition,

• The minimal refund receipt request must include a Line.SalesItemLineDetail sub-object.
• Include a reference to the Customer object corresponding to the customer, according to your business process. The sample code below creates objects for the sandbox customer, Pye’s Cakes.
• The app must have the Payments data source enabled.
• Do not create two refund receipts with the same CreditCardPayment.CreditChargeResponse.CCTransId.

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

{
    "Line": [{
       "Id": "1",
       "LineNum": 1,
       "Description": "Sprinkler Pipes",
       "Amount": 80.0,
       "DetailType": "SalesItemLineDetail",
       "SalesItemLineDetail": {
          "ItemRef": {
             "value": "17",
             "name": "Sprinkler Pipes"
          },
          "UnitPrice": 4,
          "Qty": 20
       }
    }],
    "CustomerRef": {
          "value": "15",
          "name": "Pye's Cakes"
       },
    "CreditCardPayment": {
       "CreditChargeInfo": {
             "ProcessPayment": "true"
       },
       "CreditChargeResponse": {
             "CCTransId": "EKFOR97XK9UD"
       }
    },
    "TxnSource": "IntuitPayment",
    "DepositToAccountRef": {
         "value": "40",
         "name": "Checking"
 }
}

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

{
    "RefundReceipt": {
       "domain": "QBO",
       "sparse": false,
       "Id": "930",
       "SyncToken": "0",
       "MetaData": {
          "CreateTime": "2014-04-25T09:40:43-07:00",
          "LastUpdatedTime": "2014-04-25T09:40:43-07:00"
       },
       "CustomField": [
          {
             "Name": "P.O. Number",
             "Type": "StringType"
          },
          {
             "Name": "Sales Rep",
             "Type": "StringType"
          }
       ],
       "DocNumber": "10033",
       "TxnDate": "2014-04-25",
       "DepartmentRef": {
          "value": "1",
          "name": "Garden Services"
       },
       "Line": [
          {
             "Id": "1",
             "LineNum": 1,
             "Amount": 420,
             "DetailType": "SalesItemLineDetail",
             "SalesItemLineDetail": {
                "ItemRef": {
                   "value": "33",
                   "name": "Concrete"
                },
                "TaxCodeRef": {
                   "value": "NON"
                }
             }
          },
          {
             "Amount": 420,
             "DetailType": "SubTotalLineDetail",
             "SubTotalLineDetail": {}
          }
       ],
       "TxnTaxDetail": {
          "TotalTax": 0
       },
       "TotalAmt": 420,
       "ApplyTaxAfterDiscount": false,
       "PrintStatus": "NeedToPrint",
       "Balance": 0,
       "PaymentRefNum": "To Print",
       "DepositToAccountRef": {
          "value": "40",
          "name": "Checking"
       }
    },
    "time": "2014-04-25T09:40:43.687-07:00"
}

QuickBooks Online can manage product inventory. Line items entered on sales, purchase, and refund transactions flow into inventory items to automatically adjust quantity on hand. Additionally, cost and price of individual inventory items are stored so the merchant can track inventory value.

Enable inventory management for the QuickBooks company via Preferences.ProductAndServicesPrefs. By default, it is not enabled. Set these flags to true:

• ForSales—Show product column on sales forms
• ForPurchase—Show product column on purchase forms
• QuantityWithPriceAndRate—Quantity with price and rate enabled.
• QuantityOnHand—Quantity on hand enabled.

After enabling inventory management, add individual inventory items as Item objects.

• FIFO inventory accounting
• Tracking quantity on hand
• Categories to four levels
• Taxable status of the item
• Price and cost

• LIFO or Average Cost inventory accounting
• Tracking individual items—or example, by serial number
• Tracking by different stock locations

Create an Item object for each inventory item that is tracked. Take care when using categories to define your products—they can add complexity when parsing out the inventory item of interest.

Sample Request

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

{
    "Name": "Office Supplies",
    "Description": "This is the sales description.",
    "Active": true,
    "Taxable": true,
    "UnitPrice": 25,
    "Type": "Inventory",
    "IncomeAccountRef": {
       "value": "79",
       "name": "Sales of Product Income"
    },
    "PurchaseDesc": "This is the purchasing description.",
    "PurchaseCost": 35,
    "ExpenseAccountRef": {
       "value": "80",
       "name": "Cost of Goods Sold"
    },
    "AssetAccountRef": {
       "value": "81",
       "name": "Inventory Asset"
    },
    "TrackQtyOnHand": true,
    "QtyOnHand": 10,
    "InvStartDate": "2013-02-19"
}

View Sample Response

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

{
    "Item": {
       "Name": "Office Supplies",
       "Description": "This is the sales description.",
       "Active": true,
       "FullyQualifiedName": "Office Supplies",
       "Taxable": true,
       "UnitPrice": 25,
       "Type": "Inventory",
       "IncomeAccountRef": {
          "value": "79",
          "name": "Sales of Product Income"
       },
       "PurchaseDesc": "This is the purchasing description.",
       "PurchaseCost": 35,
       "ExpenseAccountRef": {
          "value": "80",
          "name": "Cost of Goods Sold"
       },
       "AssetAccountRef": {
          "value": "81",
          "name": "Inventory Asset"
       },
       "TrackQtyOnHand": true,
       "QtyOnHand": 10,
       "InvStartDate": "2013-02-19",
       "domain": "QBO",
       "sparse": false,
       "Id": "36",
       "SyncToken": "0",
       "MetaData": {
          "CreateTime": "2015-04-17T15:21:09-07:00",
          "LastUpdatedTime": "2015-04-17T15:21:10-07:00"
       }
    },
    "time": "2015-04-17T15:21:09.688-07:00"
}

Your app needs to provide options to allow merchants to manage and track their customers.

• Account login: For customers who want a logged-in presence with your app, supply a way for customer accounts to be created. This feature is built on creating individual customer objects in the QuickBooks company file.
  • When creating sales receipts, add a reference to the individual customer.
  • Store the customer’s credit card or eCheck information for future use as a Payments API Cards object (credit card and eCheck details are opaque to you).
• Guest login: For customers who are more transient in nature or who don’t want to create an account, supply a default guest customer. This feature is built on a single account with the name, Guest. When creating sales receipts, add a reference to this account.

Having a customer reference attached to each sales receipt enables the merchant to accurately track customer activity.