Testing and Go Live

JavaScript v3

• Current Braintree SDKs
• Android v5
• iOS v6
• JavaScript v3
• Previous Versions
• Android v4
• iOS v5
• JavaScript v2

You can test your PayPal integration in the Braintree sandbox environment in 2 ways:

• Mocked PayPal testing (default)
  • Behaves similarly to production but does not allow for end-to-end testing
  • Uses Braintree sandbox test values to simulate PayPal responses in your Braintree sandbox
  • Allows you to confirm that your client- and server-side configurations are correct and that you are receiving appropriate responses for your requests
  • Does not return data to your PayPal sandbox account
  • Does not work with the PayPal Checkout component of the JavaScript v3 SDK
• Linked PayPal testing
  • Requires additional setup
  • Directly connects your Braintree sandbox account to your PayPal sandbox account
  • Returns data to both sandbox accounts
  • Allows you to test the full functionality of your PayPal integration (e.g. transaction reporting, email receipts)

Mocked PayPal testing

Use your Braintree sandbox API credentials and the test values on our Testing page to ensure your client and server integrations with Braintree are working as expected.

Any testing you do in the mocked PayPal flow will only be reflected in your Braintree sandbox – no data will be sent to your PayPal sandbox. If you'd like to do complete end-to-end testing, see linked PayPal testing.

Linked PayPal testing

In order to link a PayPal sandbox test account to your Braintree sandbox account, you will need the API credentials for that PayPal sandbox test account.

If you don't already have a PayPal sandbox test account for testing your Braintree integration, create a new one by following these steps:

1. Create a PayPal business sandbox account:
   • Log into the PayPal Developer Dashboard
   • Navigate to Sandbox > Accounts
   • Select the account type as Business
   • Select the same Country as your Braintree sandbox account
   • Select Create Account
2. Go to the Create New App page
   • Create an app to get sandbox API credentials
   • Select the same sandbox developer account as the test account created in step 1
3. Note the following Sandbox API Credentials for the new app you created:
   • Email address associated with this app
   • Client ID
   • Secret

Once you have those PayPal sandbox API credentials, enter them in your Braintree sandbox:

1. Log into your Braintree sandbox Control Panel
2. Navigate to Settings > Account Settings > Payment Methods > PayPal
3. Select Link Sandbox
4. Enter the Email address, Client ID, and Client Secret for your PayPal sandbox test account
5. Select Link PayPal Sandbox

Testing App Switch

App Switch allows PayPal customers who have the PayPal app installed to complete their transaction in the PayPal app, streamlining checkout with strong multi-factor authentication. This feature can be tested in both the PayPal production app and sandbox environments. To test App Switch, make sure your integration is:

• App Switch eligible.
• You have completed the PayPal App Switch integration.

Testing your integration using PayPal's sandbox

PayPal's sandbox application allows PayPal users, both inside and outside the United States, test the app switch consumer experience.

Who is this solution intended for?

• This solution is available for your development team internationally.

Use cases that can be tested:

Preconditions:

• Long-lived session or remember me flow

• Face id or Biometric

How can I enable the above login methods ?

1. Login to your PayPal app. On the home screen, select the avatar icon.

Use cases that cannot be tested:

1. System errors

2. App launch failure

3. Activity feed updates

4. Non-App Switch flow screens

Go Live

Create an API user

Production API credentials, including your API keys, must be entered into your server-side code to connect API calls to the Braintree gateway. While each user in your gateway has their own unique set of API keys, only one set can be included in your integration.

We do not recommend including an individual user's API credentials. If you ever need to delete or suspend that user, this could break your connection to Braintree and result in failed transactions.

Get production credentials

Log into your production account as the API user to obtain your API credentials. You'll need the:

• Production merchant ID
• Production public key
• Production private key

Keep in mind that public and private keys are both environment- and user-specific.

Update production account settings

Make sure your production account settings mirror the ones in your tested sandbox configuration. Be sure to recreate any recurring billing plans or settings if you plan to use recurring billing in production.

Update live server configuration

In your server code, update your configuration to production values:

gateway = Braintree::Gateway.new(
  :environment => :production,
  :merchant_id => "use_your_merchant_id",
  :public_key => "use_your_public_key",
  :private_key => "use_your_private_key",
)

var gateway = new BraintreeGateway
{
    Environment = Braintree.Environment.PRODUCTION,
    MerchantId = "YOUR_PRODUCTION_MERCHANT_ID",
    PublicKey = "YOUR_PRODUCTION_PUBLIC_KEY",
    PrivateKey = "YOUR_PRODUCTION_PRIVATE_KEY"
};

gateway = braintree.BraintreeGateway(
    braintree.Configuration(
        braintree.Environment.Production,
        merchant_id="use_your_merchant_id",
        public_key="use_your_public_key",
        private_key="use_your_private_key"
    )
)

$gateway = new Braintree\Gateway([
    'environment' => 'production',
    'merchantId' => 'use_your_merchant_id',
    'publicKey' => 'use_your_public_key',
    'privateKey' => 'use_your_private_key'
]);

const gateway = new braintree.BraintreeGateway({
  environment: braintree.Environment.Production,
  merchantId: "YOUR_PRODUCTION_MERCHANT_ID",
  publicKey: "YOUR_PRODUCTION_PUBLIC_KEY",
  privateKey: "YOUR_PRODUCTION_PRIVATE_KEY"
});

BraintreeGateway gateway = new BraintreeGateway(
  Environment.PRODUCTION,
  "YOUR_PRODUCTION_MERCHANT_ID",
  "YOUR_PRODUCTION_PUBLIC_KEY",
  "YOUR_PRODUCTION_PRIVATE_KEY"
);

Once you have updated these values and configured your preferred processing settings, the live production environment will function similarly to the sandbox environment you've been using for development. Learn more about the differences between production and the sandbox.

On the client side, no configuration updates are needed when you make the switch to production – your client obtains its client token from your server, which is all the configuration it needs.

Test transactions in production