# Swish
Swish is a popular Swedish app payment method that enables customers to pay for online purchases instantly using their banking app. Customers are redirected to the Swish app, either on their mobile device or via a QR code on a desktop, and the funds are transferred in real time.
> **Information**
>
> To enable Swish on your account, contact your account manager or [request support](https://dashboard.checkout.com/support/new?topic=case_account_management_and_access&issue=issue_account_changes).
| | |
| --- | --- |
| Model | Collecting |
| Payment flow | Redirect |
| Payment-method type | Account to account |
| Auto-capture | ✓ |
| Authorization | ✗ |
| Manual capture | ✗ |
| Refunds | ✓ Full and partial refunds |
| Chargebacks | ✗ |
| Recurring payments | ✗ |
---
## 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 Swish payments, you can subscribe the following webhooks:
| Webhook | Description |
| --- | --- |
| `payment_pending` | Occurs when an asynchronous payment request is successfully initiated.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_pending.md) |
| `payment_capture_pending` | Occurs when the payment is authorized, but not yet captured.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_capture_pending.md) |
| `payment_captured` | Occurs when a capture is successful.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_captured.md) |
| `payment_capture_declined` | Occurs when a capture is declined.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_capture_declined.md) |
| `payment_declined` | Occurs when a payment authorization request times out, or if an authorization is rejected. For example, due to insufficient funds, the issuer blocking the card, or a Do Not Honor instruction.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_declined.md) |
| `payment_expired` | Occurs when the payment expires (not applicable to 3DS payment expiries).
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_expired.md) |
| `payment_refunded` | Occurs when a refund is successful.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_expired.md) |
| `payment_refund_declined` | Occurs when a refund is declined.
[See example](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_refund_declined.md) |
The following sections describe the order in which each notification is sent, depending on the payment lifecycle:
**Successful payment**
1. `payment_pending`
2. `payment_capture_pending`
3. `payment_captured`
**Unsuccessful payment**
1. `payment_pending`
2. `payment_capture_pending`
3. `payment_declined`
**Payment refunded**
1. `payment_pending`
2. `payment_capture_pending`
3. `payment_captured`
4. `payment_refund_pending`
5. `payment_refunded`
**Payment expired**
1. `payment_pending`
2. `payment_expired`
---
## Response codes
You can receive the following response codes when processing Swish payments:
| Response code | Description |
| --- | --- |
| `10000` | Approved |
| `10200` | Deferred capture |
| `20000` | The transaction failed for unknown reasons. |
| `20001` | The external system declined the transaction. For example, bank account not accepted, not enough funds. |
| `20003` | The payment gateway declined the transaction. For example, for risk-management reasons. |
| `20006` | Error / Invalid request parameters. |
| `20017` | The customer canceled the payment. |
| `20019` | There was a timeout while waiting for the transaction result.
The customer either never completed the transaction and left the payment page open, or they closed the browser. |
| `20089 ` | Administration error. For example, a configuration error. |
| `20096` | System malfunction. |
---
## Available for
- [Web](https://www.checkout.com/docs/payments/add-payment-methods/swish/web.md): Accept Swish payments on your website with Flow, our pre-built, customizable payment user interface.
- [Payment Setup API](https://www.checkout.com/docs/payments/add-payment-methods/swish/payment-setup-api.md): Build your own UI and integrate with our Payment Setup API to process Swish payments.
- [Unified Payments API](https://www.checkout.com/docs/payments/add-payment-methods/swish/unified-payments-api.md): Build your own UI and integrate with our API to process Swish payments.