After the merchant application is submitted, BlueSnap performs an initial review. When this review is complete, we send you updates with webhooks, which typically indicate one of the following outcomes: the merchant application status was updated, or BlueSnap underwriting requests additional documents to complete the KYC/AML process.
Processing and Payout Status
BlueSnap sends updates about the merchant's status with the MERCHANT_PARTNER_ONBOARDED webhook. This webhook informs you whether the merchant was approved for processing, approved for payout, or if the application was denied:
transactionType=MERCHANT_PARTNER_ONBOARDED&merchantId=13224446&sandboxId=1165743&payoutStatus=Y&accountCanProcess=Y&merchantName="Business Name"
The parameters for this webhook can in indicate a variety of application statuses—refer to Determining Your Status for details.
The following table describes the parameters that this webhook might include:
| Parameter | Description |
|---|---|
accountCanProcess | Indicates whether the merchant account can begin processing payments. Possible values includeY (Yes), N (No), and Pending. |
merchantEmail | Merchant's email. This corresponds to the businessInfo.email value sent in the application request. |
merchantId | Unique identifier that BlueSnap assigned to the merchant. |
merchantName | Merchant's name. This corresponds to businessInfo.businessName value sent in the application request. |
payout | Indicates whether the merchant account is approved to receive payouts. Possible values includeY (Yes), N (No), and Pending. |
sandboxId | Unique identifier that BlueSnap assigned to the merchant's test account. |
Determining Your Status
The parameter values for MERCHANT_PARTNER_ONBOARDED indicate your current merchant application status. For example, a merchant can be approved to process orders but not approved to receive payout.
The key parameter that you want to watch for is merchantId. If the webhook contains merchantId, then the merchant's application status is approved to generate API credentials, and begin processing payments.
The following table describes all possible parameter combinations and how it affects the merchant's next steps:
| merchantId | payout | Next Step |
|---|---|---|
| ✅ | Y | Create the merchant API credentials and begin processing. |
| ✅ | Pending | Create the merchant credentials to begin processing.
You receive a second IPN when the merchant is approved for payout. This scenario represents Conditional Approval. |
| ❌ | Pending | You cannot create merchant credentials to begin processing. You will receive a second IPN when the merchant is approved. |
| ❌ | N | The merchant has been declined. No further updates will be sent. |
Document Request
If BlueSnap underwriting requests additional documents, you receive an APPLICATION_DOCUMENT_REQUEST webhook:
transactionType=APPLICATION_DOCUMENT_REQUEST&sandbox_id=1165743&case_id=5005a00002kAF6sAAG&ipnId=937b8a9a-a31f-48b1-8db6-9b5a331d5c9c
This webhook informs you that the BlueSnap underwriting team requires additional information to confirm details in the merchant application as part of the KYC/AML review process.
Your partner-merchant workflows determine how you learn which documents were requested and how you send those documents to BlueSnap.