10. Available Webhooks

This platform uses webhooks to notify your application for the following action categories

1. Onboarding: You will receive webhooks when a merchant is created and updated, as well as when there is a change in the onboarding status. Additionally, webhooks will be sent for the initiation of bank account micro-deposits, when the account is ready for verification, and for both successful and failed verification attempts. For specific event names and sample payload examples, please consult the documentation located here.

2. Gateway: Webhooks will be triggered when a gateway is created, updated, or deleted for a merchant. These events help keep your system in sync with changes to gateway configurations, such as enabling/disabling a gateway or modifying gateway-specific settings. For specific event names and sample payload examples, please consult the documentation located here.

3. Transaction processing: this platform sends numerous webhook events for various types of transactions, including authorization, voiding, credit card sales, capture, transaction failures, refunds, credit transactions, ACH sales, and device sale. For specific event names and sample payload examples, please consult the documentation located here.

4. Payment Links: Webhooks will be sent for the payment link creation, updating and cancellation. Refer here for the payload examples.

5. Subscriptions: Similar to payment links, you will receive the webhooks for the creation, updating and cancellation of the subscriptions. Please consult the documentation located here for the payload examples.

6. Batch: When the payment batch is generated, BATCH_GENERATED webhook will be sent. Please refer here for the payload example.

7. Dispute management: The platform will send a dispute_created webhook when the transaction is disputed and dispute_information_updated when the information is updated. Please refer here for the details

Following are all the webhook events available:

Onboarding

1. Onboarding

Following are the webhook events for various onboarding activities

MERCHANT_CREATED

After a merchant is created, the platform will send a MERCHANT_CREATED webhook event

{
  event_uid: '220489c0dfa263d19ee1796973cdc9f6',
  event: 'MERCHANT_CREATED',
  data: {
    id: 'c404d923-226f-4aae-92da-22c1ef370434',
    account_id: 'e90c1de6-4e87-4c9e-bcbc-c535d6e349ec',
    merchant_id: 'c404d923-226f-4aae-92da-22c1ef370434'
  }
}

b. MERCHANT_UPDATED

When a merchant’s fee schedule is updated, this webhook event will include the following fields:

• fee_schedule_id – The ID of the newly assigned fee schedule.

• old_fee_schedule_id – The ID of the previous fee schedule before the change.

{
  event_uid: '220489c0dfa263d19ee1796973cdc9f6',
  event: 'MERCHANT_UPDATED',
  data: {
    id: 'c404d923-226f-4aae-92da-22c1ef370434',
    account_id: 'e90c1de6-4e87-4c9e-bcbc-c535d6e349ec',
    merchant_id: 'c404d923-226f-4aae-92da-22c1ef370434',
    external_id: 'ID123',
    fee_schedule_id: 'c404d923-226f-4aae-92da-22c1ef370weq',
    old_fee_schedule_id: 'a124d923-226f-4aae-92da-22c1ef3qwdwq'
  }
}

c. MERCHANT_STATUS_CHANGED

{
  event_uid: '220489c0dfa263d19ee1796973cdc9f6',
  event: 'MERCHANT_STATUS_CHANGED',
  data: {
    id: 'c404d923-226f-4aae-92da-22c1ef370434',
    status: 'in_review'
    account_id: 'e90c1de6-4e87-4c9e-bcbc-c535d6e349ec',
    merchant_id: 'c404d923-226f-4aae-92da-22c1ef370434'
    capabilities: ["cc", "ach"] //will be included only when the status is "Active"
  }
}

d. MICRO_DEPOSIT_INITIATED

{
  event_uid: '220489c0dfa263d19ee1796973cdc9f6',
  event: 'MICRO_DEPOSIT_INITIATED',
  data: {
    account_id: 'e90c1de6-4e87-4c9e-bcbc-c535d6e349ec',
    merchant_id: 'c404d923-226f-4aae-92da-22c1ef370434',
    bank_account_id: 'cb1c24fd-f3de-4315-a05f-19581bfa9289'
  }
}

e. MICRO_DEPOSIT_READY_FOR_VERIFICATION

{
  event_uid: 'd9e335ce77489e329b1e7abda59fb2b3',
  event: 'MICRO_DEPOSIT_READY_FOR_VERIFICATION',
  data: {
    account_id: 'bb3bc2a6-b5c7-4369-be9c-18455c63c228',
    merchant_id: '7a8c5219-f9f6-49cd-b747-561f02c36374',
    bank_account_id: 'cb1c24fd-f3de-4315-a05f-19581bfa9289'
  }
}

f. MICRO_DEPOSIT_VERIFIED

{
  event_uid: 'd9e335ce77489e329b1e7abda59fb2b3',
  event: 'MICRO_DEPOSIT_VERIFIED',
  data: {
    account_id: 'bb3bc2a6-b5c7-4369-be9c-18455c63c228',
    merchant_id: '7a8c5219-f9f6-49cd-b747-561f02c36374',
    bank_account_id: 'cb1c24fd-f3de-4315-a05f-19581bfa9289'
  }
}

g. MICRO_DEPOSIT_VERIFICATION_FAILED

{
  event_uid: 'd9e335ce77489e329b1e7abda59fb2b3',
  event: 'MICRO_DEPOSIT_VERIFICATION_FAILED',
  data: {
    account_id: 'bb3bc2a6-b5c7-4369-be9c-18455c63c228',
    merchant_id: '7a8c5219-f9f6-49cd-b747-561f02c36374',
    bank_account_id: 'cb1c24fd-f3de-4315-a05f-19581bfa9289'
  }
}

h. MERCHANT_FEE_UPDATED

When the fee schedule is changed, below webhook event is sent

{
  event_uid: '220489c0dfa263d19ee1796973cdc9f6',
  event: 'FEE_SCHEDULE_UPDATED',
  data: {
    account_id: 'e90c1de6-4e87-4c9e-bcbc-c535d6e349ec',
    fee_schedule_id: 'c404d923-226f-4aae-92da-22c1ef370weq',
    affected_merchants_count: 3,
    affected_merchants_id: [
      'c404d923-226f-4aae-92da-22c1ef370434',
      'd404d923-226f-4aae-92da-22c1ef370425',
      'e404d923-226f-4aae-92da-22c1ef370434'
     ]
  }
}

Gateway

Transactions

Payment Links

Subscriptions

Batch

Dispute

Payout