Ready for Launch?

This section discusses the general steps necessary for a production launch

Certify Your Integration

In order to ensure that you have used the best practices while building your integration and that you have successfully tested your use cases we always suggest doing a demo and code review with your Solutions Engineer and Integration Engineer. Once that is completed and all necessary changes are made then you will get the green light to move forward with production launch.

Make sure to factor in demo and code review, as well as follow-up integration changes to your development timeline

Production Account Setup

The account structure you designed with your PayPal Solutions Engineer and Integration Engineer will determine how we set up your production accounts. It is also important to note that the production account setup will not begin until you have a signed contract with Braintree.

Work with your PayPal team to start the account onboarding process well before your desired launch date

Once your Production Account is created you will also need to generate production API keys. API keys should always be generated by your account admin as they will have the most user permissions. You will need to make sure that the API user that is created has the correct access to your production Merchant Account IDs (MAIDs). These API keys and Production Account MAIDs will need to be configured in your integration and passed with API requests.

Create users in Braintree Control Panel

Once your production Braintree account is set up you can start creating users and roles within the Braintree Control Panel. We recommend creating users for all of your business users that will need access to the control panel and also segmenting permissions by creating different roles for various business functions such as: IT, Tech Support, Developer, Accounting, Reporting, Admin, etc... You may also segment user access by the merchant account IDs that the user needs access to.

Braintree team will not do this on your behalf in Production since that is a more sensitive environment but we can provide training and support as you set this up

Ordering Production Card Readers

In order to launch your integration you will need to procure, stage, and deploy production card readers. Please be sure to account for these lead times as you plan your pilot launch timeline. Consult your PayPal Solutions Engineer and Integration Engineer to align on the requirements for staging the readers for deployment.

Work with your PayPal team to forecast the number of readers that you will need for launch to ensure availability and align with your launch timeline!

Before we ship any production card readers we will require that your contract is signed and executed with PayPal.

Pre-Launch Configuration Checklist

All of these features should be tested in Sandbox successfully and integrated before enabling in production. Note that some of these activities can only be completed once the production Braintree account has been created.

• If you plan to support Unreferenced Refunds, that means that "blind credits" must be enabled on your Braintree Gateway Account. To do this, you must request this to be enabled by your PayPal project team (Engagement Manager, Integration Engineer, or Customer Success Manager)

• If you plan to support Vaulting with Braintree, this must be enabled on your account, so make sure to request this from your PayPal project team

• If you want to enable Offline Processing (Store and forward) functionality then you must generate SSL certificates for your POS and readers and request to enable it from the PayPal project team as outlined in our documentation

• If you want to enable QR code payments (PayPal and Venmo) there is additional set up required, which will need to be coordinated with your PayPal project team

• In order to enable Partial Authorization, please request this from your PayPal project team

• If you would like to have custom idle screen images for your reader displays, you will need to follow the instructions for each device set up (P400, M400, E285)

• If you will be passing L2/L3 data in your requests to Braintree, your tax ID will need to be configured on your Braintree merchant account

• In order to enable the Card Data Collection feature on the Braintree reader, be sure to make sure the Braintree team has configured your BIN ranges on your merchant account

• If you plan to use the requestTextPrompt, requestAmountPrompt or Card Data Collection the Braintree team will need to configure your gateway account to enable these features

• If you plan to enable Incremental Authorizations (updateTransaction) you'll need to make sure your Braintree account is configured accordingly.

• If you plan to enable Overcapture be sure to have the Braintree team enable this on your merchant account

Launch Readiness Questionnaire

This will help you determine if you are prepared for you upcoming launch with Braintree, please note that this is complimentary to any requirements from your other integrated systems which may be part of the launch such as Point of Sale, ERP, OMS, E-commerce or other systems. Make sure to discuss this with your PayPal Engagement Manager and Integration Engineer.

• Is your production account set up with Braintree? Have all of the required Merchant Account IDs (MAIDs) been onboarded?

• Have you reviewed the Pre-Launch Configuration Checklist above?

• Have you received your production Braintree card readers?

• Have you tested all of your use cases?

• Has your PayPal Integration Engineer certified your integration?

• Have you agreed to a launch timeline with your PayPal Integration Engineer?

• Have you created users in your production Braintree Control Panel?

• If you answered yes to the above questions that you are likely ready for launch!

Launch Checklist

A few reminders of what is needed to ensure a successful day of launch with Braintree in your store environment.

• Make sure your in-store network is configured according to the Braintree requirements

• Double check that your integrated Point of Sale instance is pointing to the Braintree production API endpoint (https://payments.braintree-api.com/graphql), and using your Braintree production account API keys

• Create location IDs in your production environment

• Pair your production readers to your production location IDs

• Make sure your readers are updated to the latest firmware version which you have tested

• Run a test to make sure your production set up is working as expected

For your API requests to be successful in the production environment you will need to make sure you are sending your requests to the Braintree production GraphQL API endpoint which is https://payments.braintree-api.com/graphql and you will also need to use Production Account API keys