If you read here https://developer.intuit.com/docs/0150_payments, Intuit is saying "If you're working with an implementation of Hosted PayPage or you need to implement a recurring billing solution soon, then use the legacy QBMS Payments API instead. But if possible, try to use our growing Payments Beta. The QBMS API will soon be deprecated."

How does that affect this module?

Comments

jantoine’s picture

Status: Active » Postponed

This project currently requires the QuickBooks PHP DevKit module for integration with QuickBooks Merchant Services. If the QuickBooks PHP DevKit library is updated to leverage the new QuickBooks API without having to change their API, then in theory, nothing would need to be changed here. If however, the QuickBooks PHP DevKit library has to alter their API, a 2.x branch will need to be created to either work with an updated QuickBooks PHP DevKit API or directly with the new QuickBooks API.

Because the sponsor of the 1.x branch has moved on to a new payment gateway due to QuickBooks' lack of support for currencies other than the USD, I would need a new sponsor for this 2.x branch.

cbanton’s picture

Was it determined if a new branch is needed to support the new Quickbooks API. Looks like they are completely shutting off access through QBMS April 30th 2016.

Thanks.

jantoine’s picture

I'm not sure if the QuickBooks PHP DevKit (https://github.com/consolibyte/quickbooks-php) is utilizing the new Payments API from Intuit. Someone would need to check with the maintainers of that library. You would also need to check that switching to this new API hasn't changed the library at all.