Introduction

MerchantE has created an integration with BlueSnap to maintain a competitive suite of processing capabilities. This integration enables the processing of international transactions while providing onboarding, new product offerings, reporting, and improving the overall customer experience.

To use the MerchantE International Gateway, you will need to sign up for a BlueSnap account and integrate the account with the MerchantE Payment Gateway. This will then allow you to send fields required by BlueSnap for payment processing to the Payment Gateway. Reports for the payments can then be generated in the MerchantE Business Portal. This guide outlines how to set up the MerchantE Payment Gateway to use BlueSnap for international transactions.

Card on File Transactions

Card of File transactions are initiated using a payment method saved by the merchant. These transactions can be initiated either by the cardholder or the merchant. For international payments, the transactions can be linked to previous Card on File transactions using BlueSnap transaction information stored by MerchantE when the transaction was processed.

Cardholder Initiated Transactions (CIT)

When a transaction is initiated by the Cardholder and uses the card credentials that have already been stored by the merchant, it is known as a Cardholder Initiated Transaction (CIT). An example is when a cardholder logs in to a website account and makes a purchase using the card credentials that are stored by the merchant.

Merchant Initiated Transactions (MIT)

When a transaction is initiated by the Merchant per an agreement they have with the Cardholder and uses the card credentials that have already been stored by the merchant. An example is a Fitness Center that automatically processes a monthly transaction for the cardholder’s membership.

Network Transaction ID (NTI) and Original Network Transaction ID

The networkTransactionId (NTI) is the BlueSnap identifier for a transaction. The NTI can be used to retrieve information on previously approved transactions for related transactions, such as subscription services.

An NTI is included in the response for:

• CITs using 3DS2 (threed_secure_refrenceId).

• MOTO transactions which return an NTI.

• MITs which have input parameters referencing previous transactions (transaction_id).

The original NTI (ONTI) is the NTI associated with the original BlueSnap transaction, either processed. The original NTI (ONTI) can then be provided as part of an MIT request to identify the associated transaction.

The ONTI is identified from previous transactions using two methods:

1. threed_secure_referenceId - The threed_secure_referenceId is a unique identifier created as part of a BlueSnap 3DS transaction. If the threed_secure_referenceId is provided in the payment gateway request, the ONTI can be retrieved. If no ONTI is found in the table, the NTI is used.

2. transaction_id - If the threed_secure_referenceId is not available, the transaction_id created by the payment gateway can be used to search for the ONTI and used in the request. If the ONTI is not found, the NTI is used. If neither the ONTI nor NTI are found for the transaction_id, nothing is provided to BlueSnap.

Setting Up the International Gateway

1. Register with BlueSnap - BlueSnap will contact you directly when the application is approved or if additional information is required.

2. Create BlueSnap API Credentials - You will need to create API credentials and set up 3DS2.

3. Provide the API Credentials to MerchantE - Customer Care will then create an account change request to add the information to your profile.

   1. help@merchante.com

   2. 1-888-288-2692

4. Contact MerchantE Sales Engineering. Sales Engineering will help you complete and test the settings.

   1. help@merchante.com

   2. 1-888-288-2692

Registering with BlueSnap

To use the international gateway, you will first have to register with BlueSnap.

1. Sign up using the BlueSnap Application Portal.

   1. https://sandbox.bluesnap.com/jsp/referred_onboarding/?referral=MERCHANTE1

   2. For subsequent visits, login to your account.

2. Click the Account Application tile to start the application process.

3. Fill out the application.

   1. Business Info:

      1. Country - Select the country of origin.

      2. Email - Add a contact email for the business.

      3. Business Name (Doing Business As) - The informal name of the business.

      4.  Business Legal Name - The legal name of the business.

      5. Website - The business website.

      6. Address - Street address, city, state, and postal code for the business.

      7.  Phone - Business contact phone number.

      8.  Click Next.

   2. Processing Info:

      1. Product and Services Description - Keywords describing the goods and services provided.

      2.  Business Entity - Structure of the business.

      3. Product Description - Category for the goods and services.

      4. Sales Volume ($)

      5. Tax ID - Tax identification number for the business.

      6. Click Next.

   3. Ownership Info:

      1. Country - Company representative’s country of citizenship.

      2. First Name - Company representative’s first name.

      3. Last Name - Company representative’s last name.

      4. Date of Birth - Company representative’s date of birth.

      5. Address - Company representative’s street address, city, state, and postal code.

      6. Phone - Contact phone number for the company representative.

      7. Number of Owners - Number of owners who own more than 25% of the business.

      8. Click Next.

   4. Banking Info:

      1. Bank Account State - Location of the Bank.

      2. Account Type - Checking or Savings account.

      3. Bank Name - Name of the bank.

      4. Routing Number - Account routing number.

      5. Account Number - Account number.

      6. Click Complete.

BlueSnap Merchant Account Setup

To use the international gateway, you will need to complete the account setup after BlueSnap approves the account registration. This includes setting up:

• API Credentials

• 3DS2 Support Options

API Credentials

1. Navigate to the URL provided in the welcome email.

2. Open the Settings menu and select API Settings.

3. API Credentials - Set a password and click Request API credentials.

4. Provide the Username and Password in the API Credentials section to MerchantE.

Completing Your International Gateway Setup

Completing your setup depends on how the international gateway will be used.

• If you are using NetSuite, follow the instructions to set up your NetSuite account to use the international gateway. You will need to enable features in your Payment Processing Profile to use 3DS2 transactions and select the currencies that will be used for transactions.

• If you are not using NetSuite, additional development work will be necessary depending on your specific implementation. You will need to send the fields specified in the Non-NetSuite section.

3DS2 Transactional Parameters

1. Navigate to the URL provided in the welcome email.

2. Open the Settings menu and select Fraud Settings.

3. Use the Fraud Settings page to customize your support. For more information, see Fraud Prevention.

4. The 3D Secure rules section can be used to customize your 3DS2 support.

NetSuite

You will need to configure your Payment Processing Profile to use the International Gateway in NetSuite.

The MerchantE SuitePayments bundle is already configured to use fraud_session_id for non-3DS2 transactions.

 To configure your Payment Processing Profile to receive international payments in other currencies, you will have to:

• Enable Payer Authorization in your Payment Processing Profile. This will allow 3DS2 transactions to be used.

• Select the charge and settlement currencies.

• Register with BlueSnap.

Download the MerchantE SuitePayments API Plug-In

Navigate: NetSuite → Customization → SuiteBundler → Search & Install Bundles

When the list comes up, search for MerchantE Payment Gateway API and click in the name of the bundle.  The Bundle Details page will load, shown below:

Click on the Install button to load the most recent version of MerchantE Payment Gateway API to your account.

Set Up MerchantE Payment Processing Profile

Navigate: NetSuite → Setup → Accounting → Payment Processing Profiles → New

1. In the Setup section, open the Accounting submenu. Select Payment Processing Profiles and click New.

2. The Payment Gateway Integrations window will open. Click Add Profile to the left of the MerchantE option.

3. Next, on the MerchantE Credit Card Processing Profile screen, complete the Primary and Authentication Credentials sections.

4. Complete MerchantE Plugin Payment Processing Profile.

   1. Primary

      1. Web Site - Select the websites associated with the profile.

      2. Name – Select a Name for this payment processing profile that will be recognizable to employees for its specified purpose, for example MerchantE, ME-SE Region, or ME–your DBA name. Consider whether different segments of your business should use specific profiles and name them, so they are easily identifiable.

      3. Subsidiary - Select the subsidiary.

      4. Settlement Currency - The currency used to receive the payment.

      5. Charge Currencies - The currency used to make the payment.

      6. Settlement Bank Account - The account where the payment will be deposited.

      7. Support Line-Level Data - Do NOT enable.

      8. Payer Authentication - Enable 3DS payment processing for international payments, see International Payments using BlueSnap.

      9. Test Mode - Enable if you want to enter test transactions for this credit card processor.

      10. Inactive – Do NOT enable. This will make the profile inactive.

   2. Authentication Credentials

      1. Profile Key - Profile Key is a unique 32-character alpha-numeric, case-sensitive transaction passkey. This was provided on the VAR sheet sent by MerchantE when your merchant account was opened.

   3. MerchantE Configuration -

      1. Profile ID - Profile ID is a unique 20-digit number. This was provided on the VAR sheet sent by MerchantE when your merchant account was opened.

      2. Activation Code - MeS20!7

      3. Generate Token for Card Swipe Payments - Enable to use generate tokens for card swipe payments.

      4. Typical Recurring Payment Use-Case - For more information, see *Recurring Payments for SuitePayments.

      5. Default ACH Authorization Type - Select the default ACH authorization type.

   4. Payment Information -

      1. Supported Payment Methods - Highlight all payment methods you intend to accept.

      2. Gateway Request Types - Highlight Authorizations, Captures, Sales, Refunds, and Void.

5. Click Save.

At this point, you can begin processing payments with MerchantE. However, we strongly recommend that you enable some standard fraud control measures, which require you to log in to the MerchantE Reporting Portal/Business Platform.

Adding Currencies

Navigate: NetSuite → Lists → Accounting → Currencies → New

1. From the Accounting submenu of the Lists menu, select Currencies. The Currencies screen appears.

2. Click New. The Currency screen appears.

3. Fill out the fields.

   1. Name - Enter the name of the currency.

   2. Default Locale - Set the default location.

   3. ISO Code - Enter the ISO code for the currency. For more information, see ISO Currency Code.

   4. Default Exchange Rate - The default exchange rate for the currency against the base currency of the parent organization. For more information, see Currency Exchange Rates.

   5. Inactive - Check to make the currency inactive. A currency cannot be made inactive if there are pending transactions using the currency.

   6. Override Currency Format - Check to customize the currency display format.

4. Click Save.

Non-NetSuite

Using BlueSnap with the Payment Gateway depends on the type of fraud prevention measure being used.

• Non-3DS2 - Uses a device data check to generate a fraud_session_id.

• 3DS2 - Requires authentication with BlueSnap to generate a threed_secure_referenceId.

Non-3DS2 Transactions

For non-3DS2 transactions, you must include the fraud_session_id in the request parameters sent to the Payment Gateway. The fraud_session_id is sent as part of the transactionFraudInfo directly from BlueSnap. This requires you to implement Kount SDK device data collector. For more information, see Device Data Checks in the BlueSnap documentation.

Additional Information

·       Device Data Check 

·       Implementing Device Data Collector

3DS2 Transactions

Additional Information

·       3D Secure Documents

·       3D Secure Reference

·       Request and Response Examples