Table of Contents |
---|
Introduction
...
threed_secure_referenceId
- Thethreed_secure_referenceId
is a unique identifier created as part of a BlueSnap 3DS transaction. If thethreed_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.transaction_id
- If thethreed_secure_referenceId
is not available, thetransaction_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 thetransaction_id
, nothing is provided to BlueSnap.
Setting Up the International Gateway
Register with BlueSnap - BlueSnap will contact you directly when the application is approved or if additional information is required.
Create BlueSnap API Credentials - You will need to create API credentials and set up 3DS2.
Provide the API Credentials to MerchantE - Customer Care will then create an account change request to add the information to your profile.
1-888-288-2692
Contact MerchantE Sales EngineeringEngineering. Sales Engineering will help you complete and test the settings.
1-888-288-2692
Registering with BlueSnap
To use the international gateway, you will first have to register with BlueSnap.
Sign up using the BlueSnap Application Portal.
https://sandbox.bluesnap.com/jsp/referred_onboarding/?referral=MERCHANTE1
For subsequent visits, login to your account.
Click the Account Application tile to start the application process.
Fill out the application.
Business Info:
Country - Select the country of origin.
Email - Add a contact email for the business.
Business Name (Doing Business As) - The informal name of the business.
Business Legal Name - The legal name of the business.
Website - The business website.
Address - Street address, city, state, and postal code for the business.
Phone - Business contact phone number.
Click Next.
Processing Info:
Product and Services Description - Keywords describing the goods and services provided.
Business Entity - Structure of the business.
Product Description - Category for the goods and services.
Sales Volume ($)
Tax ID - Tax identification number for the business.
Click Next.
Ownership Info:
Country - Company representative’s country of citizenship.
First Name - Company representative’s first name.
Last Name - Company representative’s last name.
Date of Birth - Company representative’s date of birth.
Address - Company representative’s street address, city, state, and postal code.
Phone - Contact phone number for the company representative.
Number of Owners - Number of owners who own more than 25% of the business.
Click Next.
Banking Info:
Bank Account State - Location of the Bank.
Account Type - Checking or Savings account.
Bank Name - Name of the bank.
Routing Number - Account routing number.
Account Number - Account number.
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
Navigate to the URL provided in the welcome email.
Open the Settings menu and select API Settings.
API Credentials - Set a password and click Request API credentials.
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
Navigate to the URL provided in the welcome email.
Open the Settings menu and select Fraud Settings.
Use the Fraud Settings page to customize your support. For more information, see Fraud Prevention.
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
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Set Up MerchantE Payment Processing Profile
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Adding Currencies
Navigate: NetSuite → Lists → Accounting → Currencies → New
From the Accounting submenu of the Lists menu, select Currencies. The Currencies screen appears.
Click New. The Currency screen appears.
Fill out the fields.
Name - Enter the name of the currency.
Default Locale - Set the default location.
ISO Code - Enter the ISO code for the currency. For more information, see ISO Currency Code.
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.
Inactive - Check to make the currency inactive. A currency cannot be made inactive if there are pending transactions using the currency.
Override Currency Format - Check to customize the currency display format.
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
.
Info |
---|
3DS2 is required in the European Union. If a transaction using a card from an issuer in the EU is sent and 3DS2 is not used, the transaction may be declined. |
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.
Field | Decription | Example | Transaction Types | Required? | Length | Format |
fraud_session_id | Unique ID of the shopper whose device fingerprint information was collected on the checkout page. For more information, see transactionFraudInfo. | fbcc094208f54c0e974d56875c73af7a | Card Present Sale Card Not Present Sale Card Present Pre-Authorization Re-Authorization | Required for all non-MOTO BlueSnap international transactions. | 32 | AN |
Additional Information
· Implementing Device Data Collector
3DS2 Transactions
Name | Transaction Types | Description |
3DS Authentication | 3DT | This transaction type is sent to BlueSnap to a obtain 3DS Payment token. This transaction is sent with card number and expiration date. |
Field | Decription | Example | Transaction Types | Required? | Length | Format |
threed_secure_referenceId | Sent by merchant to Payment Gateway after activating BlueSnap 3DS Token. This field is returned by a 3DT transaction and sent to BlueSnap as part of Pre-Authorization, Settle, and Sale transactions. | Sale Settle Pre-Authorization | Required for 3DS transactions. | AN |