Onboarding

BlueSnap Dash™ Overview

With BlueSnap Dash™, your platform will quickly go live with zero to very little development effort. BlueSnap Dash™ provides an out-of-the-box, code-free hosted application for your merchants and customers. Our global merchant application is localized and optimized for a frictionless user experience.

Account Application

As a platform, you will get a unique URL for your BlueSnap Hosted Application. You can embed this URL on your platform, website, or share it via email or chat. When your merchant opens the link, they will signup for a BlueSnap Test account. Using the test account, they can submit an account application. As a platform, you do not need to do any onboarding work. BlueSnap will do the heavy lifting for you.

📘

Note

Merchants do not need to submit the application in one sitting; their answers will automatically be saved and they can continue their application where they left off at anytime.

KYC/AML Process Details

As a payments technology company, BlueSnap is required to collect and verify information about all BlueSnap merchant accounts. Our regulators require these steps in order to prevent money laundering, tax evasion, and other financial crimes.

Once we receive your merchant’s account application data from you, we will run a series of background checks automatically. In certain cases, the information provided may need further verification. We may ask for additional documents such as:
• A government-issued photo ID
• A voided check or bank letter
• Business registration documents etc.
• Financial statements
• Processing statements
• Forward delivery schedule
• Website and description of goods related documents

If we need additional documents, someone from our underwriting team will reach out to the merchant with instructions. Submitting accurate information is crucial and it reduces the likelihood we will reach out to you for more documents. Your merchants are responsible for providing requested documents in a timely manner. As a platform, you also have the ability to track the status of your merchant’s application.

BlueSnap reviews the merchant account

You will receive an IPN based on the outcome of the review. Keep in mind that the IPN is sent only after the review process is complete.

The IPN can contain the following:

• Merchant Name (merchantName)
• Merchant Email (merchantEmail)
• Merchant ID (merchantId) [The presence of this depends on the review outcome.]
• Sandbox ID (sandboxId)
• Processing (accountCanProcess) = Y, N, or Pending
• Payout (payoutStatus) = Y, N, or Pending

Use the IPN details to determine what to do next.

Merchant ID	Processing	Payout	Next Step
✔	Y	Y	You can create the merchant credentials and begin processing.
✔	Y	Pending	You can create the merchant credentials to begin processing. You will receive a second IPN when the merchant is approved for payout.
✖	Pending	Pending	You cannot create merchant credentials to begin processing. You will receive a second IPN when the merchant is approved.
✖	N	N	The merchant has been declined; no further updates will be sent.

Account Setup

Once your merchant passes the KYC/AML verification, their account will automatically and instantly get created in our global payments network. Your merchants will then get a signup email to access their production account.

In order to connect your platform account to your merchant accounts and run transactions on their behalf, merchants will need to create API credentials and plug them into your platform.

Create credentials for your merchant (optional)

Use the Merchant ID (merchantId) from the IPN to create the merchant's credentials using the Get Merchant Credentials API request. These credentials are used to send transactions to BlueSnap on behalf of the merchant.

If your request is successful, you will receive a 200 OK response from BlueSnap with the merchant's credentials.

New Get Merchant API Credentials request

https://platform.bluesnap.com/services/2/merchants/api-credentials

Get Merchant API Credentials Parameters

Parameter	Required	Details	Description
approvalTesting	No	boolean	Default=false. If you include this parameter and set it to true, you are testing the feature.
merchantId	Yes	numeric	The merchant ID assigned to the merchant and included in the IPN.
username	No	string	The username for the merchant account. If you don't include it, the response will provide the username.
password	No	string	The password for the merchant account. Minimum 8 characters and maximum 64 characters. If you don't include a password, the response will provide it.
dataProtectionKey	No	string	The Data Protection Key for the merchant account. If you don't include it, the response will provide it. The Data Protection Key is required to perform certain functions.

Get Merchant API Credentials Request examples

Get API Credentials: Request with only merchantId

curl -v -X POST https://platform.bluesnap.com/services/2/merchants/api-credentials \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \ 
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d '
{
  "merchantId":857345
}

with all data

curl -v -X POST https://platform.bluesnap.com/services/2/merchants/api-credentials \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \ 
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d '
{
  "merchantId":857345,
  "username":"MerchantUsername",
  "password":"kjhdA@3aA",
  "dataProtectionKey": "Kru5Y50p"
}

Request in TEST mode

curl -v -X POST https://platform.bluesnap.com/services/2/merchants/api-credentials \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \ 
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d '
{
  "approvalTesting": true,
  "merchantId": 857345,
  "username": "MerchantUsername",
  "password": "kjhdA@3aA",
  "dataProtectionKey": "Kru5Y50p"
}

Get Merchant API Credentials Response examples

Successful response: 200 OK

{
    "merchantId": 857345,
    "username": "MerchantUsername",
    "password": "kjhdA@3aA",
    "dataProtectionKey": "Kru5Y50p"
}