# Tabby > **Information** > > Tabby is available for Flow. Flow enables you to [accept payments on your website](https://www.checkout.com/docs/payments/accept-payments/accept-a-payment-on-your-website.md) using Checkout.com's global network of payment methods with a single integration. Start accepting payments using Tabby, a popular MENA payment method that lets customers split a payment into four installments. > **Information** > > To start accepting Tabby payments, contact your account manager or [request support](https://dashboard.checkout.com/support/new?topic=case_account_management_and_access&issue=issue_account_changes). **Gateway** | | | | --- | --- | | Model | Gateway | | Payment flow | Direct | | Auto capture | ✓ | | Manual capture | ✓ Full and partial capture | | Refund | ✓ Full and partial refund | | Void | ✓ | | Disputes | ✓ All disputes are handled directly via Tabby | | Chargeback | ✓ All chargeback are handled directly via Tabby | **Collecting** | | | | --- | --- | | Model | Collecting | | Payment flow | Direct | | Auto capture | ✓ | | Manual capture | ✓ Full and one single partial capture | | Refund | ✓ Full, partial, and multiple partial refund | | Void | ✓ | | Dispute | ✓ All disputes are handled directly via Tabby. | | Chargeback | ✓ All chargebacks are handled directly via Tabby. | > **Note** > > If you use the collecting processing model, multiple partial captures are not supported. Any partial capture is considered final and we release the remaining authorized amount. --- ## Webhooks You can manage your webhooks using the [API](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/manage-webhooks-using-the-api.md), or the [Dashboard](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/manage-webhooks-in-the-dashboard.md). When integrating Tabby, you can subscribe to the following webhooks: | Webhook | Description | | --- | --- | | `payment_pending` | Occurs when the payment request is successfully initiated. | | `payment_approved` – Manual-capture payments only | Occurs when the payment is approved by the customer. | | `payment_declined` | Occurs when the payment request is rejected. | | `payment_captured` | Occurs when the payment is successfully captured. | | `payment_capture_declined` – Manual-capture payments only | Occurs when the capture request is rejected. | | `payment_expired` | Occurs when the payment expires. | | `payment_refunded` | Occurs when the payment is fully or partially refunded. | | `payment_refund_declined` | Occurs when the refund fails. | | `payment_voided` – Manual-capture payments only | - The payment is voided after authorization
- The payment is voided after partial capture, releasing the remaining amount
- The payment expires | | `payment_void_declined` – Manual-capture payments only | Occurs when the void request fails. | --- ## Available for - [Web](https://www.checkout.com/docs/payments/add-payment-methods/tabby/web.md): Accept Tabby payments on your website with Flow, our pre-built, customizable payment user interface. - [Mobile app](https://www.checkout.com/docs/payments/add-payment-methods/tabby/mobile-app.md): Accept Tabby payments on your app with Flow for mobile, our pre-built, customizable payment user interface. - [Payment Setup API](https://www.checkout.com/docs/payments/add-payment-methods/tabby/payment-setup-api.md): Build your own UI and integrate with our Payment Setup API to process Tabby payments. - [Unified Payments API](https://www.checkout.com/docs/payments/add-payment-methods/tabby/unified-payments-api.md): Build your own UI and integrate with our API to process Tabby payments.