Confirming Sub-merchant Onboarding
Availability
If you're a new merchant looking for a marketplace solution,
contact our Sales team.
Note
The
{{ formatVariable "bt_signature" serverSdk.name }} and
{{ formatVariable "bt_payload" serverSdk.name }} variables in the code snippets below
represent parameters received from the webhook POST request. For more information, read the
documentation on parsing webhooks.
Sub-merchant approved
Once you have webhooks configured, you can listen for a
SubMerchantAccountApproved webhook that looks like this:
- C#
WebhookNotification notification = gateway.WebhookNotification.Parse(
btSignature,
btPayload
);
notification.kind == WebhookKind.SUB_MERCHANT_ACCOUNT_APPROVED;
// true
notification.MerchantAccount.Status;
// "active"
notification.MerchantAccount.Id;
// "blue_ladders_store"
notification.MerchantAccount.MasterMerchantAccount.Id;
// "14ladders_marketplace"
notification.MerchantAccount.MasterMerchantAccount.Status;
// "active"Sub-merchant declined
You can also listen for a SubMerchantAccountDeclined webhook that looks like this:
- C#
WebhookNotification notification = gateway.WebhookNotification.Parse(
btSignature,
btPayload
);
notification.kind == WebhookKind.SUB_MERCHANT_ACCOUNT_DECLINED;
// true
notification.Message;
// "Credit score is too low"
notification.Errors;
// ValidationErrorsDeclined, the webhook will contain
validation errors
indicating why the sub-merchant was declined. There are several reasons this can occur:
- Failed OFAC
- Failed Mastercard MATCH
- Failed KYC
- SSN invalid
- SSN matches deceased person