Payment Processing via Cloud into QuickBooks® Accounting Software

Testing

Connections

Connections provides the ability to check against the Secure Vault System API Credentials to ensure valid responses. Also can provide the ability to store system information or product versions.

POST connection

Test software connection.

Resource Information

Method: POST

URL: https://demo.goodfundsgateway.com/api/connection.json

Requires authentication? Yes

Method Parameters

N/A

Query Parameters

Parameter	Type	Required	Description
software_info	node	N	Software Info Node: This is your current software information
version	string	N	Current Version to track version control in your software with ours.
external_software	node	N	External Software Info Node: Any external software that is being used with your software. (Example: QuickBooks, Google Apps, etc...)
product	string	N	Software, Product Name, or App name that is being used.
desktop_info	node	N	Desktop Information Node: This is helpful when needing to track your clients current computer / server OS
osversion	string	N	Clients current OS Version. (Example: Microsoft Windows NT 6.1.7601 Service Pack 1)

PHP Example CC Request: (json format)

      $data = array(
        'software_info'  => array(
          'version'   => '3.1.10.0'
        ),
        'external_software' =>  array(
          'product'   =>  'QuickBooks Pro 2016'
        ),
        'desktop_info'  =>  array(
          'osversion'   =>  'Microsoft Windows NT 6.1.7601 Service Pack 1'
        )
      );

      $data_string = json_encode($data);

      $ch = curl_init('https://demo.goodfundsgateway.com/api/connection.json/software');
      curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST");
      curl_setopt($ch, CURLOPT_SSLVERSION, 6);
      curl_setopt($ch, CURLOPT_POSTFIELDS, $data_string);
      curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
      curl_setopt($ch, CURLOPT_HTTPHEADER, array(
          'Content-Type: application/json',
          'Content-Length: ' . strlen($data_string),
          'svs-api-id: [SVS API ID]',
          'svs-api-key: [SVS API KEY]')
      );                       
                                                                                                                           
      $result = curl_exec($ch);
      $err = curl_error($ch);

      curl_close($ch);

      if ($err) {
        echo "cURL Error #:" . $err;
      } else {
        echo $result;
      }

Response data: (json format)

      {
        "status":"success",
        "successMessage":
        {
          "response_code":203,
          "message":
            {
              "account":
              {
                "CreditCardGateway":
                {
                  "gateway_id":"[Gateway ID]",
                  "alias":"Converge Credit Card",
                  "allows_refunds":1,
                  "allows_level3":1
                },
                "ECheckGateway":
                {
                  "gateway_id":"[Gateway ID]",
                  "alias":"Converge ACH",
                  "allows_refunds":0,
                  "allows_level3":1
                },
                "parent_client_id":"[Your Client ID]"
                }
              }
        }
      }

Our sandbox environment provides a sandbox to implement Invoiced, perform quality assurance (QA), and develop integrations.

Sandbox

You can sign up for a free sandbox account at .

In the sandbox you will be able to test out workflows and integrations you are building on Invoiced. The sandbox is identical to our production environment with the exception that it does not perform any live charges to credit cards or bank accounts. Sandbox accounts are entirely separate from your production account in order to keep testing isolated.

Data Storage and Rate Limiting

You should not depend on any data stored in the sandbox. Test data is not guaranteed to be retained, and we might periodically clean out old test data to preserve system resources. Generally this would happen after data has been stale for months.

The sandbox is intented to allow you to build and test without restrictions, however, we could enforce rate limiting or data caps to prevent abuse. In normal scenarios you should never bump into these.

<3> Clearing data You can clear all the data in your test account in Settings → Developers with the Delete all test data button. This will clear out data such as customers, invoices, and subscriptions while retaining your settings.

Payments

When using the test gateway you can use the payment information below to simulate payments in various scenarios.

Credit Card

BRAND	NUMBER
Visa	`4242 4242 4242 4242`
Visa	`4111 1111 1111 1111`
Visa (debit)	`4000 0566 5566 5556`
MasterCard	`5454 5454 5454 5454`
MasterCard	`2223 0031 2200 3222`
MasterCard (debit)	`5200 8282 8282 8210`
MasterCard (prepaid)	`5105 1051 0510 5100`
American Express	`3782 822463 10005`
Discover	`6011 1111 1111 1117`
Diners Club	`3056 9300 0902 0004`
Diners Club	`3056 9309 0259 04`
JCB	`3530 1113 3330 0000`
UnionPay	`6200 0000 0000 0005`

Credit Card Failures

BRAND	NUMBER	DESCRIPTION
Visa	`4000 0000 0000 0069`	Declined charge
Visa	`4000 0000 0000 0127`	Vaulting or charging will fail

ACH

Any valid account and routing number will produce a successful charge.

ROUTING NUMBER	ACCOUNT NUMBER
`110000000`	`123456789`

Deposit Verification Amounts

If you are testing the micro-deposit verification flow you can use $0.35 and $0.45 as the amounts. Any other amounts will fail.

ACH Failures

ROUTING NUMBER	ACCOUNT NUMBER	DESCRIPTION
`123123123`	`123123456`	Declined charge
`123123123`	`123123893`	Pending charge, will succeed
`123123123`	`000222222227`	Pending charge, will fail
`123123123`	`000111111116`	Vaulting or charging will fail

SEPA

IBAN	DESCRIPTION
`DE89370400440532013000`	Successful charge
`DE62370400440532013001`	Failed charge

Other gateways

If you are connecting to a payment gateway other than test in the sandbox then the sandbox will connect to your payment gateway in test mode. This means that you can use test payment information from your payment gateway instead of live ones. In test mode, payments will behave identically to live mode without performing any real charges.

API

In order to access the sandbox through the API you must use the api.sandbox.invoiced.com endpoint. All of our official client libraries have support for the sandbox built in. You simply pass in your sandbox API key and true as the second argument when instantiating a new API client, i.e.

Invoiced::Client.new("{YOUR_SANDBOX_API_KEY}", 
		true)