TAPP for Stripe and Microsoft Dynamics 365 Sales – Deployment and Configuration
Introduction
This page explains how you can get TAPP for Microsoft Dynamics 365 Sales deployed and configured in your Microsoft Dynamics 365 Sales Environment. Contact Bluefort support on support@bluefort.io if you have any questions.
Pre-requisites
In order to successfully deploy this product you need to have a Microsoft Dataverse environment with a database and Microsoft Dynamics 365 Sales app deployed.
It is recommended to conduct testing, training and integration testing with any other solutions in a test environment first before using the software on a production environment.
Obtaining the Software for Bluefort TAPP
The Software can be downloaded from Microsoft AppSource. These are the high-level steps:
- Browse to Microsoft AppSource.
- Make sure you are logged in to AppSource with a user from the same tenant where you would like to install TAPP for Microsoft Dynamics 365 Sales.
- Click on the Install button.
- Confirm your detail and click on the Install button.
- You are now automatically re-directed to Power Platform admin center.
- Within Power Platform admin center, select the target environment where you want to install the software, agree to the legal terms and privacy statements and click on the Install button.
- The installation will start within Power Platform admin center.
Configuration
Upon successful deployment of the solution you should see a new model driven app called Bluefort TAPP in the main menu of Dynamics 365 as shown in the screenshot below.
Assignment of Dataverse (CRM) roles
Once the model driven app is visible in the environment, the next step would be for a user with the System Administrator role to assign other roles to the application so that other non-admin users are able to access the application. This can be done by clicking on the ellipses (3 dots) right above the name of the model driven app (i.e. beneath the Bluefort TAPP logo) and then clicking on Manage Roles in the menu which pops up.
Once this is clicked, a new slider menu is displayed where one can assign which roles can access the Enterprise Subscription Automation model driven app. Both standard CRM roles and custom CRM roles which are specific to the organisation can also be assigned to the application.
Onboard your Dataverse (CRM) environment to Stripe
The first step is to open the Bluefort TAPP model driven app by clicking on the Bluefort TAPP logo in the apps menu. Then click on TAPP onboardings and click on the New button to create a new onboarding record.
In the form’s General Tab:
- Enter a Name for the onboarding record
- Set Onboarding Type to Stripe Connect
- Set Onboarding Sub-Type to Sandbox or Live (depending on what Stripe API endpoint type you want to connect to)
- Enter the 2 letter country value of the country the CRM organisation is operating within in the Stripe ISO Alpha-2 Country field. These can be found here, in the Alpha-2 code column.
Do not click Save yet but go to the Stripe Tab and provide a value for:
- Stripe Success URL – this is the web page your customers will be re-directed to if a payment method / payment flow is successful. This should be a page hosted on your web-site with your own branding and theming where you thank the customer for their business and confirm that payment has been processed.
- Stripe Cancel URL – this is the web page your customers will be re-directed to if a payment method / payment flow fails or encounters an error. This should be a page hosted on your web-site with your own branding and theming where the customer is encouraged to retry the operation.
You may now proceed to save the record.
Once the record is saved, back on the General Tab, the Onboarding URL is generated. The onboarding URL is used to onboard the CRM organisation (i.e. the legal entity using CRM) to Stripe.
In a sandbox/test scenario, you can fast-track through the Stripe wizard and insert dummy/test data – dummy values are often suggested within various input text boxes within the wizard.
In a production/live scenario, the information required by the Stripe wizard exposed by this URL should be submitted by a legal representative of the legal entity who has the legal authority to act on behalf of the legal entity. This is typically a business owner, a director or a member of the governing board but might differ by region and legal setup of the organisation.
Note: This wizard also give you the opportunity to tailor the experience of your customers by configuring aspects such as business name and statement descriptors to be shown on your customers’ bank statements, customer support phone numbers, contribution to the Stripe Climate commitment etc
When the onboarding to Stripe is successful, the person going through the wizard should see the Bluefort success screen below.
After the legal representative receives the success message the onboarding can be verified by clicking on the Test Merchant Connection button in the ribbon. A successful result should be shown in the fields within the Stripe Merchant Connection section.
If the message shown is not a success message (as shown in the screenshot below) then it means that the Stripe onboarding Wizard was not correctly completed end-to-end and thus the Stripe service is not able to correctly onboard this merchant for payment processing.
Multiple Stripe Accounts [optional]
TAPP support creating multiple Stripe merchants within one CRM organisation. This is because some customers have multiple Stripe accounts which they might use for different legal entities, business units, teams or business lines.
In most scenarios, having one Stripe account should suffice but if you require and have configured multiple onboarding records of type Stripe Connect that you might also want to configure the Stripe Connect onboarding record which is most commonly used to be defaulted for your users.
TAPP Setups [optional]
In some scenarios, such as when generating a Stripe Payment Method URL for a customer or when generating a stripe URL for a one-off payment, you would like CRM to auto-default the Stripe Connect onboarding method to use, instead of having the user manually having to select it on every customer (for payment method URLs) or every invoice (for one-off payment URLs). If this is the case, then you would need to create a record in TAPP setups. The record should have the following field values:
- Identifier – Stripe
- Description – Any value [optional]
- Default TAPP Onboarding GoCardless – This should be left empty for Stripe
- Default TAPP Onboarding Stripe – This is a lookup field where you should select the specific Stripe Onboarding record you’d like to be defaulted for users.
After entering the data above simply save the record.
Congratulations!
You have finished configured Bluefort TAPP for Stripe and Microsoft Dynamics 365 Sales. If you’ve encountered any issues, have questions or need help or support please reach out to the Bluefort support team on support@bluefort.io
Enjoy using Bluefort TAPP for free!
Click Here to see a demo of configuration and day-to-day use of Bluefort TAPP for Microsoft Dynamics 365 Sales.