4. Policy – App Card
1. No credit card -
App must have
free trial. Required
2. No plan selection -
App card pricing
language should
match pricing
language in app
plan page on 3rd
party site.
Required
5. Purchase Authorization … cont’d
Note: The app logo
used for the app in
the Intuit Appcenter
will be the same
one used during the
purchase flow
7. OpenID Landing Page
1. DirectConnecttoIntuit() Call
has already been made to get
access token
2. The email addressed passed
in the OpenID assertion
should be the address used
to create the account. The
field can be editable
Required
3. Show wording that the
accounts are being linked.
Required
4. The mapping of the Intuit
Account and your app should
occurr during this step.
Required
5. Additional fields may be
required to provision an
application (i.e,. Company
name) – this information
should be requested from
QBO/QBD and used if
available via API. (Please see
notes) Required
6. There should be a way to
sign-in using an existing
account. It should be clearly
visible i.e., next to the field
entry. Recommended
2
6
3
8. Example
1. DirectConnecttoIntuit() Call
has already been made to get
access token
2. The email addressed passed
in the OpenID assertion
should be the address used
to create the account. The
field can be editable
Required
3. Show wording that the
accounts are being linked.
Required
4. The mapping of the Intuit
Account and your app should
occurr during this step.
Required
5. Additional fields may be
required to provision an
application (i.e,. Company
name) – this information
should be requested from
QBO/QBD and used if
available via API. (Please see
notes) Required
6. There should be a way to
sign-in using an existing
account. It should be clearly
visible i.e., next to the field
entry. Recommended
2
6
3
9. First – time Logged in
1. The Blue-dot menu
must appear
immediately on
page load.
Required
2. The intuit first-run
widget will appear
next to the blue
dot. This widget will
only appear the
first-time the user
lands on the app
when completing
the purchase from
Intuit Appcenter.
Required
3. Clearly show the
benefit/value of the
app being
connected to
QuickBooks.
Recommended
2
1
6
12. Button
1. The “Connect to QuickBooks”
button must be used when
connecting your app to
QuickBooks Desktop or
QuickBooks Online data.
Required
2. To render the connect to
quickbooks button, the app
must use the
<ipp:connectToIntuit>… tag. Do
not hard code the img tag.
Required
3. The button should be hidden
(replaced with the blue-dot)
upon connect for a profile. For
apps that support multiple
profiles, the button may be
rendered when not
“connected” to a particular
profile. Recommended
14. Button
1. All users who have
signed up for the app
from the appcenter
must be given the
option to sign-in with
their Intuit account.
Required
Minute dock
Mavenlink
ProOnGo
Platform Changes (planned with timing)
App Center
Under Try it now button near Pricing details, we should show Free Trial details (planned for 3.6)
SUSI – INTUIT DOES THIS
Try/Buy
Authorize page shows data that will be shared ( 3.6) – different text on this than C2QB
Authorize Confirm screen - animation shows successful sync of data (3.6) (same for C2QB)
Provide html in guidelines for customer mapping (3.6)
Provide additional APIs for customer info collection as part of the Open ID provisioning (Full name, company name, phone number, email, address) (3.6)
The layout of this page is recommended best practice
5. OpenID and IDS APIs must be used to retrieve the following user info during the purchase flow
1. First name/Last name – API
2. Company name – API
3. Phone number – API
4. Email – API
5. Address – API
Technical questions about the use of API can be directed to IPP Developer Relations.
3. Bill.com’s case is a good example. For each org, the connect to quickbooks is shown when not connected. Once connected, the button is replaced by the blue-dot.
Note: Mavenlink requires the user to click on the drop down arrow next to “3rd-party service”.
ISSUE: How do we handle services that do whitelabeling? Hide unless Cookied?
