# Account setup
Source: https://docs.slickerhq.com/account_setup

Learn how to manage your Slicker account

## Account Creation

To create an account, please get in touch with us. Our team will collaborate with you to understand your specific requirements and set up your account accordingly.

For details on how we handle your data securely, refer to the [security section](/essentials/security). Each client’s data is stored in separate, dedicated storage for enhanced privacy and compliance.

## Managing Users

Easily add or remove users and manage their access levels:

* **Owner Access**: Grant users permissions to manage the organization.
* **Viewer Access**: Limit users to viewing the organization without management rights.

<Frame>
  <img alt="Managing user access to the organization" />
</Frame>

You can also configure global settings for user access:

* Restrict access to users with specific email domains.
* Allow users with non-matching email domains to join the organization.

<Frame>
  <img alt="Managing global organization access settings" />
</Frame>

## Managing User Authentication

Ensure secure access to your account by managing authentication settings:

* **Change Passwords**: Update your login credentials regularly.
* **Enable Two-Factor Authentication (2FA)**: Add an extra layer of security to your account.

<Frame>
  <img alt="Managing your personal authentication settings" />
</Frame>

## Accessing Slicker

Log in to the platform using one of the following methods:

1. **Username and Password**: Use the credentials you set during account creation.
2. **Magic Link**: Click the magic link sent to your registered email address. Emails will be sent from `noreply@auth.slickerhq.com`.

<Frame>
  <img alt="Logging into Slicker" />
</Frame>


# List recovery actions
Source: https://docs.slickerhq.com/api-reference/list_recovery_actions

api.yaml GET /recovery_actions



# Slicker API Overview
Source: https://docs.slickerhq.com/api-reference/overview

Slicker public API endpoints and how to interact with them

## API Basics

The Slicker API is a RESTful HTTP API that allows you to integrate with Slicker's retry data.

* **Protocol**: HTTPS only (unencrypted HTTP is not supported)
* **Base URL**: `https://api.slickerhq.com`
* **Data Format**: All requests and responses use JSON format
* **Character Encoding**: UTF-8

## Authentication

The API uses Bearer token authentication. An API key from Slicker which should be included in all API requests via the Authorization header:

```
Authorization: Bearer YOUR_API_KEY
```

You can see and manage your organization's API keys at [https://auth.slickerhq.com/org/api\_keys](https://auth.slickerhq.com/org/api_keys).

Your API key grants access to sensitive data and should be kept secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, or in API requests to other services.

## Request Limits

* **Maximum Batch Size**: Each API request can contain up to 100 items.
* **Rate Limiting**: The API implements rate limiting to ensure stable performance for all users. The default rate limits are 100 requests a second. If this does not meet your requirements, please [contact us](mailto:support@slickerhq.com) directly.
* **Concurrency**: We recommend no more than 5 concurrent requests per second

If you exceed these limits, the API will return a `429 Too Many Requests` response. Implement appropriate backoff strategies in your integration.

## API Versioning

The API version is included in the URL path (e.g., `/v1/recovery_actions`). When new versions are released, we'll provide appropriate migration guidance and timelines.

## Pagination

The Slicker API uses token-based pagination to handle large datasets efficiently. Each paginated endpoint returns a subset of results along with a pagination token for retrieving subsequent pages.

### Pagination Parameters

* **`pageSize`**: Number of items to return per page (1-100, defaults to 100)
* **`pageToken`**: Token for retrieving the next page of results. Use the `nextPageToken` from the previous response.

### Pagination Response

Each paginated response includes:

* **`{data}`**: Array of objects for the current page
* **`nextPageToken`**: Token to fetch the next page (empty if no more pages)
* **`totalSize`**: Total number of items available across all pages

### Best Practices

#### Avoiding Duplicates During Pagination

When paginating through results, new recovery actions may be created while you're processing pages. To avoid missing or duplicating entries:

1. **Use ascending sort order**: Sort by `executed_at` or `created_at` in ascending order (`asc`)
2. **Why ascending?** If you sort in descending order (`desc`) and new entries are created, they appear at the beginning of the result set, potentially causing you to skip entries that get pushed to later pages.

```bash theme={null}
# Recommended: Ascending order to avoid duplicates
GET /v1/recovery_actions?orderBy=executed_at&orderDirection=asc&pageSize=100

# Not recommended for continuous processing
GET /v1/recovery_actions?orderBy=executed_at&orderDirection=desc&pageSize=100
```

#### Example Pagination Flow

```bash theme={null}
# First request
GET /v1/recovery_actions?orderBy=executed_at&orderDirection=asc&pageSize=100

# Response includes nextPageToken
{
  "recoveryActions": [...],
  "nextPageToken": "150",
  "totalSize": 250
}

# Subsequent request using the token
GET /v1/recovery_actions?pageToken=150
```

#### Incremental Data Syncing

For regular data synchronization or warehousing:

1. **Initial sync**: Fetch all recovery actions up to a specific timestamp
2. **Subsequent syncs**: Use time-based filters with `executedAfter` to only fetch new or updated entries
3. **Always use ascending sort** to maintain consistency

```bash theme={null}
# Initial sync
GET /v1/recovery_actions?orderBy=executed_at&orderDirection=asc&executedBefore=2024-01-31T23:59:59Z

# Subsequent sync (fetch entries after last sync)
GET /v1/recovery_actions?orderBy=executed_at&orderDirection=asc&executedAfter=2024-01-31T23:59:59Z
```

### Error Handling

* **Invalid tokens**: Expired or invalid `pageToken` values will return a `400 Bad Request` error
* **Rate limiting**: If you exceed rate limits, implement exponential backoff before retrying
* **Connection issues**: Always store the last successful `pageToken` to resume pagination after connection failures


# Analytics & Reporting
Source: https://docs.slickerhq.com/essentials/analytics

Learn how to use Slicker Analytics to investigate payments, recovery, 3DS, and reports

Slicker Analytics gives you a payment and recovery workbench for understanding why revenue is lost, where retries are working, and which customer or issuer segments need attention. Start with **Ask**: it is the fastest way to turn a business question into an answer, a report, or a focused follow-up investigation.

Open Analytics from [app.slickerhq.com/analytics](https://app.slickerhq.com/analytics).

## Start with Ask

Use the **Ask** tab to ask natural-language questions about your payment and recovery data. The analytics assistant can answer directly, generate a report, and help you decide which segments are worth investigating next.

<Steps>
  <Step title="Choose the reporting window">
    Set the date range for the period you want to analyze.
  </Step>

  <Step title="Ask the business question">
    Ask what you would ask an analyst, such as "Which issuers have the lowest auth rate?" or "How is payment recovery performing this quarter?"
  </Step>

  <Step title="Review the answer or report">
    The assistant can return a direct answer or build a report that organizes charts, metrics, and narrative findings.
  </Step>

  <Step title="Follow up">
    Ask a narrower follow-up question, open the relevant dashboard tab, or save the report for later.
  </Step>
</Steps>

Good starting questions include:

| Question | What It Helps You Find |
| - | - |
| How is payment recovery performing this quarter? | Recovery rate, recovered amount, timing, and whether performance is improving or slipping. |
| Which issuers have the lowest auth rate? | Bank-level acceptance issues that may need routing, 3DS, or payment strategy changes. |
| How does recovery rate vary by country? | Geographic segments where failed payments recover differently. |
| What changed in failed payments this week? | Error-code, gateway, issuer, or payment-method shifts behind a decline spike. |
| Where are customers dropping off in 3DS? | Challenge abandonment, issuer rejection, and device or issuer patterns. |

## Save and Schedule Reports

When Ask produces a report, you can keep it as a reusable artifact instead of rebuilding the same analysis each time.

Reports can be:

* Saved for later review.
* Marked private or shared with your organization.
* Reopened from the Reports tab.
* Scheduled so recurring report runs email recipients when they finish.

Use reports for recurring reviews such as weekly recovery performance, issuer regressions, 3DS drop-off, or payment-method trends.

## Use Dashboards for Follow-Up

The dashboard tabs are supporting lenses for deeper investigation. They are useful when you already know which part of the payment or recovery funnel you want to inspect, or when Ask points you toward a specific segment.

These views will continue to evolve as Slicker adds new analytics surfaces, but the main investigation areas are:

| Tab | Use It To |
| - | - |
| Invoices | Understand invoice collection, first-attempt success, recovery rate, invoice churn, and failed invoice segments. |
| Transactions | Analyze authorization rate, payment volume, gateway performance, payment initiation, issuer behavior, and raw decline codes. |
| Failure Analysis | Study the failed-invoice cohort: what entered dunning, what recovered, what stayed in recovery, and what became lost revenue. |
| Recovery | Measure where recovery is happening, how long it takes, how many retries are needed, and what share Slicker is driving. |
| 3DS | Investigate 3D Secure enrollment, challenge completion, abandonment, authentication results, issuers, devices, and customers. |

## Filters and Time Controls

Use the date range picker to set the reporting window. Trend charts can be grouped daily, weekly, or monthly.

Use filters to narrow the analysis to a specific slice of your business, such as:

* Countries and currencies.
* Payment methods and card brands.
* Error codes and normalized Slicker error types.
* Gateway or payment processor.
* Business entities, plans, or billing cycles when available.

Filtered views are useful when a headline metric looks stable but one segment is degrading.

## Invoices

Use **Invoices** for invoice-level collection and recovery performance. An invoice is counted once, even if it has multiple payment attempts.

Common questions:

* What percentage of invoices are paid on the first attempt?
* How much collection improves after recovery activity?
* Which error codes, countries, card brands, payment methods, or billing cycles drive failed invoices?
* Which segments recover well, and which segments turn into invoice churn?

The overview compares first-attempt outcomes with final invoice outcomes, so you can see the recovery uplift between the initial payment attempt and the eventual result.

## Transactions

Use **Transactions** for authorization-level analysis. A transaction is one authorization attempt, so retries on the same invoice appear as separate rows.

Transactions helps you inspect:

* Authorization rate and succeeded or failed volume over time.
* Gateway performance across payment processors.
* Decline reasons by normalized Slicker error type, provider error code, and scheme error code.
* Issuer country, card brand, card product, and payment method behavior.
* Customer-initiated, merchant-initiated, and MOTO transaction performance.
* Issuer-level patterns that may indicate routing, 3DS, or processor issues.

This tab is best for diagnosing payment acceptance problems before they become invoice recovery problems.

## Failure Analysis

Use **Failure Analysis** to study invoices that had at least one failed payment attempt and entered recovery.

Recovery status means:

| Status | Meaning |
| - | - |
| Recovered | The invoice was eventually paid. |
| In Recovery | The retry or dunning window is still open. |
| Failed Recovery | The recovery window closed without payment. |

Key views include:

* **Outcomes**: How the failed-invoice cohort split between recovered, in recovery, and failed recovery.
* **First Failure**: The first failed transaction that pushed each invoice into recovery.
* **Subsequent Failures**: Retry attempts that also failed after the initial failure.
* **Error Code**: Normalized error types, provider codes, and scheme codes within the failed cohort.
* **Issuer**: Bank-level, country-level, and card-brand patterns inside the failed cohort.

Use this tab when you need to understand why some failed invoices recover and others do not.

## Recovery

Use **Recovery** to measure recovery effectiveness and efficiency.

The recovery views show:

* Recovered invoices and recovered amount.
* Recovery method, such as Slicker retries, recovery emails, or other recovery paths.
* Average time from first failure to successful recovery.
* Number of retries needed before recovery.
* Retry success rate and retry cost ratio.
* Slicker's share of recovery activity compared with other retry sources.

This tab is useful for monitoring whether recovery is improving, slowing down, or becoming more expensive in retry attempts.

## 3D Secure

Use **3DS** to understand authentication performance for card payments that enter a 3D Secure flow.

The 3DS views cover:

* Enrollment volume, challenge rate, authentication success, and liability shift.
* Funnel drop-off from enrollment to challenge completion.
* Abandonment versus issuer challenge failure.
* EMVCo cancel and reason-code breakdowns.
* Performance by card brand, currency, device type, gateway, issuer, issuer country, and customer.

Use this tab when authentication required, challenge abandonment, or issuer rejection is affecting payment success.

## Dashboard and Recovery Pages

The main [Dashboard](https://app.slickerhq.com/dashboard) is still the best place for a quick executive overview of subscription health, payment health, churn, and recovered revenue.

The [Revenue Recovery page](https://app.slickerhq.com/revenue-recovery) provides operational visibility into past and scheduled recovery attempts.

Use Analytics when you need deeper investigation, segment comparisons, or reusable reporting.

## Recommended Workflows

| Workflow | Where to Start |
| - | - |
| Weekly payment health review | Ask what changed in payments and recovery, then inspect Transactions and Invoices. |
| Decline spike investigation | Ask what caused the spike, then inspect Transactions error code, gateway, issuer, and payment initiation views. |
| Recovery performance review | Ask how recovery is trending, then inspect Recovery and Failure Analysis. |
| Lost revenue deep dive | Ask which segments are driving failed recovery, then inspect Failure Analysis first failures, subsequent failures, error code, and issuer views. |
| 3DS conversion issue | Ask where 3DS users are dropping off, then inspect 3DS funnel, failures, breakdowns, issuers, and customers. |
| Executive reporting | Ask the question once, save the generated report, and schedule it from Reports. |

## Related Docs

* [Recovery Strategies](/essentials/strategies)
* [Emails](/essentials/emails)
* [Multi Gateway Routing](/essentials/multi_gateway_routing)
* [3D Secure Authentication](/guides/3ds)


# Configuration
Source: https://docs.slickerhq.com/essentials/configuration

Learn how to configure and customize Slicker recovery settings

### Recovery Settings

To access the recovery settings, you can:

* **Use the menu:** Click the user icon in the bottom-left corner and select **"Recovery Settings"**.

<Frame>
  <img alt="Navigating to the settings page" />
</Frame>

* **Direct link:** [Open Recovery Settings](https://app.slickerhq.com/settings/recovery).

By default, Slicker dynamically manages recovery settings based on factors such as issuer bank preferences, customer behavior, and other variables that influence the recovery process. These intelligent defaults are designed to optimize results and minimize churn.

However, if you prefer, you can customize settings to suit your needs. Adjustable options include:

* Maximum number of retries
* Minimum time between retries
* Minimum time before the first retry

<Frame>
  <img alt="Recovery settings example configuration" />
</Frame>

### Custom Settings

Need a specific setting that’s not currently available? Let us know by [contacting us](https://www.slickerhq.com/contact), and we’ll work with you to address your requirements.


# Emails
Source: https://docs.slickerhq.com/essentials/emails

Learn how Slicker's automated emails recover failed payments alongside retries

Recovery emails contact customers when a failed payment needs their attention. They complement [payment retries](/essentials/strategies): retries handle failures that may clear on their own, while emails help customers replace an expired card, approve a transaction, or resolve another account issue.

<Card title="Set up recovery emails" icon="paper-plane" href="/guides/email-dunning-launch-guide">
  Follow the launch guide to configure your sending domain, DNS, tracking, branding, scenarios, testing, and reporting.
</Card>

## When Emails Help

Payment retries work well for temporary bank declines or insufficient funds at the moment of charge. Customer communication is more useful when the failure requires action, including:

* A hard decline that another retry will not resolve.
* An expired, lost, blocked, or inactive card.
* A bank approval or authentication step.
* A stopped recurring payment or cancelled billing agreement.

Slicker coordinates the two channels without treating them as the same action. Retry timing can be optimized around the next collection attempt while email timing and copy can focus on getting a response without over-communicating.

## How Recovery Emails Work

<Steps>
  <Step title="A failed payment matches a scenario">
    A scenario represents a type of payment failure and the audience that should receive an email. When more than one scenario matches, the higher-priority scenario wins.
  </Step>

  <Step title="Slicker selects the appropriate template">
    A scenario contains one or more enabled templates. Sequence positions distinguish first, middle, and final messages; multiple templates at the same position can be used as copy variants.
  </Step>

  <Step title="The email is scheduled and sent">
    Slicker renders customer and invoice variables, applies the scenario's email configuration, and sends from your verified domain.
  </Step>

  <Step title="Results appear in Emails">
    You can inspect scheduled and sent messages, recovery outcomes, scenario performance, and—when tracking is configured—open and click activity.
  </Step>
</Steps>

## Scenarios and Templates

Slicker prepares an initial set of scenarios and templates for your payment-failure patterns during onboarding. They are a starting point, not a locked configuration.

On the [Scenarios](https://app.slickerhq.com/dunning/scenarios) page you can:

* Review enabled and disabled scenarios and filter them by trigger.
* Change a scenario's name, description, trigger, priority, assigned email configuration, and enabled status.
* Review its templates, sequence positions, and performance.
* Edit template names, subjects, and message content using the available customer, invoice, and payment variables.
* Add templates and send test emails before using new copy with customers.

Use **Detailed View** to compare sent volume, recovered invoices, recovery rate, and available engagement metrics across scenarios. Higher scenario priorities are evaluated first, so review overlapping scenarios carefully before enabling them.

## Sending From Your Domain

Customers receive messages from an address on a domain you control. Use a dedicated subdomain such as `billing.example.com` or `payments.example.com` instead of the root `example.com`.

A subdomain separates recovery-email reputation from login, support, and marketing mail. It is also required for Slicker's custom-domain open and click tracking. Configure the domain, DNS records, sender name, from address, reply-to address, and optional BCC recipients in [Emails → Settings](https://app.slickerhq.com/dunning/settings).

SPF and DKIM records authenticate sending and must be verified before emails can be sent. DMARC is recommended for spoofing protection and deliverability. DNS changes can take up to 48 hours to propagate; the Settings page shows the live status of every record and lets you re-run verification.

## Branding and Calls to Action

An email configuration controls the sender domain and shared presentation of an email. In [Styling & configuration](https://app.slickerhq.com/dunning/styling), you can manage:

* The sending domain, logo, alignment, font, and button color.
* CTA text and either a static payment-page URL or a [customer-specific dynamic destination](/guides/email-dunning-launch-guide#dynamic-billing-page-urls).
* Help text, signature, and footer links.
* Multiple configurations for different brands or business units, including one default.
* A live preview and test email.

A scenario can use a specific email configuration or fall back to the default.

## Tracking and Reporting

Optional tracking DNS records route images and links through your sending subdomain. Slicker records an open when the tracking image is requested and a click when a tracked link is followed. Email clients can block images or prefetch links, so engagement metrics are useful directional signals rather than proof that a person read an email.

The Emails area provides three reporting levels:

* **Overview** — scheduled emails, recovered invoices and amount, total emails sent, and available open and click rates.
* **Scheduled Emails and Sent Emails** — recipient-level records with timing, invoice, scenario, message preview, and recovery information.
* **Analytics** — scenario recovery rates, send volume and timing, monthly recovered invoices and amount, plus engagement charts when tracking is configured.

For broader recovery reporting, see [Analytics & Reporting](/essentials/analytics).

## Connect Email Outcomes to Your Systems

Use an [email-outcome webhook](/guides/email-dunning-launch-guide#email-outcome-webhooks) when another system should react after Slicker attempts a recovery email—for example, to enqueue an SMS or update an internal workflow. Webhooks include structured customer, invoice, scenario, and email-attempt data and support idempotent retry handling.

## Next Step

Follow the [Email dunning launch guide](/guides/email-dunning-launch-guide) for the complete setup sequence, DNS troubleshooting, tracking behavior, launch checklist, and advanced configuration.


# FAQs
Source: https://docs.slickerhq.com/essentials/faq

Frequently asked questions about Slicker

### What is Slicker, and how does it help my business?

Slicker is a revenue recovery platform that helps subscription businesses reduce involuntary churn by optimizing payment retries, improving payment health, and providing actionable insights through analytics.

### How do I integrate with Slicker?

Slicker integrates directly with popular payment processors and billing platforms like Stripe, Recurly, and Chargebee. For more details, see our [Integrations](/integrations/overview) page.

### I use a billing platform that Slicker supports, but my payment processor is not listed. Can I still use Slicker?

Yes! We only need to integrate with your billing platform to get started. Using the data from your payment processor(s) takes the recovery strategies to the next level and is strongly recommended, but it is not required.
If you have requirements for a specific payment processor, [contact us](https://www.slickerhq.com/contact) to discuss your needs.

### What types of businesses benefit the most from using Slicker?

Subscription-based businesses, particularly those experiencing high involuntary churn due, benefit the most from Slicker. Not sure if your business fits? [Contact us](https://www.slickerhq.com/contact) to get a free payments audit and discuss your needs.

### How does Slicker ensure the security of my data?

Slicker uses separate data stores for each client and implements encryption at rest and in transit. We are also working towards SOC 2 compliance. For more details, visit our [Security & Compliance](/essentials/security) page.

### Is my data shared with other clients?

No, Slicker uses separate data stores for each client to ensure complete data isolation and privacy.

### How does the revenue recovery process work?

Slicker uses machine learning and industry heuristics to optimize retries for failed payments. We tailor strategies to individual customers based on factors like BINs, geography, and payment timing. Learn more on our [Recovery Strategies](/essentials/strategies) page.

### Can I customize Slicker’s recovery strategies?

Yes, clients can adjust certain parameters, such as maximum retries and minimum time between retries, while most settings are dynamically controlled by Slicker. See the [Configuration](/essentials/configuration) page for details.

### How do I set up my Slicker account?

Contact our team to create your account. We’ll collaborate with you to configure it based on your specific requirements. For more information, see the [Account Setup](/account_setup) guide.

### What information do I need to provide during setup?

You’ll need to provide details about your payment and billing systems and any specific requirements for recovery strategies or integrations.

### How long does it take to get started with Slicker?

Adding the integrations to your billing and payments providers takes 5 minutes. Initial analytics are available within 10 minutes, and full recovery strategies can start running withing a couple of hours.

### What is Slicker’s pricing model?

Our pricing is based on the revenue recovered for your business. We won't charge you more than the recovered revenue. [Contact us](https://www.slickerhq.com/contact) for a customized quote.

### Does Slicker offer customer support?

Yes, we provide support via email, shared Slack channel, and a dedicated support engineer.

### How do I report an issue or security vulnerability?

Please report any issues or vulnerabilities to [security@slickerhq.com](mailto:security@slickerhq.com). We take security concerns seriously and will address them promptly.

### What insights can I get from the dashboard?

The dashboard provides key metrics, including churn breakdown, subscription health, payment health, and revenue recovery performance. Learn more on the [Analytics & Reporting](/essentials/analytics) page.

### How frequently is data updated in the dashboard?

Dashboard data is updated in near real-time to ensure accuracy and relevance.


# Grace Periods
Source: https://docs.slickerhq.com/essentials/grace_periods

Decide how long Slicker keeps recovering a failed payment, and what happens when the grace period ends

### Grace Periods

When a payment fails, your billing provider decides how long to keep trying and what to do when it gives up. Those defaults are rarely the ones you would choose. Often the provider cancels or writes off the customer before Slicker, or the customer themselves, has had a fair chance to recover the payment.

Grace Periods let you set that policy yourself. You choose how long Slicker keeps working a failed invoice, and what should happen once that window closes, so recovery runs on your schedule instead of your gateway's.

### Why it matters

Billing providers apply blunt, one-size-fits-all rules when payments fail.

Some give up too early. Mandate-based and regulated recurring payment methods (for example SEPA Direct Debit, or recurring cards in India under RBI e-mandate rules) are often dropped after a single attempt, because their rules limit how and when a failed charge can be re-presented. The provider then cancels the subscription or writes off the invoice a few days later, even though the payment was still recoverable.

Others give up too late, or never. Turn that behaviour off and unpaid invoices and delinquent subscriptions build up with nothing to close them out.

A grace period sits in between. Slicker keeps recovering for as long as it is worth it, then takes a clean, deliberate action.

### How it works

<Steps>
  <Step title="Set the grace period">
    Choose how many days, measured from the first failed payment, Slicker should keep recovering an invoice. Throughout this window Slicker keeps dunning and retrying using your configured [strategies](/essentials/strategies).
  </Step>

  <Step title="Choose what happens when it ends">
    Pick the action Slicker applies once the grace period expires: cancel the subscription, mark the invoice as uncollectible, or leave it overdue for your team to handle.
  </Step>

  <Step title="Slicker does the rest">
    Slicker runs the window automatically every day and applies your end-of-grace action as soon as an invoice ages out, with a full record of every decision.
  </Step>
</Steps>

### What you can configure

<CardGroup>
  <Card title="Grace period length" icon="hourglass-half">
    The number of days from the first failure that Slicker keeps recovering before it acts.
  </Card>

  <Card title="Subscription action" icon="repeat">
    What happens to the subscription when the window closes, such as cancelling it or leaving it untouched.
  </Card>

  <Card title="Invoice action" icon="file-invoice-dollar">
    What happens to the unpaid invoice, such as marking it uncollectible or leaving it overdue.
  </Card>

  <Card title="Full audit trail" icon="list-check">
    Every grace-period decision is recorded, so you always know what Slicker did, when, and why.
  </Card>
</CardGroup>

### Availability

<Note>
  Grace Periods are available today for Stripe Billing. Support for more billing providers is on the way. If you are on another provider and want early access, [get in touch](https://www.slickerhq.com/contact).
</Note>

For Stripe, Slicker needs to own the recovery window, which takes two things:

1. Set Stripe to leave failed invoices overdue rather than cancelling or writing them off, so Stripe does not close the customer before your grace period is up. The [Stripe Billing integration guide](/integrations/billing/stripe) walks through it.
2. Give Slicker permission to apply your end-of-grace action. Marking an invoice uncollectible uses the `Write` on `Invoices` permission Slicker already needs. Cancelling a subscription also needs `Write` on `Subscriptions`. The [Stripe Billing integration guide](/integrations/billing/stripe) covers the exact API key setup.

### Getting started

Grace Periods are set up by our team as part of your recovery configuration. [Contact us](https://www.slickerhq.com/contact) and we will set the window and end-of-grace actions to match how your business works.

<Info>
  **Looking for dynamic grace periods?** Fixed windows are just the start. We are working on grace periods that adapt on their own, based on payment method, customer value, and how likely a payment is to recover, so every invoice gets the right amount of runway. If that is something you want, [talk to us](https://www.slickerhq.com/contact). It is on our roadmap and we would love your input.
</Info>

With Grace Periods, you decide when a failed payment is really done, not your billing provider.


# Multi Gateway Routing
Source: https://docs.slickerhq.com/essentials/multi_gateway_routing

Learn how Slicker optimizes payment success by leveraging multiple gateways

### Multi Gateway Routing

Multi Gateway Routing allows you to use multiple payment gateways to optimize payment success rates. When a payment fails with a specific error code on one gateway, Slicker intelligently retries the payment on another gateway, increasing the likelihood of successful processing.

### How It Works

Slicker uses data from past payments, including gateway performance metrics, error codes, and transaction details, to predict which gateway has the highest probability of success for a given transaction. This dynamic routing ensures that your payments are always processed through the most effective channel.

For example if a payment fails on **Gateway A** with an error like `generic_decline`, Slicker can route the retry to **Gateway B** based on historical success rates for this type of user and this type of error.

### Availability

This feature is available for billing providers that support integration with multiple payment gateways. If your billing provider enables this capability, Slicker can manage the routing process seamlessly.

### Benefits of Multi Gateway Routing

* **Higher Success Rates**: By routing retries to gateways with higher predicted success, you recover more revenue.
* **Reduced Churn**: Successful retries mean fewer failed transactions and lower involuntary churn.
* **Data-Driven Optimization**: Decisions are based on real-time insights from your payment data and historical trends.

### Getting Started

If your billing provider supports multiple payment gateways, [contact us](https://www.slickerhq.com/contact) to enable Multi Gateway Routing. We’ll configure the feature based on your setup and provide all the necessary guidance to maximize its benefits.

***

With Multi Gateway Routing, Slicker ensures your transactions have the best chance of success, helping you recover more revenue and enhance customer satisfaction.


# Security & Compliance
Source: https://docs.slickerhq.com/essentials/security

Learn how Slicker ensures the security and compliance of your data

At Slicker, we prioritize the security and compliance of your data to provide you with peace of mind and ensure that your sensitive information is protected at all times. Below, we outline the key measures and practices we implement.

### Data Isolation

We ensure strict data segregation by using **separate data stores for each client**. This approach guarantees that your data remains isolated and secure, preventing unauthorized access between clients.

### Encryption

To safeguard your data:

* **Encryption at Rest**: All stored data is encrypted using industry-standard algorithms to protect it from unauthorized access.
* **Encryption in Transit**: We use secure protocols such as HTTPS to encrypt data transmitted between our systems and your applications.

These measures help ensure your data remains protected throughout its lifecycle.

### Role-Based Access Control (RBAC)

Slicker implements **role-based access control** to manage permissions effectively:

* **Administrator Access**: Users can manage the organization, including adding or removing users.
* **Viewer Access**: Users have read-only access to view data without making changes.

This ensures that only authorized personnel can access sensitive areas of your account. For more details, see [Account Setup](/account_setup).

### Incident Response and Security Reporting

Slicker has a robust incident response plan to quickly detect, address, and mitigate any security issues.

* **Incident Handling**: We continuously monitor for security threats and maintain a structured protocol for managing incidents.
* **Client Notification**: In the unlikely event of a security breach, we promptly notify affected clients with actionable steps.

If you discover a vulnerability or have security concerns, please report them to us at **[security@slickerhq.com](mailto:security@slickerhq.com)**. We value your input in maintaining a secure environment.

### Policy Reviews and Availability

Our security policies are reviewed regularly to stay compliant with evolving standards and best practices.

* **On-Demand Access**: Clients can request copies of our policies for review by their security teams. To request access, please [contact us](https://www.slickerhq.com/contact).

These frequent reviews ensure that we remain proactive in addressing new threats and meeting the latest compliance requirements.

### Compliance

We are committed to meeting the highest industry standards for compliance:

* **SOC 2 Compliance**: Slicker is actively working towards achieving SOC 2 certification, demonstrating our dedication to robust security, availability, and confidentiality practices.

***

Your trust is our top priority, and we continually review and enhance our security and compliance measures to stay ahead of evolving threats. If you have any questions or require more information, please don’t hesitate to [contact us](https://www.slickerhq.com/contact).


# Recovery Strategies
Source: https://docs.slickerhq.com/essentials/strategies

Learn how Slicker recovers revenue

### Recovery Strategies

At Slicker, we understand that no two businesses are the same, and we tailor our recovery strategies to meet the unique needs of each client. Our approach leverages a combination of **industry heuristics** and advanced **machine learning models** to optimize revenue recovery.

### Tailored to Your Business

Our strategies analyze numerous features to make informed and individualized decisions for each customer. Key factors include:

* **Bank Identification Numbers (BINs)**: To understand issuer-specific preferences.
* **Payment Time**: Insights into the optimal retry windows based on customer behavior.
* **Transaction Amounts**: Tailoring strategies for small versus large transactions.
* **Geography**: Adapting to regional payment trends and customer behavior.
* **Customer History**: Behavioral patterns like past successful retries and engagement levels.
* **Payment Method**: Preferences based on credit cards, direct debits, or digital wallets.

These inputs allow Slicker to make dynamic, data-driven decisions for each customer instead of relying on a one-size-fits-all strategy.

### Dynamic and Adaptive Strategies

Our retry strategies are continuously evolving. By analyzing results and incorporating feedback, we fine-tune our algorithms to improve performance over time. This ensures that your recovery efforts remain effective as market and customer conditions change.

### Client Control and Customization

While most parameters of the retry strategies are dynamically controlled by Slicker to maximize efficiency, we provide clients with the ability to set certain boundaries, such as:

* Maximum number of retries
* Minimum time between retries

For more details on configuring these settings, visit our [Configuration Page](/essentials/configuration).

### Continuous Improvement

Slicker’s algorithms are always learning from past results, ensuring that strategies are adjusted based on real-world performance. This iterative process allows us to stay ahead of emerging trends and deliver optimal results for our clients.

By combining tailored decision-making with the latest in machine learning and dynamic control, Slicker ensures that your revenue recovery strategy is as effective and unique as your business.


# 3D Secure Authentication
Source: https://docs.slickerhq.com/guides/3ds

Learn about 3D Secure (3DS) authentication and its impact on recurring payments

### Overview of 3D Secure Authentication

3D Secure (3DS) is an additional layer of security for online card transactions, requiring the cardholder to authenticate their payment, typically through a password, one-time code, or biometric verification. It is widely used in regions with stringent payment security regulations, such as:

* The **European Economic Area (EEA)** under PSD2 regulations.
* **India**, where the Reserve Bank of India mandates 3DS for all online card transactions.

### Importance of Supporting 3D Secure

Supporting 3DS is crucial for businesses that operate in regions where it is mandated or preferred. Proper implementation reduces fraud, ensures compliance with regional regulations, and builds trust with customers. Without 3DS support, merchants risk failed payments and customer dissatisfaction.

### How 3D Secure Impacts Recurring Payments

3D Secure behaves differently for recurring payments compared to one-off transactions. The first payment in a subscription typically requires 3DS authentication. Once this initial payment is authorized, subsequent recurring transactions may bypass 3DS, but this depends on the card issuer and the specifics of the transaction.

However, improper implementation of 3DS can lead to challenges. For example, errors such as **transaction\_not\_allowed** often indicate that 3DS authentication is required for a recurring payment. In such cases, the payment cannot be completed unless the customer manually re-authenticates. If these issues are not addressed promptly, they can result in payment failures and, ultimately, involuntary churn.

### What Can Be Done?

**Customer Communication**

Retrying such payments as a merchant is rarely successful since 3DS errors typically require customer interaction. The best approach is to contact affected customers and guide them through re-authenticating their payments.

**How Slicker Helps**

Slicker provides tools to manage 3DS-related issues effectively:

* **3DS Failure Analysis**: Use [Analytics → 3DS → Failures](https://app.slickerhq.com/analytics?tab=three_ds\&subtab=failures) to break down challenge failures by reason over time, cancellation code, and issuer reason code. This helps distinguish customer abandonment, issuer declines, and ACS or gateway problems.
* **Tailored Messaging**: By understanding the specific error, you can send personalized messages to customers, making the resolution process more effective.
* **Auditing Suggestions**: If many 3DS-related errors occur, it might indicate issues with your 3DS implementation or that of your billing provider. Auditing the setup can help resolve systemic problems.

### Conclusion

3D Secure authentication is a critical component of modern payment systems, especially in regions like India and the EEA where it is mandated. While it adds security, improper handling can lead to spikes in errors and failed payments. With Slicker’s insights and tools, you can address these issues proactively, ensuring smoother transactions and improved customer experience.


# Email dunning launch guide
Source: https://docs.slickerhq.com/guides/email-dunning-launch-guide

Configure, test, launch, and monitor recovery emails

Use this guide to take recovery emails from initial setup to production. It covers your sending domain, DNS authentication, engagement tracking, sender identity, branding, Slicker's initial scenarios and templates, testing, launch, and reporting.

For the product concepts first, read the [Emails overview](/essentials/emails).

## Before You Start

Gather the following before configuring emails:

* Access to the DNS provider for the domain you will use.
* A monitored support address for customer replies.
* Your logo, brand color, help text, signature, and footer links.
* The payment or billing-page URL customers should reach from the CTA.
* An owner who will review scheduled sends and recovery performance after launch.

If another system already sends payment-recovery emails, decide which cohorts each system owns. Running both systems for the same customer and failure can create duplicate messages. A controlled comparison is fine, but define the split before enabling Slicker scenarios.

## Phase 1: Set Up the Sending Domain

### Choose a Dedicated Subdomain

Use a subdomain such as `billing.example.com`, `payments.example.com`, or `recovery.example.com`.

This separates recovery-email reputation from your root domain and from other important mail such as login, support, and marketing messages. It also lets Slicker serve tracked images and links from a domain aligned with the sender.

<Warning>
  A root domain such as `example.com` can be used only after acknowledging the deliverability trade-off. Open and click tracking cannot be configured on a root domain, so a dedicated subdomain is strongly recommended.
</Warning>

### Add the Domain

<Steps>
  <Step title="Open email settings">
    Go to [Emails → Settings](https://app.slickerhq.com/dunning/settings) and select **Add Your First Domain** or **Add another domain**.
  </Step>

  <Step title="Enter the full sending domain">
    Enter the subdomain, for example `billing.example.com`. Do not enter a protocol, path, or email address.
  </Step>

  <Step title="Copy the generated DNS records">
    Slicker generates the exact type, name, value, priority, and TTL that your DNS administrator should publish.
  </Step>
</Steps>

### Publish the DNS Records

| Record group | Purpose | Requirement |
| - | - | - |
| SPF and DKIM | Authorize sending and cryptographically authenticate each message. | Required before sending. |
| DMARC | Tells receiving servers how to handle failed authentication and helps prevent spoofing. | Recommended. Start with the policy Slicker provides. |
| Click & Open Tracking | Routes tracked images and links through your sending subdomain. | Optional, but required for engagement metrics. Available only for a subdomain. |

Add every record exactly as displayed in Slicker. Most DNS providers automatically append your DNS zone to the record name, so the Settings page shows names without the zone where appropriate. If verification cannot find a record, check whether your provider expects the full hostname instead.

<Info>
  DNS changes are not immediate. Propagation can take up to 48 hours depending on the provider and existing TTL. A pending record during that window does not necessarily mean the value is wrong.
</Info>

After publishing the records, return to the domain's **DNS Records** panel and select **Verify DNS**. The UI shows each record as pending or verified. If a record remains pending after propagation:

1. Compare its type, name, value, priority, and TTL with the Slicker value.
2. Check that the provider did not append the zone twice, such as `record.billing.example.com.example.com`.
3. If you used the short record name, try the full hostname, or vice versa, based on your provider's convention.
4. Remove conflicting records only after confirming they are not used by another mail service.
5. Re-run **Verify DNS**.

SPF and DKIM must both verify before Slicker can send recovery emails from the domain.

### Configure the Sender Identity

Complete the domain's **Email Settings**:

* **From email prefix** — use a recognizable purpose such as `billing`, `payments`, or `subscriptions`. Avoid `noreply` or `no-reply`; they discourage responses and can hurt trust and deliverability.
* **Friendly name** — use the brand name customers recognize, such as `Acme Billing`.
* **Reply-To** — use an active, monitored mailbox that can resolve billing questions.
* **BCC** — optionally add comma-separated internal recipients when your compliance or audit process requires a copy of every message.

If you configure multiple domains, set the normal fallback domain as **Default**. A non-default domain can be assigned to a specific email configuration. The default domain cannot be deleted until another domain becomes the default.

## How Open and Click Tracking Works

When tracking DNS is configured, links and images in a recovery email use your sending subdomain rather than an unrelated third-party hostname. Behind the scenes, Slicker proxies those requests through its tracking infrastructure:

* An **open** is recorded when the email's tracking image is requested.
* A **click** is recorded when a recipient follows a tracked CTA, content, or footer link.
* Analytics excludes activity identified as automated bot traffic from engagement charts.

Tracking does not change whether the email can be sent. Without the tracking records, recovery emails continue to send, but opens and clicks are not collected.

<Note>
  Open and click data is approximate. Some email clients block remote images, and security scanners may prefetch images or links. Use engagement rates to compare trends and copy variants, not as proof that an individual person read a message.
</Note>

## Phase 2: Create the Email Configuration

Go to [Emails → Styling & configuration](https://app.slickerhq.com/dunning/styling). An email configuration combines a sending domain with the shared visual and CTA settings applied to templates.

<Steps>
  <Step title="Name the configuration and choose a domain">
    Use a name that identifies the brand or business unit. Select a verified sending domain and make the configuration the default if scenarios should use it unless another is assigned.
  </Step>

  <Step title="Add your branding">
    Upload a logo or provide a hosted logo URL, then choose its height and alignment. Select an email-safe font and your CTA button color.
  </Step>

  <Step title="Configure the CTA">
    Add clear button text and a valid HTTPS billing or payment-update URL. Leave button text empty only when the email should have no CTA.
  </Step>

  <Step title="Complete the support content">
    Add help text, a recognizable signature, and valid footer links. Remove placeholder `#` links before launch.
  </Step>

  <Step title="Preview and test">
    Review the live preview and send a test email to real inboxes used by your team. Save the configuration when the sender, links, images, and replies behave correctly.
  </Step>
</Steps>

Create separate configurations when brands, business units, domains, or CTA destinations need different presentation. Each scenario can use a named configuration or the default.

## Phase 3: Review Scenarios and Templates

Slicker prepares an initial set of scenarios and templates for your business during onboarding. Open [Emails → Scenarios](https://app.slickerhq.com/dunning/scenarios) to review them before launch.

### Review Every Scenario

The scenario list shows its name, payment-failure trigger, priority, template count, and enabled status. **Detailed View** adds performance metrics when data is available.

Open a scenario to review or change:

| Setting | What it controls |
| - | - |
| Name and description | How the scenario is identified by your team. |
| Trigger | The payment-failure category the scenario handles. |
| Priority | Which scenario wins when the same candidate matches more than one enabled scenario. Higher values are evaluated first. |
| Email configuration | The sending domain, branding, and CTA configuration used for its templates. |
| Enabled | Whether the scenario can schedule recovery emails. |

Keep a scenario disabled while its audience or copy is still under review. When priorities overlap, confirm that the most specific or important scenario has the higher value.

### Review and Edit Templates

Each scenario contains its email templates. Open a template to review the rendered preview and edit its name, description, subject, and body. The editor lists the variables available for customer, payment, invoice, and company data.

Templates use a sequence position:

* **First** — the first-touch message.
* **Middle** — a follow-up while recovery remains open.
* **Final** — the last message in the sequence.

You can add another template from the scenario page and choose its sequence position, priority, and initial enabled status. When several enabled templates are available for the same step, Slicker can select between those copy variants using their configured traffic weights.

For each template:

1. Use a subject that clearly identifies the account or payment action without exposing sensitive data.
2. Explain what failed and what the customer should do next.
3. Keep the CTA consistent with the action in the copy.
4. Check that every variable renders correctly in the preview.
5. Send a test email and open it on both desktop and mobile.

<Warning>
  A successful test verifies rendering and delivery of the test message. It does not prove that every production customer has complete source data or that every customer-specific URL can be resolved.
</Warning>

## Phase 4: Validate and Launch

Before enabling production scenarios, confirm:

* The dedicated subdomain is in use.
* SPF and DKIM show as verified; DMARC is published.
* Tracking DNS is verified if you need open and click metrics.
* The friendly name, from address, reply-to address, and optional BCC list are correct.
* Every active scenario points to the intended email configuration.
* Every active scenario has suitable enabled templates for its sequence.
* Subjects, variables, logo, CTA, signature, and footer links render correctly in test inboxes.
* Static and customer-specific CTA destinations use HTTPS and lead to the intended account.
* Another recovery-email system will not message the same customers unintentionally.
* Your support and billing teams know what customers will receive and where replies will arrive.

Enable the agreed scenarios after the checklist passes. For a cautious rollout, begin with a limited audience coordinated with Slicker, review the first scheduled and sent emails, and expand after the content and recovery results look correct.

## Phase 5: Monitor Email Operations

### Overview

The [Emails overview](https://app.slickerhq.com/dunning) shows:

* **Scheduled emails** and the number of unique customers represented.
* **Invoices recovered** and the recovered amount.
* **Total emails sent**, including the last 30 days.
* **Email open rate** and **email click rate** when engagement reporting is available.

The tables below the cards provide quick access to recent scheduled and sent messages.

### Scheduled and Sent Emails

Use **Scheduled Emails** to inspect pending messages before they run. Filter or sort by recipient, scheduled time, amount, invoice, or scenario, then open a preview to verify the rendered message.

Use **Sent Emails** to inspect completed sends, the executed time, scenario and invoice context, and whether the associated invoice was recovered. Provider acceptance means the provider accepted Slicker's send request; it does not guarantee inbox placement or prove that the recipient read the email.

### Analytics

Use the date picker on [Emails → Analytics](https://app.slickerhq.com/dunning/analytics) to review:

* Sent emails by scenario and over time.
* Recovery rate by scenario.
* Scheduled volume for the next seven days.
* Sends by hour and day of week in UTC.
* Monthly recovered-invoice count and recovered amount.
* Open and click rates over time, clicks by link type, open rate by scenario, and click-to-open rate by template when tracking data is available.

Review scenario results over a meaningful sample rather than reacting to a few sends. Compare recovery rate alongside volume: a narrowly targeted scenario may have a high rate but affect fewer invoices.

## Dynamic Billing-Page URLs

A static button URL works when every recipient can start from the same login or billing-portal page. Use a dynamic billing-page destination when each customer needs a different CTA, such as a signed payment-update URL stored on their Customer.io profile.

Slicker supports customer-specific URLs stored in a **Customer.io attribute**. At send time, Slicker looks up the recipient by email, reads the configured attribute, adds any configured query parameters, and validates the result against your destination-host allowlist. The email contains an expiring, opaque Slicker redirect instead of exposing the resolved URL in email-processing history or tracking data.

To configure a destination:

1. In Customer.io, enable email identifiers and populate an attribute containing an absolute HTTPS billing-page URL for each customer. Create a dedicated Customer.io App API key for Slicker.
2. Open [Emails → Styling & configuration](https://app.slickerhq.com/dunning/styling), edit an email configuration, and expand **Call to Action Button**.
3. Keep a valid static **Button URL** for disabled and shadow operation. Under **Dynamic billing-page destination**, select **Manage** and create a **Customer.io attribute** destination.
4. Choose the Customer.io region, enter the attribute name and App API key, and add any query parameters as one `key=value` pair per line.
5. Add every permitted billing-page hostname. A hostname must match this allowlist before Slicker uses the resolved URL; prefix an entry with `.` to allow its subdomains.
6. Choose whether a failed resolution should fail the email or use an explicitly configured static fallback. Set an appropriate link lifetime, then save the destination in **Shadow** mode.
7. Run the end-to-end connection test, then allow representative recovery emails to run in Shadow mode. Shadow mode validates live lookups while recipients continue to receive the static URL. A manual test does not count as live shadow evidence.
8. After the saved configuration has passed both the connection test and a live shadow resolution, change it to **Active** and save the email configuration with the destination selected.

Changing provider settings starts a new validation cycle. Move the destination back through Shadow mode before reactivating it. To stop using customer-specific links, select the static button URL or set the destination to Disabled.

## Email-Outcome Webhooks

Use an email-outcome webhook when your system should react after Slicker attempts a recovery email—for example, to send an SMS through your existing provider. Slicker sends the event; your system remains responsible for phone-number storage, consent, quiet hours, message delivery, and recipient deduplication.

Configure the webhook in [Emails → Webhooks](https://app.slickerhq.com/dunning/webhooks):

1. Enter one public HTTPS endpoint and a Bearer token. Local, private-network, and redirecting destinations are rejected. The token is write-only and is sent in the `Authorization: Bearer …` header.
2. Choose whether to emit after every email-provider attempt or only after the provider accepts the email. Provider acceptance is not inbox delivery, and a later bounce does not emit another event.
3. Choose the payload copy source. Slicker can include a custom message for another channel, include the rendered subject and body of the selected recovery email, or send only structured event fields so your endpoint can compose its own message.
4. Set the default for all scenarios, then add per-scenario enablement or message overrides where needed. New scenarios inherit the default.
5. Save the configuration, select a scenario, and send a test event. Test deliveries are marked with `test: true`, appear in delivery history, and are not retried.
6. Enable the endpoint after your receiver validates the sample payload and returns a `2xx` response.

Production events use the `dunning_email_attempted` type and include a stable event ID plus structured scenario, customer, invoice, and email-attempt data. Depending on the copy source, `data.message` or `data.emailCopy` is also present:

```json theme={null}
{
  "id": "whdr_01...",
  "type": "dunning_email_attempted",
  "created": "2026-09-24T10:30:00Z",
  "data": {
    "schemaVersion": 1,
    "test": false,
    "dunningActionId": "dact_01...",
    "scenario": { "id": "dsc_01...", "name": "Card expired" },
    "customer": { "id": "cus_123", "email": "customer@example.com" },
    "invoice": { "id": "inv_123", "amountMinorUnits": 1299, "currency": "USD" },
    "email": {
      "templateId": "etpl_01...",
      "result": "accepted",
      "attemptedAt": "2026-09-24T10:29:58Z"
    },
    "message": "Please update your payment method."
  }
}
```

Webhook delivery is at least once. Slicker sends the same stable event ID in the body and the `Idempotency-Key` header. Persist that value before triggering SMS or another customer-facing action. Failed production deliveries are retried with exponential backoff, up to five total attempts, without delaying or changing the original email result.

Delivery history shows the payload, attempt count, response status, and any truncated error. It contains customer data and should be available only to authorized users.

## Ongoing Review

After launch, establish a regular review cadence:

* Check pending volume for unexpected spikes or gaps.
* Investigate failed sends and invalid customer data.
* Compare recovery rate and recovered amount by scenario.
* Compare copy variants only after they have meaningful volume.
* Treat open and click rates as directional and prioritize paid-invoice outcomes.
* Re-test sender identity, CTA destinations, and webhooks after configuration changes.
* Update scenarios and templates as products, billing flows, or support policies change.

For platform-wide recovery reporting, continue with [Analytics & Reporting](/essentials/analytics).


# Dealing with Expired Cards
Source: https://docs.slickerhq.com/guides/expired_cards

Learn how to detect, understand, and address the challenges of expired payment methods

### How to Detect Expired Cards

Expired cards can sneak up on any subscription business, but identifying them early is key to keeping your revenue flowing. Here are some ways to detect them:

* **General Approach**: Review failed payments for error codes indicating card expiration. Most payment processors include these details in their logs.
* **In Slicker**: Use the **Payments Analytics** feature to identify transactions failing due to expired cards. Learn more about this tool on the [Analytics & Reporting](/essentials/analytics) page.

### Implications of Expired Cards

Expired cards often lead to payment failures, which can result in:

* **Customer Churn**: In most cases, manual intervention from the customer is required to update their card details. Without this, they may unintentionally churn.
* **Revenue Impact**: Every failed transaction is a potential hit to your bottom line.

### What Can Be Done?

**Reactive Solutions**

* **Retries**: Unfortunately, retries won’t help with expired cards unless the user updates their billing details.
* **Account Updater Services**: Some payment processors, like Stripe, offer tools to automatically update card details when available. These tools are helpful but don’t cover every scenario - for example, if a customer changes bank, or their new card is not linked to their account.
* **Dunning Emails**: Sending follow-up emails after a failed payment can help recover some payments, but this approach only works after the failure has already occurred and is not a guaranteed success.

**Proactive Solutions**

A proactive approach can reduce the impact of expired cards. By identifying cards that are about to expire and notifying customers in advance, you can prevent failed payments before they happen.
Proactive communication not only reduces failed payments but also enhances the customer experience by ensuring a seamless subscription process.

In Slicker you can use the [Expiring Cards tab](https://app.slickerhq.com/revenue-recovery?tab=expiring-cards) on the **Revenue Recovery** page to see which customers’ cards are nearing expiration. Combine this with insights from the [Analytics & Reporting](/essentials/analytics) page to notify customers ahead of time.

***

Slicker helps you reduce involuntary churn and dealing with expired cards is one of the ways we do this.


# High Number of Insufficient Funds Errors
Source: https://docs.slickerhq.com/guides/insufficient_funds

Learn how to handle and recover from insufficient funds payment errors

### How to Detect Insufficient Funds Errors

Detecting insufficient funds errors follows a similar process to identifying other payment issues:

* **General Approach**: Look for error codes related to insufficient funds in your payment processor logs or your internal BI platform.
* **In Slicker**: Use the **Payments Analytics** feature to identify patterns and monitor transactions failing due to insufficient funds. Learn more on the [Analytics & Reporting](/essentials/analytics) page.

### What Is the Impact?

Insufficient funds errors are classified as "soft errors," meaning they can often be recovered eventually. However, there are risks:

* **Revenue at Risk**: Repeated failures may lead to involuntary churn or delay in cash flow.
* **Churn Impact**: Failed payments that aren’t recovered result in lost revenue and potentially lost customers.

Understanding and addressing these errors quickly can minimize their impact on your business.

### What Can Be Done?

**Dunning Emails**

Sending follow-up emails to notify customers about failed payments can prompt them to resolve the issue. However, this approach depends on the customer taking action and is not always reliable.

**Retries**

Retries can be highly effective for insufficient funds errors, provided they are timed correctly. Success often depends on factors such as:

* **Country**: In the United Kingdom, for example, consumer debit cards might succeed when retried on the last working day of the month (typical pay day).
* **Amount**: Larger amounts may require a different retry cadence compared to smaller transactions.
* **Card Type**: Prepaid, debit, and credit cards may have varying retry success windows.
* **Customer Behavior**: Past payment patterns can inform the optimal retry schedule.

### How Slicker Helps

At Slicker, we ingest payment data, analyze customer behavior, and consider factors like country-specific trends, card types, and transaction history. Using this data, we make intelligent retry decisions that maximize the likelihood of recovery and help you recover more revenue efficiently.

By automating the process and leveraging smart algorithms, Slicker ensures you stay ahead of insufficient funds challenges.


# High Number of Not Sent to Network Errors
Source: https://docs.slickerhq.com/guides/not_sent_to_network

Understand why payments are blocked before reaching the network and how to manage them effectively

### Why Payments Aren’t Sent to the Network

"Not Sent to Network" errors occur when a payment is blocked before it even reaches the card network or issuer for processing. These blocks are typically initiated by payment processors or banks due to potential fraud detection or transaction anomalies. While these mechanisms are essential for preventing fraudulent transactions, they can sometimes unintentionally block legitimate payments.

#### Typical Payment Flow

The diagram below illustrates the usual flow of a payment and where the "Not Sent to Network" issue occurs:

```mermaid theme={null}
flowchart LR
    BillingProvider[Billing Provider] -->|Payment Info| PaymentProcessor[Payment Processor]
    PaymentProcessor -->|Fraud Checks| Network[Card Network]
    Network --> Issuer[Issuer Bank]
    PaymentProcessor -.->|Blocked| Blocked[Payment Not Sent to Network]
```

1. The **Customer** submits their payment details.
2. The **Payment Processor** validates the payment and performs fraud checks.
3. If approved, the payment is sent to the **Card Network** (e.g., Visa, MasterCard).
4. The **Issuer Bank** authorizes or declines the payment.

If a payment is flagged during fraud checks by the **Payment Processor**, it is **Not Sent to the Network**, resulting in a block.

### Common Reasons for "Not Sent to Network" Errors

Here are some common reasons why payments might be blocked at the processor stage:

* **Fraud Detection Mechanisms**: Transactions flagged due to unusual patterns or mismatched details.
* **Issuer Bank Policies**: Blocks based on spending limits, regional restrictions, or account activity.
* **Unusual Transaction Amounts**: Amounts outside the customer’s typical range.
* **Repeated Payment Attempts**: Multiple retries in a short timeframe.
* **Behavioral Changes**: Sudden shifts in the customer’s purchasing habits.
* **Incomplete or Incorrect Data**: Errors like invalid CVV or expired card details.

### The Impact of False Positives

False positives can disrupt legitimate payments, causing:

* Frustration for customers.
* Increased involuntary churn.
* Revenue loss due to unnecessary payment blocks.

### How Slicker Can Help

Slicker analyzes flagged payments and selectively approves legitimate ones. It evaluates risk scores, transaction amounts, and customer history to minimize disruptions and ensure legitimate payments are processed.

***

By understanding the payment flow and addressing false positives proactively, you can improve your approval rates and reduce churn.


# Integration setup
Source: https://docs.slickerhq.com/integration_setup



Integrations are how we gain insights into lost revenue and automate the recovery process.
Adding an integration takes less than 5 minutes, requires no code, and looks something like this:

<Steps>
  <Step title="Generate credentials" icon="key">
    Generate API credentials with the appropriate permissions in your provider.
  </Step>

  <Step title="Create integration in Slicker" icon="vault">
    Create an integration in Slicker that uses these credentials.
  </Step>

  <Step title="Sit back and let the revenue flow in" icon="rocket">
    Slicker will start syncing data, providing insights, and recovering revenue. All without you lifting a finger.
  </Step>
</Steps>

For a more detailed guide for each provider, check out the individual integration pages below.

### Billing & subscription providers

The bread and butter of any subscription business. We integrate with the best billing and subscription providers to manage your revenue and reduce churn.

<CardGroup>
  <Card
    title="Chargebee"
    icon={
<svg id="logosandtypes_com" data-name="logosandtypes com"  width="36" height="36" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 150 150">
    <path class="cls-2" d="M0,0H150V150H0V0Z" fill="none"/>
    <path class="cls-1" d="M54.43,76.09l80.25-19.32V14.77h-41.61l-38.64,61.32Z" fill="#f30"/>
    <path class="cls-1" d="M14.65,75.35c0,5.02,.61,9.9,1.75,14.57l38.02-13.84-38.33-13.96c-.93,4.25-1.44,8.68-1.44,13.21h0Z" fill="#f30"/>
    <path class="cls-1" d="M28.79,36.3l25.62,39.79,11.81-60.72c-14.96,2.12-28.14,9.81-37.43,20.93Z" fill="#f30"/>
    <path class="cls-1" d="M54.43,76.09l80.25,19.31v42h-41.61l-38.64-61.31Z" fill="#f30"/>
    <path class="cls-1" d="M28.8,115.86l25.62-39.79,11.8,60.7c-14.96-2.12-28.14-9.81-37.43-20.93h.01Z" fill="#f30"/>
</svg>
}
    href="/integrations/billing/chargebee"
  >
    Automate revenue recovery for your Chargebee subscriptions.
  </Card>

  <Card
    title="Recharge"
    icon={<svg xmlns="http://www.w3.org/2000/svg" width="126" height="25" viewBox="0 0 1264 251" fill="none">
  <g clip-path="url(https://mintlify.s3.us-west-1.amazonaws.com/slicker/#clip0_20_9)">
      <path d="M124.915 251C149.628 251.006 173.788 243.65 194.34 229.862C214.891 216.074 230.911 196.473 240.373 173.539C249.835 150.604 252.313 125.366 247.496 101.016C242.678 76.6666 230.781 54.2989 213.308 36.742C195.835 19.1851 173.572 7.22771 149.334 2.38208C125.096 -2.46355 99.9716 0.0202282 77.1388 9.51929C54.306 19.0184 34.7901 35.106 21.0595 55.7477C7.32878 76.3894 7.90368e-07 100.658 0 125.484C-1.05962e-06 158.767 13.1596 190.688 36.5848 214.226C60.0099 237.764 91.7824 250.991 124.915 251Z" fill="#3901F1"/>
      <path d="M136.86 175.195H74.9236C74.7368 175.241 74.5417 175.241 74.3548 175.195C74.1874 175.107 74.0374 174.989 73.9124 174.846C73.7858 174.702 73.6987 174.527 73.6596 174.338C73.6128 174.151 73.6128 173.954 73.6596 173.767L85.7308 111.485C85.785 111.261 85.8935 111.054 86.0468 110.882C86.2089 110.715 86.4189 110.604 86.6472 110.564C86.8687 110.509 87.1016 110.522 87.3157 110.601C87.5299 110.68 87.7153 110.822 87.848 111.009L137.808 173.195C137.932 173.384 137.998 173.604 137.997 173.83C138.061 174.037 138.061 174.258 137.997 174.465C137.907 174.668 137.765 174.843 137.586 174.973C137.379 175.134 137.121 175.213 136.86 175.195Z" fill="#FFFBF6"/>
      <path d="M73.786 81.1695H135.69C135.877 81.1224 136.072 81.1224 136.259 81.1695C136.447 81.2378 136.612 81.359 136.733 81.5187C136.842 81.6743 136.927 81.8455 136.986 82.0266C137.033 82.2141 137.033 82.4104 136.986 82.598L125.01 145.134C124.944 145.351 124.824 145.547 124.662 145.705C124.512 145.871 124.312 145.983 124.093 146.023C123.879 146.103 123.644 146.103 123.43 146.023C123.206 145.957 123.007 145.824 122.861 145.642L72.68 83.1059C72.6289 82.9189 72.6289 82.7215 72.68 82.5345C72.6167 82.306 72.6167 82.0645 72.68 81.8361C72.8038 81.6376 72.9648 81.4651 73.154 81.3282C73.3478 81.2221 73.5653 81.1674 73.786 81.1695Z" fill="#FFFBF6"/>
      <path d="M143.18 81.1695C142.91 81.1666 142.649 81.269 142.453 81.4552C142.226 81.6121 142.067 81.8508 142.01 82.1218C141.375 87.3054 141.834 92.5654 143.359 97.5584C144.884 102.551 147.44 107.165 150.861 111.098C154.281 115.032 158.489 118.196 163.21 120.385C167.93 122.574 173.057 123.738 178.256 123.802H179.551C179.834 123.8 180.11 123.711 180.341 123.548C180.549 123.37 180.684 123.121 180.72 122.849L189.063 82.5345C189.093 82.3559 189.093 82.1734 189.063 81.9948C188.998 81.8291 188.902 81.678 188.778 81.5504C188.661 81.4072 188.509 81.2976 188.336 81.233C188.17 81.19 187.996 81.19 187.83 81.233L143.18 81.1695Z" fill="#FFFBF6"/>
  </g>
  <defs>
      <clipPath id="clip0_20_9">
          <rect width="1264" height="251" fill="white"/>
      </clipPath>
  </defs>
</svg>}
    href="/integrations/billing/recharge"
  >
    >

    Automate revenue recovery for your Shopify or BigCommerce subscriptions managed in Recharge.
  </Card>

  <Card
    title="Recurly"
    icon={
<svg id="logosandtypes_com" xmlns="http://www.w3.org/2000/svg" width="36" height="36" viewBox="0 0 150 150.2"><path d="M0 .2h150v150H0V.2z" fill="none"/><g><path d="M74.4 12.5c-34 0-61.6 27.6-61.6 61.6s27.6 61.6 61.6 61.6S136 108.1 136 74.1s-27.6-61.6-61.6-61.6zm13.4 96.9L75.3 89.3c-5.2-7.7-8.2-8.8-11.2-8.8v28.9h-14V71h22.2c10 0 14.2-6 14.2-13.9 0-5.4-3.1-11.9-11.9-11.9-10.4 0-10.5 8.3-10.5 8.3h8l-15 11.9-14-11.9h7c1.8-11.5 10-18.2 24.1-18.2 16 0 26.1 7 26.1 21.8 0 12-8.7 19.4-17.5 21.6 1.7 1.3 4.3 4.8 7.7 10.1l12.8 20.6H87.8z" fill="#713080"/></g></svg>
}
    href="/integrations/billing/recurly"
  >
    Automate revenue recovery for your Recurly subscriptions.
  </Card>

  <Card title="Stripe Billing" icon={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32" width="26" height="26" fill="#6772e5"><path d="M111.328 15.602c0-4.97-2.415-8.9-7.013-8.9s-7.423 3.924-7.423 8.863c0 5.85 3.32 8.8 8.036 8.8 2.318 0 4.06-.528 5.377-1.26V19.22a10.246 10.246 0 0 1-4.764 1.075c-1.9 0-3.556-.67-3.774-2.943h9.497a39.64 39.64 0 0 0 .063-1.748zm-9.606-1.835c0-2.186 1.35-3.1 2.56-3.1s2.454.906 2.454 3.1zM89.4 6.712a5.434 5.434 0 0 0-3.801 1.509l-.254-1.208h-4.27v22.64l4.85-1.032v-5.488a5.434 5.434 0 0 0 3.444 1.265c3.472 0 6.64-2.792 6.64-8.957.003-5.66-3.206-8.73-6.614-8.73zM88.23 20.1a2.898 2.898 0 0 1-2.288-.906l-.03-7.2a2.928 2.928 0 0 1 2.315-.96c1.775 0 2.998 2 2.998 4.528.003 2.593-1.198 4.546-2.995 4.546zM79.25.57l-4.87 1.035v3.95l4.87-1.032z" fill-rule="evenodd"/><path d="M74.38 7.035h4.87V24.04h-4.87z"/><path d="M69.164 8.47l-.302-1.434h-4.196V24.04h4.848V12.5c1.147-1.5 3.082-1.208 3.698-1.017V7.038c-.646-.232-2.913-.658-4.048 1.43zm-9.73-5.646L54.698 3.83l-.02 15.562c0 2.87 2.158 4.993 5.038 4.993 1.585 0 2.756-.302 3.405-.643v-3.95c-.622.248-3.683 1.138-3.683-1.72v-6.9h3.683V7.035h-3.683zM46.3 11.97c0-.758.63-1.05 1.648-1.05a10.868 10.868 0 0 1 4.83 1.25V7.6a12.815 12.815 0 0 0-4.83-.888c-3.924 0-6.557 2.056-6.557 5.488 0 5.37 7.375 4.498 7.375 6.813 0 .906-.78 1.186-1.863 1.186-1.606 0-3.68-.664-5.307-1.55v4.63a13.461 13.461 0 0 0 5.307 1.117c4.033 0 6.813-1.992 6.813-5.485 0-5.796-7.417-4.76-7.417-6.943zM13.88 9.515c0-1.37 1.14-1.9 2.982-1.9A19.661 19.661 0 0 1 25.6 9.876v-8.27A23.184 23.184 0 0 0 16.862.001C9.762.001 5 3.72 5 9.93c0 9.716 13.342 8.138 13.342 12.326 0 1.638-1.4 2.146-3.37 2.146-2.905 0-6.657-1.202-9.6-2.802v8.378A24.353 24.353 0 0 0 14.973 32C22.27 32 27.3 28.395 27.3 22.077c0-10.486-13.42-8.613-13.42-12.56z" fill-rule="evenodd"/></svg>} href="/integrations/billing/stripe">
    Automate revenue recovery for your subscriptions managed by Stripe Billing.
  </Card>

  <Card
    title="Zuora"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="44" height="36" viewBox="0 0 542 468" fill="none"><path d="M75 234C75 105.318 179.318 1 308 0.99999C436.682 0.999979 541 105.318 541 234C541 362.682 436.682 467 308 467C179.318 467 75 362.682 75 234Z" stroke="#00D2B9" stroke-width="2"></path><path d="M234 -1.00607e-05C104.765 1.2374e-06 -1.2374e-06 104.765 1.00607e-05 234C2.13587e-05 363.235 104.765 468 234 468C363.235 468 468 363.235 468 234C468 104.765 363.235 -2.13587e-05 234 -1.00607e-05Z" fill="#103426"></path><path d="M328.269 275.335C322.068 269.229 313.768 265.723 304.967 265.723H259.555L332.538 207.075C337.284 203.33 339.193 196.986 337.046 191.357C334.923 185.728 329.676 181.984 323.499 181.984H271.672L297.359 161.091C302.105 157.108 304.013 151.002 301.866 145.373C299.72 139.745 294.497 136 288.319 136H173.24C164.463 136 156.139 139.506 149.962 145.612C143.522 151.956 140.207 160.161 140.207 168.842C140.207 177.524 143.522 185.728 149.724 191.834C156.139 197.916 164.463 201.446 173.24 201.446H308.282L228.407 265.723H169.687L209.159 233.12C213.19 229.59 213.905 223.484 210.328 219.262C206.774 215.279 200.597 214.588 196.304 218.094L145.192 260.095C140.446 264.078 138.776 270.183 140.923 275.812C143.069 281.441 148.293 285.185 154.47 285.185H203.912L177.533 306.532C172.787 310.3 170.879 316.62 173.002 322.249C175.148 327.878 180.372 331.646 186.573 331.646H304.967C313.768 331.646 322.068 328.355 328.269 322.249C334.685 315.929 338 307.7 338 299.042V298.565C338 289.645 334.446 281.441 328.269 275.335ZM240.523 181.745H173.24C169.687 181.745 166.347 180.577 163.748 177.977C161.363 175.401 159.932 172.11 159.932 168.604C159.932 165.098 161.124 161.806 163.748 159.23C166.347 156.869 169.687 155.462 173.24 155.462H273.103L240.523 181.745ZM318.276 299.042C318.276 302.549 317.083 305.84 314.459 308.416C311.86 310.753 308.521 312.16 304.967 312.16H202.028L235.299 285.424H304.967C308.521 285.424 311.86 286.592 314.459 289.168C316.845 291.768 318.276 295.036 318.276 298.565V299.042Z" fill="#00D2B9"></path></svg>
}
    href="/integrations/billing/zuora"
  >
    Automate revenue recovery for your Zuora subscriptions.
  </Card>

  <Card
    title="Custom"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 64 64">
<rect width="64" height="64" rx="12" fill="#7FF3D6" />
<path d="M40.236 42.982c-2.546 2.318-5.74 3.477-9.582 3.477-4.197 0-7.623-1.36-10.277-4.08-2.654-2.72-3.982-6.23-3.982-10.529 0-4.3 1.328-7.81 3.982-10.53 2.654-2.72 6.08-4.08 10.277-4.08 3.741 0 6.87 1.091 9.387 3.273l-2.85 4.284c-1.907-1.664-4.087-2.495-6.537-2.495-2.644 0-4.77.827-6.378 2.482-1.608 1.655-2.412 3.826-2.412 6.512 0 2.687.804 4.857 2.412 6.512 1.608 1.655 3.734 2.483 6.378 2.483 2.54 0 4.79-.876 6.754-2.63l2.829 5.32z" fill="#000000"/>
</svg>
}
    href="/integrations/billing/custom"
  >
    Integrate with a custom in-house billing system.
  </Card>
</CardGroup>

### Payment providers

We integrate with payment providers to gain more accurate insights into why payments fail and how to recover them.

<CardGroup>
  <Card
    title="Adyen"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 64 64"><path d="M51.128 0H1.073v16.1h32.894c2.145 0 3.575 1.788 3.575 3.575V47.9h-7.15c-2.145 0-3.575-1.788-3.575-3.575v-20.38H12.872A12.83 12.83 0 0 0 0 36.827V51.13C0 58.28 5.72 64 12.872 64H64V12.872C64 5.72 58.28 0 51.128 0z" fill="#35b454"/></svg>
    }
    href="/integrations/payments/adyen"
  >
    Sync Adyen payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Authorize.net"
    icon={
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 240 240" width="32" height="32">
<path d="M0 0 C79.2 0 158.4 0 240 0 C240 79.2 240 158.4 240 240 C160.8 240 81.6 240 0 240 C0 160.8 0 81.6 0 0 Z " fill="#202A43" transform="translate(0,0)"/>
<path d="M0 0 C1.48177982 1.1153469 2.93947889 2.26321329 4.375 3.4375 C5.35984375 4.20449219 6.3446875 4.97148438 7.359375 5.76171875 C17.23203514 14.04307223 24.36420272 28.10387524 25.61450195 40.88598633 C26.61313627 60.48626909 23.35762382 75.36187615 10.46875 90.70703125 C0.0074045 101.91867817 -14.78327763 108.73934857 -30.0703125 109.640625 C-46.654757 109.85189181 -62.60631585 105.12656745 -74.859375 93.40625 C-87.86415129 78.905349 -93.64192134 62.9815569 -92.97265625 43.55078125 C-91.95006174 27.76470762 -83.24535025 13.74368649 -71.625 3.4375 C-50.77883871 -13.38421108 -22.26602411 -15.04193629 0 0 Z " fill="#3773FB" transform="translate(132.625,55.5625)"/>
<path d="M0 0 C5.6567352 3.34361286 10.12160617 8.08345779 12.953125 14.00390625 C14.54594862 21.96802433 13.76674728 28.0837809 9.578125 35.12890625 C5.27241522 40.51104347 0.27901225 43.62928647 -6.546875 44.55078125 C-13.82853201 44.85418363 -18.94978221 44.0952843 -24.421875 39.12890625 C-29.79900802 33.73798571 -31.72832919 29.49498031 -31.859375 21.87890625 C-31.84077377 15.43125483 -31.05663101 10.80801399 -26.421875 6.12890625 C-18.86010642 -0.55016561 -10.02486548 -3.60571774 0 0 Z " fill="#FCC101" transform="translate(186.421875,149.87109375)"/>
</svg>
}
    href="/integrations/payments/authorize"
  >
    Sync Authorize.net payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Braintree"
    icon={
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
 viewBox="0 0 1000 1000" fill="#3f3d43" xml:space="preserve">
<path d="M60,990.5V847h119.6V148.4H60V4.9h473.5c215.3,0,349.2,95.7,349.2,267.9c0,109.9-67,177-153.1,210.5
C853.9,516.7,940,598.1,940,712.9c0.1,181.8-143.4,282.2-382.7,282.2H60V990.5z M342.2,148.5v267.9h177
c133.9,0,200.9-47.8,200.9-133.9c0-90.9-71.8-133.9-205.7-133.9L342.2,148.5z M342.2,847h200.9c157.9,0,234.4-47.8,234.4-143.5
S696.2,560,533.5,560H342.2L342.2,847z"/>
</svg>
}
    href="/integrations/payments/braintree"
  >
    Sync Braintree payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Cybersource"
    icon={<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 240.1 276.2" xml:space="preserve">
<g id="Layer_2_1_">
<g id="Layer_1-2">
<path d="M10.4,191c-3.3-8,0.5-17.2,8.5-20.6c8-3.3,17.2,0.5,20.6,8.5c3.3,8-0.5,17.2-8.5,20.6c-1.9,0.8-4,1.2-6,1.2
		C18.6,200.7,12.9,196.9,10.4,191" fill="#FFC300">
</path>
<path d="M170.1,257.3c-3.3-8,0.5-17.2,8.6-20.5c8-3.3,17.2,0.5,20.5,8.6c3.3,8-0.5,17.2-8.6,20.5
		c-1.9,0.8-3.9,1.2-6,1.2C178.3,267,172.5,263.2,170.1,257.3" fill="#202A44">
</path>
<path d="M137.9,276.2c-36.6,0.1-71.7-14.4-97.5-40.4c-6.1-6.1-6.1-16.1,0-22.2s16.1-6.1,22.2,0
		c19.9,20,47,31.3,75.3,31.2c8.7,0,15.7,7,15.7,15.7S146.6,276.2,137.9,276.2" fill="#202A44">
</path>
<path d="M213.2,235.8c-6.2-6.1-6.2-16.1,0-22.3c6.1-6.2,16.1-6.2,22.3,0s6.2,16.1,0,22.3c-3,3-7,4.6-11.2,4.6
		C220.2,240.4,216.2,238.8,213.2,235.8" fill="#202A44">
</path>
<path d="M10.4,85.2c-3.3,8,0.5,17.2,8.5,20.6c8,3.3,17.2-0.5,20.6-8.5c3.3-8-0.5-17.2-8.5-20.6c-1.9-0.8-4-1.2-6-1.2
		C18.6,75.5,12.8,79.4,10.4,85.2" fill="#FFC300">
</path>
<path d="M170.1,19c-3.3,8,0.5,17.2,8.6,20.5c8,3.3,17.2-0.5,20.5-8.6c3.3-8-0.5-17.2-8.6-20.5c-1.9-0.8-3.9-1.2-6-1.2
		C178.3,9.2,172.5,13.1,170.1,19" fill="#3874FD">
</path>
<path d="M137.9,0c-36.6-0.1-71.7,14.4-97.5,40.4c-6.1,6.2-6,16.1,0.2,22.2c6.1,6,16,6,22.1,0
		c19.9-20,47-31.3,75.3-31.2c8.7,0,15.7-7,15.7-15.7C153.7,7,146.6,0,137.9,0C138,0,138,0,137.9,0" fill="#3874FD">
</path>
<path d="M213.2,40.4c-6.2,6.1-6.2,16.1,0,22.3c6.1,6.2,16.1,6.2,22.3,0c6.2-6.1,6.2-16.1,0-22.3c-3-3-7-4.6-11.2-4.6
		C220.2,35.8,216.2,37.5,213.2,40.4" fill="#3874FD">
</path>
<path d="M0,138.1L0,138.1z M15.7,122.4C7,122.4,0,129.5,0,138.2c0,8.7,7.1,15.7,15.8,15.7c8.7,0,15.7-7.1,15.7-15.8
		C31.4,129.4,24.4,122.4,15.7,122.4C15.7,122.4,15.7,122.4,15.7,122.4z" fill="#FFC300">
</path>
</g>
</g>
</svg>}
    href="/integrations/payments/cybersource"
  >
    Sync Cybersource payments data t oget more accurate insights and recover revenue.
  </Card>

  <Card title="Stripe" icon={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32" width="26" height="26" fill="#6772e5"><path d="M111.328 15.602c0-4.97-2.415-8.9-7.013-8.9s-7.423 3.924-7.423 8.863c0 5.85 3.32 8.8 8.036 8.8 2.318 0 4.06-.528 5.377-1.26V19.22a10.246 10.246 0 0 1-4.764 1.075c-1.9 0-3.556-.67-3.774-2.943h9.497a39.64 39.64 0 0 0 .063-1.748zm-9.606-1.835c0-2.186 1.35-3.1 2.56-3.1s2.454.906 2.454 3.1zM89.4 6.712a5.434 5.434 0 0 0-3.801 1.509l-.254-1.208h-4.27v22.64l4.85-1.032v-5.488a5.434 5.434 0 0 0 3.444 1.265c3.472 0 6.64-2.792 6.64-8.957.003-5.66-3.206-8.73-6.614-8.73zM88.23 20.1a2.898 2.898 0 0 1-2.288-.906l-.03-7.2a2.928 2.928 0 0 1 2.315-.96c1.775 0 2.998 2 2.998 4.528.003 2.593-1.198 4.546-2.995 4.546zM79.25.57l-4.87 1.035v3.95l4.87-1.032z" fill-rule="evenodd"/><path d="M74.38 7.035h4.87V24.04h-4.87z"/><path d="M69.164 8.47l-.302-1.434h-4.196V24.04h4.848V12.5c1.147-1.5 3.082-1.208 3.698-1.017V7.038c-.646-.232-2.913-.658-4.048 1.43zm-9.73-5.646L54.698 3.83l-.02 15.562c0 2.87 2.158 4.993 5.038 4.993 1.585 0 2.756-.302 3.405-.643v-3.95c-.622.248-3.683 1.138-3.683-1.72v-6.9h3.683V7.035h-3.683zM46.3 11.97c0-.758.63-1.05 1.648-1.05a10.868 10.868 0 0 1 4.83 1.25V7.6a12.815 12.815 0 0 0-4.83-.888c-3.924 0-6.557 2.056-6.557 5.488 0 5.37 7.375 4.498 7.375 6.813 0 .906-.78 1.186-1.863 1.186-1.606 0-3.68-.664-5.307-1.55v4.63a13.461 13.461 0 0 0 5.307 1.117c4.033 0 6.813-1.992 6.813-5.485 0-5.796-7.417-4.76-7.417-6.943zM13.88 9.515c0-1.37 1.14-1.9 2.982-1.9A19.661 19.661 0 0 1 25.6 9.876v-8.27A23.184 23.184 0 0 0 16.862.001C9.762.001 5 3.72 5 9.93c0 9.716 13.342 8.138 13.342 12.326 0 1.638-1.4 2.146-3.37 2.146-2.905 0-6.657-1.202-9.6-2.802v8.378A24.353 24.353 0 0 0 14.973 32C22.27 32 27.3 28.395 27.3 22.077c0-10.486-13.42-8.613-13.42-12.56z" fill-rule="evenodd"/></svg>} href="/integrations/payments/stripe">
    Sync Stripe payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Worldpay"
    icon={<svg xmlns="http://www.w3.org/2000/svg" height="80" width="120" id="svg8195" version="1.1"
 viewBox="0 0 48 32">
<g transform="translate(79.6546 -150.1857)" id="layer1">
    <g transform="translate(-79.6477 150.1857) scale(.17764)" id="g8241" stroke-width="1.4895">
        <path class="st1"
              d="M60.5 63.1c-.6.9-1.3 1.8-2.1 2.7-1.7 1.9-3.7 3.7-5.9 5.2-2.8 1.9-5.7 3.4-8.7 4.5-2.6.9-4.9 1.4-6.9 1.5h-.7c-1 0-1.7-.1-2.1-.4l-.2-.1-.2-.2v-.1c0-.1 0-.3.1-.5.2-.5.5-.9.9-1.4.1-.1.3-.3.4-.5 1.5-.4 3-.9 4.7-1.4 1.5.3 3.1.4 4.5.3 1.8-.2 3.5-.7 5-1.5 1.8-1 3.4-2.3 4.7-3.9.8-1.1 1.5-2.2 2-3.5 2.7-2.1 5-4.3 6.8-6.5l.9-1.2c-.7 2.4-1.7 4.8-3.2 7m-10.3 4.5c.6-.3 1.1-.7 1.7-1-.8 1-1.8 1.9-2.8 2.6-1.4.9-2.9 1.6-4.4 1.9-.7.1-1.3.2-2 .3 2.5-1.1 5.1-2.4 7.5-3.8m18.3-25.1c0-2.9-.7-5.7-2.1-8.3-1.2-2.3-3-4.5-5.2-6.5-.5-2.7-1.9-5.2-4-7.5-1.7-1.8-3.8-3.4-6.4-4.8-2-1.1-4.2-2-6.5-2.7-1.9-.6-3.8-.9-5.6-1.1-1.7-.2-3.1-.1-4.4.1-1.3.3-2.5.7-3.6 1.3l-.2.1c-1.5-.2-3-.2-4.4-.1h-.4c-1.4.1-4.3.5-4.1 1.9 0 0 0 .8 1.8 1.4l2.5-1.5c-.2 0-.4-.1-.6-.1.8-.1 1.6-.2 2.2-.2h.5c-.2.1-.3.2-.5.3l-.8.5c-1.5.9-2 1.3-3.6 2.2-1 .6-1.9 1.2-2.9 1.7-1.9 1-3.8 2-5.8 3-1.6.7-3.2 1.5-5.3 2.4l-.2.1c-.5.2-1 .4-1.4.6h-.1c-.5.2-1.1.5-1.4 1.1l-.1.4v.4c0 .1.1.2.1.2l.3.3.3.2h.1c.3.1.7.1 1.1.1h1.8c.7 0 1.4-.1 2-.1 3.3-.1 6.3-.1 9.2 0 2.8.1 5.6.4 8.4.7l4.2.6c.9-.8 1.6-1.4 2.1-2-2.9-.6-5.8-1-8.6-1.3-2.9-.3-6-.5-9.1-.5h-1.1c-1.5 0-3.1 0-4.6.1 1.5-.7 2.8-1.4 4.1-2 1.9-1 3.8-2.1 5.7-3.3 1.4-.9 2.9-1.9 4.6-3.1l.3-.2c2 .4 4.4.8 6.8 1.3l5.1 1.2c-.7-1.7-2.8-2.7-4-3.2-1.7-.3-3.5-.7-5.6-1 .5-.4 1-.7 1.5-.9 1.7.2 3.1.5 4.4 1 1 .4 1.8.8 2.5 1.3.1.1.3.2.4.3 1.2 1 1.9 2.3 1.9 3.6.1 1.1-.2 2.3-.8 3.5-.3.7-.8 1.4-1.3 2.1-.1.2-1 1.5-3 3.2-1.9 1.8-4.2 3.4-7 5.1-1 .6-1.9 1.1-2.9 1.6-1.2.6-2.4 1.2-3.4 1.6-1.6.7-4.3 1.9-7.7 2.9-1.8.5-3.5 1-5.2 1.3-1.3.3-2.9.5-4.5.6 1.8-.8 3.8-1.3 5.9-1.6 4-.9 7.4-2.2 9.6-3.2-2.1 0-4.2.1-6.4.3-3.6.4-6.5.9-9.1 1.8-1.5.5-3.5 1.3-4 2.6-.1.7 0 1.2.2 1.7.4.8 1.2 1.2 2.5 1.4 1 .1 2.1.1 3.6-.1 2.7-.3 5.6-.9 8.9-2 2.9-.9 5.5-2 8-3.1 2.8.1 5.6.4 8.3.9 2.9.5 5.4 1.2 7.8 2.1 2.7 1 5 2.1 6.9 3.4.7-.5 1.3-1 1.8-1.4-.1 0-.1-.1-.2-.1-2.4-1.6-5.2-3-8.2-4.1-2.5-.9-5.2-1.6-8.2-2.2-1.4-.3-2.8-.5-4.3-.6 2.4-1.3 4.5-2.6 6.4-4.1 1.7-1.3 3.1-2.6 4.4-3.9 3.4.9 6.3 1.8 8.9 2.9 3.1 1.3 5.8 2.8 8.1 4.5l.2.1c.5-.7.9-1.5 1.2-2.1-2.1-1.5-4.4-2.8-6.9-4-2.8-1.3-5.9-2.4-9.3-3.3-.1 0-.2-.1-.4-.1 1.5-2.1 2.4-4.1 2.6-6 .1-.6.1-1.1 0-1.7 2.9.9 5.7 2 8.3 3.2 2.6 1.2 4.8 2.5 6.7 4l.1.1c-.5-2.1-1.6-3.7-2.2-4.4-1.2-.7-2.5-1.3-3.9-2-2.4-1.1-5.1-2.1-8-3-.6-.2-1.3-.4-1.9-.5h-.1c-.9-1.6-2.3-2.5-3.4-3.1-1.2-.6-2.6-1.1-4.2-1.4.7-.1 1.3-.2 2-.2h.2c.6 0 1.3 0 2 .1.2 0 .3 0 .5.1 1.7.2 3.4.6 5.3 1.2 2.2.7 4.3 1.6 6.1 2.7 2.3 1.3 4.2 2.8 5.7 4.5.5.6 1 1.2 1.4 1.8.1.1.2.2.2.4 0 0 0 .1.1.1.7 1.2 1.4 2.8 1.5 4.7.2 2-.2 4-.8 5.6 0 .1-.8 2.3-2.2 4.3-1.4 2.1-3.3 4.2-5.6 6.2-.5.5-2 1.8-4.1 3.2-2 1.4-4.1 2.7-6.3 3.9-1.7 1-3.5 1.8-5.7 2.8-.9.4-2.2.9-3.7 1.4-2.4.9-4.8 1.6-7.2 2.2-3.5.8-6.6 1.3-9.6 1.5-1.2.1-2.3.1-3.4 0-1.6-.1-3.3-.3-4.3-1.2l-.2-.2v-.2c.2-.6.7-1 1.2-1.4.7-.5 1.5-.9 2.5-1.3 2.3-.9 4.9-1.5 7.9-1.8 2.8-.2 5.7-.1 8.4.3 1.4.2 2.8.6 4.2 1 1-.3 2-.7 2.7-1-1.7-.7-3.6-1.3-5.6-1.8-2.8-.6-5.8-.8-8.8-.7-3.1.1-6 .6-8.6 1.4-2.1.7-4.4 1.6-5.8 3.4-.6.8-.9 1.7-.7 2.7.2 1.2 1.2 2 1.7 2.3 1.3.8 2.9 1.2 4 1.3 1.2.2 2.5.3 3.9.3h.7c2.9-.1 6-.5 9.7-1.3 3.1-.7 6.3-1.6 9.6-2.9.9-.4 1.9-.7 2.8-1.1 1.5 1 2.6 2.1 3.3 3.3.7 1.2 1 2.3 1 3.5 0 1.1-.3 2.2-.9 3.2-.1.3-.3.5-.5.8.7-.2 1.4-.5 2.1-.8l.3-.6c.5-1.3.7-2.7.5-4-.2-1.5-.9-3-2-4.3-.5-.7-1.2-1.3-1.9-1.9 3.2-1.5 6.1-3.1 8.7-4.8 1.3-.9 2.6-1.8 3.8-2.7 2 1.9 3.5 4 4.2 6.3.4 1.2.6 2.4.6 3.7.8-.7 1.5-1.3 2-1.8-.2-1.8-.8-3.5-1.8-5.2-.8-1.5-2-2.9-3.4-4.3 2.7-2.3 4.9-4.7 6.5-7.2.1-.1.2-.3.3-.4 2 2 3.5 4.2 4.5 6.4v.1c.2.4.3.9.5 1.3.7-1.6 1-3 1.1-3.9-.8-1.6-1.9-3.1-3.1-4.4-.5-.6-1.1-1.1-1.7-1.7 1.1-2.3 1.8-4.5 2-6.6.5.6 1 1.2 1.4 1.8 1.5 2.3 2.5 4.7 2.7 7 .1.9.1 1.7.1 2.6 0 .1 0 1-.3 2.4 0 .2-.1.5-.2.7-.3 1.1-.8 2.5-1.5 4-.1.1-.1.3-.2.4-.1.1-.1.3-.2.4-1.3 2.4-3.1 4.8-5.4 7-.3.3-.6.6-1 .9-.8.8-2 1.8-3.1 2.6-2.2 1.7-4.6 3.2-7.1 4.5-1.9 1-3.9 2-6 2.8-2.2.9-4.3 1.6-5.9 2-3 .8-5.9 1.4-8.7 1.7-2.6.2-4.6.2-6.5-.1-1.2-.2-2.1-.5-2.9-.9-.2-.1-.4-.3-.5-.4 0-.1-.1-.1-.1-.2v-.2c.4-1 1.7-1.5 3-1.9 1.2-.4 2.7-.6 4.3-.6h.2c1.5 0 3 .2 4.6.6 1.5.3 3 .8 4.3 1.3.1 0 .1.1.2.1.6-.1 1.3-.3 2.2-.6-.1 0-.2-.1-.4-.1-.6-.2-1.2-.5-1.8-.7-1.7-.7-3.1-1.1-4.5-1.5-1.7-.4-3.4-.7-5-.7-1.7-.1-3.4.1-5 .5-1.7.4-2.9 1.1-3.8 1.9-.6.6-.9 1.4-.9 2.2 0 .8.4 1.6 1.1 2.2 1.8 1.6 4.7 2 7 2.1 2.9.2 6-.1 9.4-.7.4-.1.9-.2 1.3-.3-.3.5-.6 1-.7 1.6-.1.9.4 1.8 1.4 2.3.9.5 2.1.8 3.7.8h.9c2.5-.1 5.1-.7 8-1.8 2.9-1 5.6-2.5 8.2-4.2 2.3-1.6 4.5-3.5 6.3-5.6 1.9-2.2 3.5-4.6 4.5-7.1 1.1-2.5 1.6-5.3 1.5-8 0-.4 0-.8-.1-1.2 1.8-2.9 2.5-5.9 2.5-8.8"
              id="path8239" fill="#e30613" stroke-width="1.4895"/>
    </g>
</g>
</svg>}
    href="/integrations/payments/worldpay"
  >
    >

    Sync Worldpay payments data to get more accurate insights and recover revenue.
  </Card>
</CardGroup>

### Missing an integration?

We're continuously expanding our integrations. If you have a specific integration in mind, please let us know by [contacting us](https://www.slickerhq.com/contact).


# Chargebee
Source: https://docs.slickerhq.com/integrations/billing/chargebee

Learn how to connect Chargebee to Slicker

### Prerequisites

Slicker integrates with Chargebee via an API key. Creating a Chargebee API key requires a user who is an
`Admin` or `Owner` of the Chargebee site.

### Create credentials

1. Create a new API key by going to `Settings > Configure Chargebee > API Keys and Webhooks` and then click on the `API Keys` tab.
   Then click on the `Add an API Key` button.

2. Give the API key a meaningful name like `Slicker`.

3. Select the `type` of the key as `Full-Access Key` with either `All` or `Write Key` permissions.

   <Warning>If the credentials are read-only, Slicker will not be able to retry failed transactions and recover revenue. </Warning>

   It should look something like this.

   <Frame>
     <img alt="Chargebee API key creation" />
   </Frame>

4. Click `Create Key` and copy the generated key - we will need it later.

### Create integration in Slicker

1. Go to the Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Chargebee` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the API key you copied earlier.
5. Enter your Chargebee site - for example, if you are using `https://{yourcompany}.chargebee.com`, enter `yourcompany`.
6. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Chargebee using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Slicker API Overview
Source: https://docs.slickerhq.com/integrations/billing/custom/api/overview

Custom billing system API endpoints for sending data to Slicker

## API Basics

The Slicker API is a RESTful HTTP API that allows you to integrate your custom billing system with Slicker's retry optimization and revenue recovery platform.

* **Protocol**: HTTPS only (unencrypted HTTP is not supported)
* **Base URL**: `https://api.slickerhq.com`
* **Data Format**: All requests and responses use JSON format
* **Character Encoding**: UTF-8

## Authentication

The API uses Bearer token authentication. You'll receive an API key from Slicker which should be included in all API requests via the Authorization header:

```
Authorization: Bearer YOUR_API_KEY
```

Your API key grants access to sensitive data and should be kept secure. Do not share your API key in publicly accessible areas such as GitHub, client-side code, or in API requests to other services.

## API Endpoints

Slicker's custom billing API includes the following primary endpoints:

| Endpoint | Description |
| - | - |
| `/v1/invoices` | Send invoice data to Slicker |
| `/v1/subscriptions` | Send subscription data to Slicker |
| `/v1/transactions` | Send transaction data to Slicker |
| `/v1/recovery_actions` | Retrieve recommended recovery actions |

Each endpoint accepts specific data formats as detailed in the [API Reference](/integrations/billing/custom/api/slicker/add_invoices).

## Request Limits

* **Maximum Batch Size**: Each API request can contain up to 200 items (invoices, subscriptions, or transactions)
* **Rate Limiting**: The API implements rate limiting to ensure stable performance for all users
* **Concurrency**: We recommend no more than 5 concurrent requests per second

If you exceed these limits, the API will return a `429 Too Many Requests` response. Implement appropriate backoff strategies in your integration.

## Best Practices

### Data Synchronization

* **Batching**: Group related data in batches for more efficient processing
* **Frequency**: Send data in real-time or near real-time for optimal recovery results
* **Completeness**: Include as many optional fields as possible for better recovery strategies

### Error Handling

* Implement retry logic with exponential backoff for failed requests
* Log all API interactions for troubleshooting purposes
* Monitor API responses for error patterns

### Testing

Before going live, thoroughly test your integration using:

1. Historical data synchronization with the Slicker API
2. Real-time event transmission
3. Query for recovery actions

## API Versioning

The API version is included in the URL path (e.g., `/v1/invoices`). When new versions are released, we'll provide appropriate migration guidance and timelines.

## Support

For API support or questions:

* Check the detailed [API Reference](/integrations/billing/custom/api/slicker/add_invoices)
* Contact your Slicker integration specialist
* Email [support@slickerhq.com](mailto:support@slickerhq.com)

## Next Steps

* Review the [API Reference](/integrations/billing/custom/api/slicker/add_invoices) for detailed endpoint specifications and data formats
* Learn about the [Webhook Implementation](/integrations/billing/custom/api/webhook) required for receiving retry instructions


# Add invoices
Source: https://docs.slickerhq.com/integrations/billing/custom/api/slicker/add_invoices

api.yaml POST /v1/invoices



# Add subscriptions
Source: https://docs.slickerhq.com/integrations/billing/custom/api/slicker/add_subscriptions

api.yaml POST /v1/subscriptions



# Add transactions
Source: https://docs.slickerhq.com/integrations/billing/custom/api/slicker/add_transactions

api.yaml POST /v1/transactions



# List recovery actions
Source: https://docs.slickerhq.com/integrations/billing/custom/api/slicker/list_recovery_actions

api.yaml GET /v1/recovery_actions



# Webhook Implementation
Source: https://docs.slickerhq.com/integrations/billing/custom/api/webhook

How to implement webhook endpoints for receiving events from Slicker

## Overview

As part of the Slicker integration, you need to implement webhook endpoints that Slicker will call to deliver optimization decisions and dunning instructions to your billing system. All webhook events use a unified structure with a consistent envelope format.

```mermaid theme={null}
sequenceDiagram
    participant S as Slicker
    participant Y as Your Webhook Endpoints
    participant B as Your Billing System
    S->>Y: POST /recovery_action (payment retry)
    Y->>Y: Validate request & authenticate
    Y->>B: Forward event data
    B->>B: Process event based on type
    Y->>S: Return 200 OK response
    S->>Y: POST /pause_collection (pause retries)
    Y->>B: Forward event data
    Y->>S: Return 200 OK response
    S->>Y: POST /complete_dunning (dunning complete)
    Y->>B: Forward event data
    Y->>S: Return 200 OK response
```

## Implementation Requirements

### Endpoint Configuration

* **Protocol**: HTTPS only (unencrypted HTTP is not supported)
* **Method**: POST
* **URL**: You define the webhook URL used for all event types and provide it to Slicker during integration setup
* **Content Type**: application/json

### Authentication

Your webhooks must implement one of the following authentication methods to ensure that only Slicker can trigger events:

#### Bearer Token Authentication

```
Authorization: Bearer YOUR_WEBHOOK_TOKEN
```

You'll provide this token to Slicker during integration setup.

#### Basic Authentication

```
Authorization: Basic base64(username:password)
```

You'll provide the username and password to Slicker during integration setup.

## Unified Event Structure

All webhook events use a consistent envelope format:

```json theme={null}
{
  "id": "evt_2uqkAo1bwllmzrgV2qtGv48DtGI",
  "type": "recovery_action",
  "created": "2023-01-18T09:00:00Z",
  "data": {
    // Event-specific fields
  }
}
```

### Common Fields

| Field | Type | Description |
| - | - | - |
| `id` | string | Unique identifier for this webhook event |
| `type` | string | Event type identifier (e.g., `recovery_action`, `pause_collection`, `complete_dunning`) |
| `created` | string | ISO 8601 timestamp of when the webhook was created |
| `data` | object | Event-specific payload that varies based on the event type |

## Event Types

### Recovery Action Event

Sent when a payment should be retried:

```json theme={null}
{
  "id": "evt_2uqkAo1bwllmzrgV2qtGv48DtGI",
  "type": "recovery_action",
  "created": "2023-01-18T09:00:00Z",
  "data": {
    "invoiceId": "inv_12345678",
    "subscriptionId": "sub_12345678",
    "actionSuggestion": "ACTION_SUGGESTION_RETRY",
    "idealRetryTime": "2023-01-18T09:30:00Z"
  }
}
```

**Action Suggestion Values:**

* `ACTION_SUGGESTION_RETRY`: Attempt to process the payment again
* `ACTION_SUGGESTION_CARD_CHANGE`: Request an updated payment method from the customer
* `ACTION_SUGGESTION_UNSPECIFIED`: No specific action recommended

### Pause Invoice Collection Event

Sent when automatic retries should be paused. This is used during A/B tests to control which invoices should be retried by Slicker vs your system.

```json theme={null}
{
  "id": "evt_3vrkBp2cxmmn0shW3ruHw59EuHJ",
  "type": "pause_collection",
  "created": "2023-01-18T10:00:00Z",
  "data": {
    "invoiceId": "inv_12345678"
  }
}
```

### Complete Dunning Event

Sent when dunning should be completed before the dunning period ends.

```json theme={null}
{
  "id": "evt_4wslCq3dynn1ptiX4svIx60FvIK",
  "type": "complete_dunning",
  "created": "2023-01-18T11:00:00Z",
  "data": {
    "invoiceId": "inv_12345678"
  }
}
```

## Response Format

Your webhook should respond with a 200 OK status code and an optional JSON body if the event was successfully received:

```json theme={null}
{
  "success": true,
  "message": "Event processed successfully"
}
```

## Implementation Best Practices

### Security

* Use HTTPS with valid SSL certificates
* Set up authentication with strong credentials
* (Optional) Implement IP whitelisting (Slicker can provide IP ranges)

### Reliability

* Acknowledge receipt quickly and process asynchronously
* Implement idempotent processing based on event `id` to handle potential duplicate webhooks
* Return appropriate error codes if requests can't be processed
* Slicker will retry failed webhooks, so ensure idempotency

## Retry Policy

Slicker automatically retries failed webhook deliveries using a two-phase strategy: immediate synchronous retries followed by delayed asynchronous retries.

A delivery is considered successful when your endpoint returns any `2xx` HTTP status code within **30 seconds**. Any other response (or a timeout/connection error) is treated as a failure and triggers retries.

### Recovery Action Events

Recovery action webhooks are retried up to **6 total attempts**:

| Attempt | Type | Delay after previous attempt |
| - | - | - |
| 1 | Initial delivery | — |
| 2 | Sync retry | \~100ms |
| 3 | Sync retry | 5 seconds |
| 4 | Sync retry | 15 seconds |
| 5 | Async retry | 15 minutes |
| 6 | Async retry | 30 minutes |

After 6 failed attempts, the webhook is marked as **exhausted** and no further retries occur.

### Pause Collection & Complete Dunning Events

These event types are retried up to **7 total attempts**:

| Attempt | Type | Delay after previous attempt |
| - | - | - |
| 1 | Initial delivery | — |
| 2 | Sync retry | \~100ms |
| 3 | Sync retry | 5 seconds |
| 4 | Sync retry | 15 seconds |
| 5 | Async retry | 15 minutes |
| 6 | Async retry | 30 minutes |
| 7 | Async retry | 1 hour |

After 7 failed attempts, the webhook is marked as **exhausted** and no further retries occur.

### Handling Retries

<Info>
  Each webhook event has a unique `id` field. Use this to deduplicate events on your side — you may receive the same event more than once if your endpoint returned a success after Slicker's timeout window or due to network issues.
</Info>

* **Respond quickly**: Return a `2xx` within 30 seconds. If processing takes longer, acknowledge receipt immediately and process the event asynchronously.
* **Idempotency**: Store the event `id` and skip processing if you've already handled it.
* **Monitoring**: If all retries are exhausted, the event is marked as failed in Slicker's delivery logs. Contact support if you experience persistent delivery failures.

### Monitoring

* Set up alerts for failed webhook calls
* Monitor webhook endpoint uptime

## Reference Documentation

For detailed API specifications, see:

* [Recovery Action Event](/integrations/billing/custom/api/your/webhooks/recovery_action)
* [Pause Collection Event](/integrations/billing/custom/api/your/webhooks/pause_collection)
* [Complete Dunning Event](/integrations/billing/custom/api/your/webhooks/complete_dunning)

## Support

If you need assistance with your webhook implementation:

* Contact your Slicker integration specialist
* Email [support@slickerhq.com](mailto:support@slickerhq.com)


# Webhook API (Deprecated)
Source: https://docs.slickerhq.com/integrations/billing/custom/api/your/deprecated/overview



<Warning>
  **This API version is deprecated.** Please migrate to [the latest Webhook definitions](/integrations/billing/custom/api/your/webhooks) which provides a unified webhook endpoint for all event types.
</Warning>

## What's Changing

The v1 webhook API used separate endpoints for each event type:

* `/recovery_action` - Payment retry instructions

**v2 improvements:**

* Single unified `/events` endpoint for all webhook events
* Consistent event envelope structure with `id`, `type`, `created`, and `data` fields
* Additional event types including `complete_dunning`
* Easier to extend and maintain

## Migration Path

To migrate from v1 to v2:

1. Update your webhook endpoint to accept POST requests at a single `/events` path
2. Parse the `type` field in the request body to determine the event type
3. Handle event-specific data from the `data` field based on the event type
4. Test with all three event types: `recovery_action`, `pause_collection`, and `complete_dunning`


# Handle recovery action
Source: https://docs.slickerhq.com/integrations/billing/custom/api/your/deprecated/recovery_action

v1.yaml POST /recovery_action



# Complete Dunning Event
Source: https://docs.slickerhq.com/integrations/billing/custom/api/your/webhooks/complete_dunning

v2.yaml webhook complete_dunning
This webhook is triggered when dunning should be completed for an invoice.
Sent when a hard error occurs or the maximum number of retries is reached.




# Pause Invoice Event
Source: https://docs.slickerhq.com/integrations/billing/custom/api/your/webhooks/pause_collection

v2.yaml webhook pause_collection
This webhook is triggered by Slicker to instruct the merchant to pause automatic retries for a specific invoice.




# Recovery Action Event
Source: https://docs.slickerhq.com/integrations/billing/custom/api/your/webhooks/recovery_action

v2.yaml webhook recovery_action
This webhook is triggered by Slicker when its algorithms determine a payment should be retried.        




# Launch guide
Source: https://docs.slickerhq.com/integrations/billing/custom/launch_guide

Plan, build, test, and roll out a custom billing integration

Use this guide when your billing system is custom-built or heavily customized. It turns the custom integration pieces into an end-to-end launch plan: data sync, recovery decisions, webhook handling, historical data, testing, rollout, and monitoring.

For endpoint details, see the [custom API reference](/integrations/billing/custom/api/overview). For the overall integration model, start with the [custom billing overview](/integrations/billing/custom/overview).

## What You Are Building

A custom billing integration has four core parts:

1. **Data sync**: Send subscriptions, invoices, and transaction attempts to Slicker.
2. **Recovery decision path**: Receive Slicker's retry and dunning recommendations by webhook, or query them from the API.
3. **Historical backfill**: Send enough past billing and payment activity for Slicker to understand your recovery patterns.
4. **Operational monitoring**: Track data freshness, webhook delivery, recovery action execution, and mismatches against your billing system.

<Info>
  Connect payment processor integrations whenever possible. Processor data gives Slicker richer authorization outcomes, gateway error codes, scheme response codes, issuer details, and payment-method metadata.
</Info>

## Phase 1: Confirm the Integration Shape

Before writing code, agree the following details with your Slicker integration team:

| Decision | What to Confirm |
| - | - |
| Canonical IDs | Which IDs uniquely identify customers, subscriptions, invoices, and transactions in your billing system. |
| Sync model | Whether you will send events in near real time, run scheduled batch syncs, or use both. |
| Payment source of truth | Which system owns final payment state and transaction outcomes. |
| Recovery execution | Whether your system will execute retries from webhooks, poll recovery actions, or use a hybrid model. |
| Dunning ownership | Which system sends recovery emails and when collection should pause or complete. |
| Historical window | How many months of invoices, subscriptions, and transactions to backfill before launch. |
| Rollout cohort | Whether launch starts with all traffic or a subset by product, country, plan, or business entity. |

The most important rule is stable identity. Use the same external IDs for historical backfill and future live events so Slicker can connect invoices, transactions, and recovery outcomes over time.

## Phase 2: Build the Data Sync

Send data in dependency order when possible:

<Steps>
  <Step title="Sync subscriptions">
    Send the active and historical subscriptions that invoices belong to. Include customer, plan, currency, billing cycle, status, and lifecycle timestamps when available.
  </Step>

  <Step title="Sync invoices">
    Send invoices with their current collection state, amount, currency, due date, subscription ID, customer ID, and timestamps.
  </Step>

  <Step title="Sync transactions">
    Send each payment attempt, including failed attempts and retries. A transaction is one authorization attempt; multiple retries for the same invoice should be sent as separate transactions.
  </Step>

  <Step title="Keep records fresh">
    Send updates when invoice status, subscription status, transaction outcome, customer details, or payment-method context changes.
  </Step>
</Steps>

### Sync Rules

* Treat API requests as idempotent from your side: retry failed requests safely and keep your external IDs stable.
* Preserve original event timestamps. Do not replace historical timestamps with the sync time.
* Send failed and successful payment attempts. Recovery analysis needs both sides of the funnel.
* Keep batch sizes within API limits. See the [custom API overview](/integrations/billing/custom/api/overview#request-limits).
* Log every request ID, response status, and failed payload reference so issues can be replayed.

## Phase 3: Implement Recovery Actions

Slicker can tell your system when to retry a payment, when to request a payment-method change, when to pause collection, and when dunning should complete.

### Webhook Path

If you use webhooks, implement one HTTPS endpoint that accepts Slicker events:

* Authenticate requests with the agreed bearer token or basic auth credentials.
* Return a `2xx` response quickly after validating and queuing the event.
* Process events asynchronously when retry execution may take longer than a few seconds.
* Deduplicate by webhook event ID.
* Store the original payload for audit and replay.
* Alert on repeated non-`2xx` responses or processing failures.

See [Webhook Implementation](/integrations/billing/custom/api/webhook) for payload structure and event-specific references.

### Polling Path

If you poll recovery actions, run the poller frequently enough to act before recommended retry windows pass. Store the last successful poll time, deduplicate actions by ID, and alert if polling stops or returns repeated errors.

See [List recovery actions](/integrations/billing/custom/api/slicker/list_recovery_actions) for endpoint details.

## Phase 4: Backfill Historical Data

Historical data helps Slicker learn payment behavior before live recovery begins.

Recommended approach:

1. Select a backfill window with the Slicker integration team. Six to twelve months is often useful when available.
2. Backfill subscriptions first, then invoices, then transactions.
3. Preserve original timestamps and final states.
4. Include recovered, unrecovered, refunded, voided, and still-open invoices when available.
5. Reconcile counts against your billing system before launch.

Useful reconciliation checks:

| Check | Expected Result |
| - | - |
| Invoice count by month | Matches your billing system within the agreed scope. |
| Transaction count by month | Matches payment attempts, not just invoices. |
| Failed transaction count | Includes initial failures and failed retries. |
| Recovery outcomes | Paid-after-failure invoices are distinguishable from first-attempt successes. |
| Currency and country coverage | High-volume segments are present and mapped correctly. |

## Phase 5: Test Before Launch

Run these tests in a non-production or controlled rollout environment before enabling full recovery automation:

| Scenario | What to Verify |
| - | - |
| Successful first-attempt invoice | Invoice and transaction sync without entering recovery. |
| Failed invoice | Failed transaction creates the expected recovery context. |
| Retry succeeds | The successful retry is sent as a new transaction and closes the invoice. |
| Retry fails | The failed retry is sent as a new transaction and recovery remains open. |
| Payment-method change needed | Your system can route the customer to the correct update flow. |
| Pause collection event | Your billing system pauses its own collection logic when instructed. |
| Complete dunning event | Your billing system stops dunning for the invoice when instructed. |
| Duplicate webhook delivery | Processing is idempotent and does not double-retry. |
| Webhook delivery failure | Slicker retries delivery and your alerts fire. |
| API failure | Your sync retries with backoff and preserves failed payloads for replay. |

## Launch Checklist

Before launch, confirm:

* API credentials are stored securely and not exposed in client-side code.
* Subscriptions, invoices, and transactions are syncing successfully.
* Historical data has been reconciled for the agreed launch scope.
* Webhook authentication, idempotency, and alerting are live.
* Recovery actions are being executed in the correct billing-system environment.
* Payment provider integrations are connected where applicable.
* Your team has an owner for integration incidents.
* You have a rollback plan, such as pausing webhook execution or disabling the rollout cohort.

## Rollout Plan

Start with visibility before automation:

<Steps>
  <Step title="Shadow mode">
    Send live data and inspect recovery recommendations without executing automated retries from Slicker.
  </Step>

  <Step title="Limited cohort">
    Enable recovery execution for a small, representative cohort such as one business entity, country, product, or plan family.
  </Step>

  <Step title="Measure and reconcile">
    Compare Slicker recovery actions, billing-system retries, invoice outcomes, and customer impact.
  </Step>

  <Step title="Expand">
    Increase the rollout scope once data freshness, webhook success, and recovery results are stable.
  </Step>
</Steps>

## Monitor After Launch

Track these signals during the first weeks after launch:

* API ingestion failures and retry volume.
* Data freshness for invoices, subscriptions, and transactions.
* Webhook delivery success rate and processing latency.
* Recovery action backlog or actions missed after their ideal retry time.
* Invoice recovery rate, failed recovery rate, and recovered amount.
* Differences between Slicker counts and your billing system counts.

If any metric regresses, pause expansion and review the affected payloads with the Slicker integration team.

## Next Steps

* Review endpoint details in the [custom API reference](/integrations/billing/custom/api/overview).
* Implement webhook handling with [Webhook Implementation](/integrations/billing/custom/api/webhook).
* Add your payment processors from the [payment provider integrations](/integrations/overview#payment-providers).


# Overview
Source: https://docs.slickerhq.com/integrations/billing/custom/overview

Integrating a custom billing system with Slicker

Slicker provides a flexible API-based integration for custom in-house billing systems, allowing businesses with proprietary or unique billing solutions to benefit from our advanced retry optimization and revenue recovery capabilities.

## How Custom Billing Integration Works

With a custom billing integration, Slicker acts as a decision engine for your billing system, determining the optimal timing and strategy for payment retries. This data-driven approach significantly improves recovery rates compared to static retry schedules.

```mermaid theme={null}
flowchart LR
    A[Your Billing System] -->|Event Data| B[Slicker Platform]
    C[Payment Processors] -->|Enriched Data| B
    B -->|Analytics & Machine Learning| D[Retry Decisions]
    D -->|Webhook to Your System| E[Optimized Retries]
    B <-.->|API Queries| A
```

### Integration Flow

1. **Data Ingestion**: Your system sends subscription, invoice, and transaction event data to Slicker's API endpoints.
2. **Payment Data Enrichment**: Optionally connect your [payment processors](/integrations/overview#payment-providers) directly to Slicker for enhanced data quality.
3. **Intelligent Analysis**: Slicker analyzes payment failures, customer behavior, and numerous other factors.
4. **Optimized Retry Execution**: When Slicker determines a retry should occur:
   * Slicker sends a webhook notification to your endpoint with retry instructions
   * Alternatively, your system can query Slicker's API to check when retries should be performed

## Integration Requirements

### Your Responsibilities

1. **Event Transmission**: Implement API calls to send subscription, invoice, and transaction events to Slicker
2. **Data Mapping**: Map your system's data fields to Slicker's expected format
3. **Webhook Endpoint**: Create an endpoint to receive retry instructions from Slicker
4. **Retry Execution**: Hook up the Slicker retry decision with your existing logic to execute retries. At this step you can perform further checks based on your business requirements if a retry should be executed.

### Data Requirements

While most fields are optional, the quality of Slicker's recovery strategies improves with the richness of data provided:

```mermaid theme={null}
flowchart TD
    A[Required Data] -->|Minimum| B[Basic Recovery]
    C[Additional Data] -->|Enhanced| D[Improved Recovery]
    E[Full Data + Payment Processor] -->|Optimal| F[Maximum Recovery]
```

* **Essential Events**: Subscription creations/changes, invoice generation, payment attempts
* **Valuable Context**: Customer history, subscription details, failure reasons
* **Complete Details**: See the [API Reference](/integrations/billing/custom/api/overview) for comprehensive field specifications

## Setup Process

Setting up a custom billing integration typically follows these steps:

<Steps>
  <Step title="Initial Consultation">
    Meet with Slicker's integration team to discuss your specific needs and system architecture.
  </Step>

  <Step title="API Implementation">
    Develop the necessary API calls to send event data to Slicker and receive retry instructions.
  </Step>

  <Step title="Testing and Validation">
    Verify data accuracy and webhook functionality in a test environment.
  </Step>

  <Step title="Progressive Rollout">
    Start with a subset of accounts to validate performance before full deployment.
  </Step>
</Steps>

## Historical Data Sync

While Slicker can start working with new incoming data immediately, syncing historical data significantly improves the effectiveness of our recovery strategies from day one:

```mermaid theme={null}
flowchart LR
    A[Historical Data] -->|Machine Learning| B[Improved Initial Accuracy]
    B -->|Better Recovery| C[Faster ROI]
```

### Benefits of Historical Data

* **Faster Learning**: Slicker's algorithms can immediately analyze past payment patterns and failures
* **Better Initial Results**: Recovery strategies are optimized from the start rather than requiring a learning period
* **Complete Customer Context**: Full payment history provides crucial context for decision-making

### Sync Options

* **Standard API**: The same APIs used for ongoing data can be used to sync historical events
* **Bulk Import**: For large data volumes, our integration team can work with you on custom bulk import solutions
* **Selective History**: Even partial history (e.g., last 3-6 months) provides significant benefits

<Info>
  The Slicker integration team will help determine the optimal amount of historical data to sync based on your business model and data volume.
</Info>

## Engineering Support

We understand that implementing a custom integration requires engineering resources. Slicker provides:

* Dedicated integration specialists to guide your team
* Documentation and code samples to accelerate development
* Technical consultation throughout the implementation process
* Ongoing support post-implementation

<Info>
  For optimal results, we highly recommend also integrating your payment processors directly with Slicker. This provides essential payment error details that significantly improve recovery rates. See our [payment provider integrations](/integrations/overview#payment-providers) for more information.
</Info>

## Next Steps

To begin your custom billing integration:

1. Review our [API Reference](/integrations/billing/custom/api/overview) to understand data requirements
2. [Contact our team](https://www.slickerhq.com/contact) to schedule an integration consultation
3. Explore connecting your [payment processors](/integrations/overview#payment-providers) for enhanced results


# Piano
Source: https://docs.slickerhq.com/integrations/billing/piano

Learn how to connect Piano to Slicker

### Prerequisites

Slicker integrates with Piano via the [Piano API](https://docs.piano.io/api). To connect Piano to Slicker, you will need:

* An **API Token** with sufficient permissions to manage subscriptions and payments.
* Your **Application ID (aid)**, which uniquely identifies your Piano application.
* Your **Piano API URL**, which depends on your Piano environment (e.g., sandbox vs production).

Only Piano users with administrator-level access can create API tokens.

### Create credentials

1. Log in to your Piano dashboard.

2. Navigate to the API tokens section to generate a new API token.

3. Give the token a descriptive name like `Slicker`.

4. Copy the generated **API Token**. We will need it later.

5. Note your **Application ID (aid)**. You can find this in your Piano dashboard settings.

6. Note your **API URL**. This is the base URL for your Piano environment. For example:
   * Production: `https://api.piano.io`
   * Sandbox: `https://sandbox.piano.io`

### Create integration in Slicker

1. Go to the Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Piano` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the **API Token** you copied earlier.
5. Enter your **Application ID (aid)**.
6. Enter your **API URL**.
7. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Piano using the provided credentials.
If the connection fails, you will see an error message like the one below.
Please double-check the API token, Application ID, and URL, then try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Recharge
Source: https://docs.slickerhq.com/integrations/billing/recharge

Learn how to connect Recharge to Slicker

### Prerequisites

Slicker integrates with Recharge via an API key. Creating a Recharge API key requires a Recharge user with permissions for `Admin -> API Tokens`.
By default, only the storeowners have this permission, but they can update account permissions to grant access to other users.

### Create credentials

1. Go to your Recharge merchant portal to create an API key. This is under `Tools & apps -> API Tokens`.

2. Click the `Create an API Token` button to generate a new API token for your store.
   <Frame>
     <img alt="Recharge API token creation button" />
   </Frame>

3. Use the `Details` field to set a name and contact email for the token.

4. Select `Read and Write access` to set the permissions for the token.

   <Warning>If the credentials are read-only, Slicker will not be able to retry failed transactions and recover revenue. </Warning>

5. Click `Save` and copy the generated key - we will need it later.

### Create integration in Slicker

1. Go to the Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Recharge` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the API key you copied earlier.
5. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Recharge using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Recurly
Source: https://docs.slickerhq.com/integrations/billing/recurly

Learn how to connect Recurly to Slicker

### Prerequisites

Slicker integrates with Recurly via an API key. Creating a Recurly API key requires a Recurly user with a role that has the `Integrations` permission.
If you are using the default roles, the `Site Admin` role has this permission already.

### Create credentials

1. Go to your Recurly dashboard and create an API key. This is under `Integrations -> API Credentials`.

   <Frame>
     <img alt="Recurly API credentials page" />
   </Frame>

2. Click the `Add Private API Key` button. This will open a new page where you can configure the API Key.
   Add an appropriate name like `Slicker` and ensure the `Read-Only` checkbox is **not** selected.

   <Warning>If the credentials are read-only, Slicker will not be able to retry failed transactions and recover revenue. </Warning>

   It should look something like this.

   <Frame>
     <img alt="Recurly Private API keys configuration page" />
   </Frame>

3. Click `Save Changes` and copy the generated key.

### Create integration in Slicker

1. Go to the Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Recurly` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the API key you copied earlier.
5. Enter the Recurly dashboard URL for your Recurly instance - for example, `https://yourcompany.recurly.com`.
   This will be useful when you need to navigate to the Recurly dashboard from Slicker.
6. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Recurly using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Stripe Billing
Source: https://docs.slickerhq.com/integrations/billing/stripe

Learn how to connect Stripe Billing to Slicker

### Prerequisites

Slicker integrates with Stripe via an API key. Creating a Stripe API key requires a Stripe user enough permissions to do so.
Stipe user roles that have this permission include `Administrator`, `Super Administrator`, and `Developer`.

### (Option 1: Stripe Marketplace App) Integerate via the Stripe Marketplace

1. Go to the [Slicker App page in the Stripe Marketplace](https://marketplace.stripe.com/apps/slicker).
2. Click on the `Install` button.
3. Follow the instructions to authorize Slicker to access your Stripe account.
4. Once authorized, you will be able to use click the `Link` button in the Slicker app page to link your Stripe account to your Slicker instance.

### (Option 2: API Key) Create credentials

1. Go to the Stripe dashboard to create a new restricted API key [here](https://dashboard.stripe.com/apikeys/create).

2. Give the key a name like `Slicker`.

3. For permissions select the following:

   * `Read` on `All core resources`

   <Frame>
     <img alt="Stripe read permissions on core resources" />
   </Frame>

   * `Read` on `All Connect resources`

   <Frame>
     <img alt="Stripe read permissions on connect resources" />
   </Frame>

   * `Read` on `All Reporting resources`

   <Frame>
     <img alt="Stripe read permissions on reporting resources" />
   </Frame>

   * `Read` on all `Billing` resources, with `Write` on `Invoices`.
     <Warning>The `Write` permission on `Invoices` is required for Slicker to retry failed transactions and recover revenue.</Warning>

   <Frame>
     <img alt="Stripe billing permissions" />
   </Frame>

   * *(Optional)* `Write` on `Subscriptions`.
     <Note>Add `Write` on `Subscriptions` only if you want Slicker's [Grace Period Manager](/essentials/grace_periods) to cancel subscriptions when their grace period ends. Marking invoices uncollectible is already covered by the `Write` on `Invoices` permission above. Cancelling subscriptions is the one grace-period action that needs this extra scope.</Note>

4. Click the `Create key` button. If prompted confirm your password. Copy the generated key - we will need it later.

### (Option 2: API Key) Create integration in Slicker

1. Go to the Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Stripe` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the API key you copied earlier.
5. Make sure to select this integration is for Stripe Billing. Otherwise, Slicker will only sync payment data, without managing failed billing attempts.

<Frame>
  <img alt="Stripe Billing enabled in Slicker integration" />
</Frame>

6. Click the `Submit` button to create the integration.

### (Optional) Enable real-time webhooks

By default Slicker keeps your data in sync by polling the Stripe API on a schedule. Adding a webhook lets Stripe push changes to Slicker the moment they happen, for near real-time recovery tracking. For Stripe Billing this is especially valuable: Stripe's API has no "updated since" filter for invoices and subscriptions, so webhooks are the most reliable way to capture later status changes — a payment that finally succeeds, an invoice that's voided, a subscription that cancels — as soon as they occur.

<Note>Webhooks are configured **per Stripe account**, in that account's own Stripe Dashboard. They're optional and can be added at any time after the integration is created.</Note>

1. Open your existing Slicker integration and find **Webhooks**. Copy the **Webhook URL** and keep the page open until you save the signing secret. For a new integration, first select **Enable Webhooks** in its creation form.

2. In the matching account's [Stripe Dashboard](https://dashboard.stripe.com/webhooks), open **Workbench → Webhooks** and add a destination for **your account's events**. Use a separate destination and signing secret for each Slicker integration, including when you use an organization API key.

3. Paste the Slicker Webhook URL into the **Endpoint URL** field. Choose **snapshot events** and the newest API version the dashboard offers (a **clover** or **dahlia** version). Thin events are not supported by this setup.

4. Under **Select events**, select these **20 individual event types**. Avoid **All events** and wildcard event families:

   * **Invoices** — `invoice.finalized`, `invoice.updated`, `invoice.paid`, `invoice.payment_failed`, `invoice.payment_action_required`, `invoice.marked_uncollectible`, `invoice.voided`
   * **Subscriptions** — `customer.subscription.created`, `customer.subscription.updated`, `customer.subscription.deleted`, `customer.subscription.paused`, `customer.subscription.resumed`
   * **Payments** — `payment_intent.succeeded`, `payment_intent.payment_failed`, `payment_intent.processing`, `payment_intent.requires_action`, `payment_intent.canceled`
   * **Customers** — `customer.created`, `customer.updated`, `customer.deleted`

   If you use **manual capture**, also select `payment_intent.amount_capturable_updated` to receive authorization updates before capture. This makes 21 event types. Keep `invoice.updated` for changes such as retry scheduling. `invoice.paid` already covers successful collection and invoices marked paid outside Stripe, so `invoice.payment_succeeded` is unnecessary.

5. Save the destination.

6. Open the endpoint you just created, reveal its **Signing secret** (it starts with `whsec_`), and copy it.

7. Back in Slicker, paste the signing secret into **Signing Secret** and select **Enable webhooks** (or submit the new integration). To rotate a secret later, use **Update secret**; keep the existing URL.

8. Confirm successful deliveries in Stripe's **Event deliveries** tab and check the corresponding records in Slicker. Slicker acknowledges every Stripe delivery, including ones it cannot verify yet, so that a setup problem never interferes with your billing; events that arrived before you saved the secret therefore show as delivered in Stripe but were not processed. Resend them from the **Event deliveries** tab after saving, or disable the destination in Stripe between steps 5 and 7 to avoid the gap. The **Configured** badge confirms saved settings; it does not confirm delivery. Updates can take roughly 30 seconds of batching plus processing time.

Keep scheduled syncing enabled. These events update customers, subscriptions, invoices, and PaymentIntents; Charge attempts, refunds, and disputes still use their existing sync paths. Adding an endpoint does not backfill old changes, and draft-invoice deletion is not handled by this event list.

<Warning>Copy the **signing secret** (`whsec_…`) — not your API key (`sk_`/`rk_`) or the endpoint ID. If you ever rotate the secret in Stripe, update it in Slicker too.</Warning>

### (Optional) Let Slicker manage the grace period

Slicker's [Grace Period Manager](/essentials/grace_periods) keeps recovering failed payments on your own schedule and decides what happens when that window ends. There are two things to set up: turn the grace period settings on in Slicker, and stop Stripe from ending the subscription itself.

<Note>The order does not matter. Slicker measures each grace period from the invoice's first failed payment, not from when you turn the feature on, so if you switch Stripe to leave invoices overdue first, they simply wait until Slicker takes over. Its next run then closes anything already past its grace period, so the backlog is handled either way.</Note>

#### Turn on grace period management in Slicker

In your Slicker integration settings, enable the grace period manager, then set the grace period length and the actions to apply when it expires.

<Frame>
  <img alt="Slicker grace period manager settings for Stripe" />
</Frame>

<Note>If you do not see these settings, [let us know](https://www.slickerhq.com/contact) and we will enable the feature for your account.</Note>

#### Turn off Stripe's automatic cancellation

Stop Stripe from ending the subscription itself, so Slicker owns the recovery window. Otherwise Stripe cancels or writes off the invoice once its own retries run out, before your grace period is up.

1. Open your Stripe [retries and recovery settings](https://dashboard.stripe.com/revenue-recovery/retries).
2. Set every failed-payment outcome to leave the invoice overdue. Do not cancel the subscription, mark it unpaid, or mark the invoice uncollectible.

<Frame>
  <img alt="Stripe retries settings with all failed-payment outcomes left as overdue" />
</Frame>

With Slicker managing the grace period and Stripe set to leave invoices overdue, Slicker applies the end-of-grace action you choose. Cancelling subscriptions also needs the optional `Write` on `Subscriptions` permission described above.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Stripe using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Zuora
Source: https://docs.slickerhq.com/integrations/billing/zuora

Learn how to connect Zuora to Slicker

### Prerequisites

Slicker integrates with Zuora via Zuora's Quickstart API. To use the Quickstart API, your Zuora tenant must have the following features enabled:

* [Orders](https://knowledgecenter.zuora.com/Billing/Subscriptions/Orders) or [Orders Harmonization](https://knowledgecenter.zuora.com/Billing/Subscriptions/Orders/Orders_Harmonization)
* [Invoice Settlement](https://knowledgecenter.zuora.com/Billing/Billing_and_Payments/Invoice_Settlement)

Only Zuora users with the appropriate permissions can create API credentials - the tenant administrator can grant these permissions and can create API credentials.

### Create credentials

Zuora API authentication requires an OAuth client ID and secret.
You should follow the [official Zuora documentation](https://developer.zuora.com/docs/get-started/introduction/#oauth-client-setup) to create these credentials. Some points to note:

* The Zuora user associated with the OAuth credentials should have a [Platform role](https://docs.zuora.com/en/zuora-platform/security-and-identity/administrator-settings/user-roles/platform-roles) with **API Write Access**.
* Assign the user the **Zuora Billing Standard User** and **Zuora Payments Standard User** roles. Together, these standard roles provide the permissions Slicker needs to read billing and payment data and recover failed payments, including:
  * **Process Electronic Payment** ([Payments roles](https://docs.zuora.com/en/zuora-platform/security-and-identity/administrator-settings/user-roles/payments-roles)) — needed to retry payment collection on invoices.
  * **Change Payment Methods** ([Billing roles](https://docs.zuora.com/en/zuora-platform/security-and-identity/administrator-settings/user-roles/billing-roles)) — needed to temporarily disable Zuora's built-in retry rules on a payment method so that Slicker controls the retry timing during an experiment, and then re-enable them afterwards.
  * **Modify Invoice** ([Billing roles](https://docs.zuora.com/en/zuora-platform/security-and-identity/administrator-settings/user-roles/billing-roles)) — needed to set custom fields on invoices for experiment tracking.
* No additional Reporting role is required. Slicker reads accounts, subscriptions, invoices, payments, payment methods, and related records through Zuora's REST and AQuA APIs. If you prefer least-privilege access, contact Slicker before creating custom Billing and Payments roles. We will provide the current list of required Zuora objects and permissions for your integration, including any features you plan to enable. This list may expand as Slicker adds capabilities to the integration. Zuora [rejects or skips AQuA queries](https://docs.zuora.com/en/zuora-platform/data/aggregate-query-api-aqua/aqua-api-error-codes) when the API user cannot access a required object.
* Make sure that the `UI Access` box is unchecked. Zuora recommends API credentials are never used for UI access.
* Copy the `Client ID` and `Client Secret` - we will need them later.

### Create integration in Slicker

1. Go to the Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Zuora` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the Client ID and Secret you copied earlier.
5. Select the base URL of your tenant from the dropdown. This is based on the data center where your Zuora tenant is hosted as detailed in [Zuora's documentation](https://knowledgecenter.zuora.com/Zuora_Environments/Zuora_Data_Centers).
6. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Zuora using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Integrations overview
Source: https://docs.slickerhq.com/integrations/overview

Integrate with your tools in 5 minutes and start recovering revenue. No code required.

Integrations are how we gain insights into lost revenue and automate the recovery process.
Adding an integration takes less than 5 minutes, requires no code, and looks something like this:

<Steps>
  <Step title="Generate credentials" icon="key">
    Generate API credentials with the appropriate permissions in your provider.
  </Step>

  <Step title="Create integration in Slicker" icon="vault">
    Create an integration in Slicker that uses these credentials.
  </Step>

  <Step title="Sit back and let the revenue flow in" icon="rocket">
    Slicker will start syncing data, providing insights, and recovering revenue. All without you lifting a finger.
  </Step>
</Steps>

For a more detailed guide for each provider, check out the individual integration pages below.

### Billing & subscription providers

The bread and butter of any subscription business. We integrate with the best billing and subscription providers to manage your revenue and reduce churn.

<CardGroup>
  <Card
    title="Chargebee"
    icon={
<svg id="logosandtypes_com" data-name="logosandtypes com"  width="36" height="36" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 150 150">
    <path class="cls-2" d="M0,0H150V150H0V0Z" fill="none"/>
    <path class="cls-1" d="M54.43,76.09l80.25-19.32V14.77h-41.61l-38.64,61.32Z" fill="#f30"/>
    <path class="cls-1" d="M14.65,75.35c0,5.02,.61,9.9,1.75,14.57l38.02-13.84-38.33-13.96c-.93,4.25-1.44,8.68-1.44,13.21h0Z" fill="#f30"/>
    <path class="cls-1" d="M28.79,36.3l25.62,39.79,11.81-60.72c-14.96,2.12-28.14,9.81-37.43,20.93Z" fill="#f30"/>
    <path class="cls-1" d="M54.43,76.09l80.25,19.31v42h-41.61l-38.64-61.31Z" fill="#f30"/>
    <path class="cls-1" d="M28.8,115.86l25.62-39.79,11.8,60.7c-14.96-2.12-28.14-9.81-37.43-20.93h.01Z" fill="#f30"/>
</svg>
}
    href="/integrations/billing/chargebee"
  >
    Automate revenue recovery for your Chargebee subscriptions.
  </Card>

  <Card
    title="Recharge"
    icon={<svg xmlns="http://www.w3.org/2000/svg" width="126" height="25" viewBox="0 0 1264 251" fill="none">
  <g clip-path="url(https://mintlify.s3.us-west-1.amazonaws.com/slicker/integrations#clip0_20_9)">
      <path d="M124.915 251C149.628 251.006 173.788 243.65 194.34 229.862C214.891 216.074 230.911 196.473 240.373 173.539C249.835 150.604 252.313 125.366 247.496 101.016C242.678 76.6666 230.781 54.2989 213.308 36.742C195.835 19.1851 173.572 7.22771 149.334 2.38208C125.096 -2.46355 99.9716 0.0202282 77.1388 9.51929C54.306 19.0184 34.7901 35.106 21.0595 55.7477C7.32878 76.3894 7.90368e-07 100.658 0 125.484C-1.05962e-06 158.767 13.1596 190.688 36.5848 214.226C60.0099 237.764 91.7824 250.991 124.915 251Z" fill="#3901F1"/>
      <path d="M136.86 175.195H74.9236C74.7368 175.241 74.5417 175.241 74.3548 175.195C74.1874 175.107 74.0374 174.989 73.9124 174.846C73.7858 174.702 73.6987 174.527 73.6596 174.338C73.6128 174.151 73.6128 173.954 73.6596 173.767L85.7308 111.485C85.785 111.261 85.8935 111.054 86.0468 110.882C86.2089 110.715 86.4189 110.604 86.6472 110.564C86.8687 110.509 87.1016 110.522 87.3157 110.601C87.5299 110.68 87.7153 110.822 87.848 111.009L137.808 173.195C137.932 173.384 137.998 173.604 137.997 173.83C138.061 174.037 138.061 174.258 137.997 174.465C137.907 174.668 137.765 174.843 137.586 174.973C137.379 175.134 137.121 175.213 136.86 175.195Z" fill="#FFFBF6"/>
      <path d="M73.786 81.1695H135.69C135.877 81.1224 136.072 81.1224 136.259 81.1695C136.447 81.2378 136.612 81.359 136.733 81.5187C136.842 81.6743 136.927 81.8455 136.986 82.0266C137.033 82.2141 137.033 82.4104 136.986 82.598L125.01 145.134C124.944 145.351 124.824 145.547 124.662 145.705C124.512 145.871 124.312 145.983 124.093 146.023C123.879 146.103 123.644 146.103 123.43 146.023C123.206 145.957 123.007 145.824 122.861 145.642L72.68 83.1059C72.6289 82.9189 72.6289 82.7215 72.68 82.5345C72.6167 82.306 72.6167 82.0645 72.68 81.8361C72.8038 81.6376 72.9648 81.4651 73.154 81.3282C73.3478 81.2221 73.5653 81.1674 73.786 81.1695Z" fill="#FFFBF6"/>
      <path d="M143.18 81.1695C142.91 81.1666 142.649 81.269 142.453 81.4552C142.226 81.6121 142.067 81.8508 142.01 82.1218C141.375 87.3054 141.834 92.5654 143.359 97.5584C144.884 102.551 147.44 107.165 150.861 111.098C154.281 115.032 158.489 118.196 163.21 120.385C167.93 122.574 173.057 123.738 178.256 123.802H179.551C179.834 123.8 180.11 123.711 180.341 123.548C180.549 123.37 180.684 123.121 180.72 122.849L189.063 82.5345C189.093 82.3559 189.093 82.1734 189.063 81.9948C188.998 81.8291 188.902 81.678 188.778 81.5504C188.661 81.4072 188.509 81.2976 188.336 81.233C188.17 81.19 187.996 81.19 187.83 81.233L143.18 81.1695Z" fill="#FFFBF6"/>
  </g>
  <defs>
      <clipPath id="clip0_20_9">
          <rect width="1264" height="251" fill="white"/>
      </clipPath>
  </defs>
</svg>}
    href="/integrations/billing/recharge"
  >
    >

    Automate revenue recovery for your Shopify or BigCommerce subscriptions managed in Recharge.
  </Card>

  <Card
    title="Piano"
    icon={
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" width="36" height="36" viewBox="0 0 992 992">
<path fill="#1B2D6B" d="M188.999817,581.353882 C180.503525,581.355713 172.503006,581.510742 164.512680,581.292480 C160.630356,581.186462 159.228958,582.479431 159.280136,586.444885 C159.458527,600.269470 159.181747,614.100769 159.428574,627.923279 C159.511841,632.586670 158.237000,634.514771 153.295380,634.319763 C144.978821,633.991577 136.637314,634.105957 128.311676,634.284607 C124.670601,634.362610 123.451157,633.194824 123.458519,629.406250 C123.583488,565.102722 123.545815,500.798889 123.606506,436.495239 C123.616554,425.851807 121.539520,426.858337 133.496002,426.846802 C154.153168,426.826843 174.810654,426.771271 195.467453,426.858337 C213.803452,426.935638 231.291702,430.308014 246.383789,441.527313 C264.626526,455.088776 273.708405,473.575684 275.399841,496.074677 C276.568359,511.618042 274.999329,526.700317 268.153687,540.805664 C257.131226,563.517212 238.417145,575.936096 213.903915,580.335815 C205.793304,581.791504 197.639206,581.155090 188.999817,581.353882 M159.336700,476.500122 C159.339172,500.464630 159.421448,524.429626 159.267044,548.393188 C159.240723,552.478088 160.452850,553.965454 164.629807,553.885620 C177.107101,553.647034 189.600082,554.031555 202.069534,553.631104 C217.482773,553.136108 228.607101,545.584045 234.704071,531.416748 C241.485855,515.658203 241.476517,499.265381 236.868393,483.058990 C232.499588,467.694305 222.353516,457.175537 206.078857,455.652100 C191.885452,454.323425 177.482620,455.253052 163.172791,455.129303 C160.422455,455.105530 159.281860,456.270508 159.327469,459.025177 C159.418381,464.515411 159.343842,470.008392 159.336700,476.500122z"/>
<path fill="#1B2D6B" d="M381.162720,557.806396 C367.540955,542.252441 362.209686,524.235474 362.395569,504.166992 C362.558746,486.548309 366.496094,470.173828 377.288879,455.954987 C390.438690,438.630859 408.294556,429.850006 429.693115,427.649475 C447.063385,425.863251 463.637299,428.545685 478.758179,437.369415 C501.570435,450.681427 512.886841,471.154541 514.318359,497.269684 C515.731934,523.057129 514.667603,548.872192 514.957764,574.673157 C515.032715,581.338623 514.903503,581.348511 508.303009,581.351379 C499.976593,581.354980 491.648315,581.239136 483.324646,581.387817 C479.875854,581.449402 478.491455,580.170837 478.667847,576.715088 C478.853790,573.072327 478.709473,569.412598 478.709473,564.253906 C464.597748,579.580505 447.336273,582.939331 428.876038,581.027344 C410.467590,579.120789 394.214172,571.948975 381.162720,557.806396 M467.824310,467.699860 C452.191010,448.293732 411.615265,449.704590 401.875397,481.248077 C396.489258,498.691681 396.622162,516.027405 404.086761,532.907837 C407.491974,540.608337 412.967529,546.839722 420.851379,549.994324 C435.367157,555.802551 450.222229,555.932556 464.497986,549.435425 C473.926575,545.144287 479.460388,537.726807 478.783051,526.470642 C478.283569,518.169800 478.778076,509.813568 478.656586,501.484558 C478.480377,489.402954 475.727509,478.080719 467.824310,467.699860z"/>
<path fill="#1B2D6B" d="M759.697998,574.471680 C735.237915,562.618286 721.926819,543.345032 718.545532,516.836060 C716.341736,499.559143 718.047424,482.833893 725.851013,467.255646 C738.150208,442.703156 758.777466,430.182007 785.824890,427.646637 C806.122986,425.743927 824.902710,429.872253 841.458496,442.098236 C858.062805,454.360046 866.655884,471.293732 869.358826,491.494507 C871.901489,510.497589 869.617798,528.747498 859.995300,545.537659 C848.665405,565.307068 831.070435,576.420349 808.898499,580.198181 C792.176880,583.047363 775.751099,581.568176 759.697998,574.471680 M758.036194,529.484985 C762.978027,542.244751 771.963806,550.484253 785.490723,553.043518 C801.107239,555.998291 817.589233,551.503662 825.861572,536.979797 C837.401184,516.719421 837.259583,495.413025 827.674133,474.794434 C820.390503,459.127014 806.139526,453.853241 789.389648,455.374817 C774.626953,456.715881 764.099915,464.432281 758.601990,478.090424 C751.896362,494.748840 752.312683,511.781860 758.036194,529.484985z"/>
<path fill="#1B2D6B" d="M692.333923,516.000122 C692.331543,536.158386 692.210632,555.817810 692.414551,575.473938 C692.461670,580.020142 691.113647,581.634094 686.476501,581.447083 C678.326538,581.118469 670.147888,581.166565 661.993164,581.427368 C657.828979,581.560608 656.566895,580.092712 656.593384,575.991089 C656.746033,552.335510 656.906494,528.675110 656.566833,505.023407 C656.394348,493.012604 654.984375,481.104309 647.692017,470.777191 C638.497864,457.756927 625.519836,453.829834 610.479736,455.448303 C597.201172,456.877197 587.626953,464.096313 581.752014,476.001404 C578.181885,483.235992 576.333191,490.990845 576.316650,499.109375 C576.265930,523.931702 576.233521,548.754089 576.202148,573.576416 C576.192322,581.356995 576.204163,581.359985 568.208374,581.357422 C560.378418,581.354919 552.545288,581.213867 544.719788,581.397095 C541.029175,581.483459 539.750305,580.097717 539.766113,576.448669 C539.871582,552.126221 539.510742,527.797607 539.934753,503.481995 C540.330322,480.797150 547.279785,460.590790 564.997437,445.234131 C577.932495,434.022766 593.133789,428.633240 610.132996,427.489075 C632.044373,426.014313 651.778625,431.302795 668.425842,445.910553 C683.915039,459.502167 690.998962,477.261810 692.241516,497.511139 C692.608215,503.486847 692.321106,509.502686 692.333923,516.000122z"/>
<path fill="#1B2D6B" d="M300.819702,544.000000 C300.824005,506.881927 300.823883,470.263824 300.838074,433.645752 C300.840668,426.972687 300.984833,426.841522 307.454010,426.829803 C315.609863,426.815002 323.767853,426.928741 331.920563,426.766357 C335.625519,426.692566 337.330902,427.769714 337.322418,431.841949 C337.222412,479.944611 337.224579,528.047546 337.303864,576.150269 C337.310089,579.917725 336.287537,581.552185 332.212250,581.434570 C323.397858,581.180237 314.569000,581.232910 305.750671,581.401062 C302.082245,581.471008 300.734802,580.120361 300.784119,576.456970 C300.927551,565.806396 300.825806,555.152588 300.819702,544.000000z"/>
<path fill="#1B2D6B" d="M326.986755,400.400330 C308.496979,405.322144 294.054504,393.735962 298.193176,373.717651 C300.427948,362.908112 311.139923,356.184204 322.043427,357.906952 C334.216339,359.830261 341.578766,368.945801 340.738495,381.030914 C340.107117,390.111572 336.215271,396.917053 326.986755,400.400330z"/>
<path fill="#1B2D6B" d="M882.846680,436.286682 C881.334961,434.225464 880.603149,437.468750 878.997681,436.175171 C878.472351,433.517212 878.340210,430.559021 879.097839,427.775909 C882.154785,426.852081 882.097351,429.831360 883.691467,430.430542 C885.183167,429.606384 885.715027,426.132324 887.577393,427.537079 C890.731995,429.916565 888.457092,433.499115 888.699646,436.790985 C886.423279,436.897766 884.774170,434.993011 882.846680,436.286682z"/>
<path fill="#1B2D6B" d="M875.111084,432.289001 C875.012146,434.129639 875.140015,435.643127 873.651794,436.896515 C870.164978,434.566742 873.645325,429.977051 869.496033,428.213043 C872.490234,426.589050 874.441345,426.483765 876.509094,427.808105 C876.033936,429.217438 875.583374,430.553894 875.111084,432.289001z"/>
</svg>
}
    href="/integrations/billing/piano"
  >
    Automate revenue recovery for your Piano subscriptions.
  </Card>

  <Card
    title="Recurly"
    icon={
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" width="36" height="36" viewBox="0 0 200 200">
<path fill="#FED606" d="M131.000000,201.000000 C87.333336,201.000000 44.166672,201.000000 1.000006,201.000000 C1.000004,134.333344 1.000004,67.666679 1.000002,1.000015 C67.666656,1.000010 134.333313,1.000010 200.999969,1.000005 C200.999985,67.666649 200.999985,134.333298 201.000000,200.999969 C177.833328,201.000000 154.666672,201.000000 131.000000,201.000000 M67.875458,30.227642 C53.787693,36.021767 44.454792,46.485584 39.124687,60.461739 C31.737713,79.831253 32.000504,99.583427 37.557827,119.322823 C43.662613,141.006790 56.044582,158.838272 71.312897,174.177551 C77.082329,168.609390 82.523186,163.358337 88.105537,157.970718 C87.131157,156.909073 86.132973,155.811615 85.124252,154.723938 C74.949226,143.752502 66.464096,131.681427 61.544781,117.421593 C56.009861,101.377281 54.904366,85.174431 61.003487,69.008354 C63.996078,61.076324 69.012970,54.791126 77.321594,51.840767 C90.386612,47.201431 101.051315,55.529285 98.901863,69.152786 C98.064728,74.458656 95.669899,79.595901 93.498413,84.598930 C88.035187,97.185951 84.425507,110.058914 87.034966,123.885498 C89.942375,139.290756 98.478172,150.472458 113.409637,155.753510 C128.102982,160.950348 141.656784,158.136215 153.424591,147.795822 C170.433212,132.850327 171.167694,102.792671 164.503220,84.278641 C157.326645,86.060913 150.125641,87.849258 143.119553,89.589195 C142.963120,90.380760 142.803360,90.717270 142.853058,91.019333 C143.068924,92.331596 143.374008,93.629036 143.596161,94.940422 C145.396378,105.568207 146.477707,116.173119 140.917236,126.127686 C137.739670,131.816315 132.769348,134.951660 126.166138,134.630798 C119.225121,134.293518 113.567215,130.896362 111.737083,124.241196 C110.249893,118.833076 109.867599,112.687820 110.788094,107.168457 C111.778893,101.227600 114.638412,95.540031 117.071709,89.910133 C122.304276,77.803619 124.979866,65.471138 120.707458,52.537636 C113.900970,31.932892 91.298416,22.219589 67.875458,30.227642z"/>
<path fill="#100F0B" d="M68.247482,30.108315 C91.298416,22.219589 113.900970,31.932892 120.707458,52.537636 C124.979866,65.471138 122.304276,77.803619 117.071709,89.910133 C114.638412,95.540031 111.778893,101.227600 110.788094,107.168457 C109.867599,112.687820 110.249893,118.833076 111.737083,124.241196 C113.567215,130.896362 119.225121,134.293518 126.166138,134.630798 C132.769348,134.951660 137.739670,131.816315 140.917236,126.127686 C146.477707,116.173119 145.396378,105.568207 143.596161,94.940422 C143.374008,93.629036 143.068924,92.331596 142.853058,91.019333 C142.803360,90.717270 142.963120,90.380760 143.119553,89.589195 C150.125641,87.849258 157.326645,86.060913 164.503220,84.278641 C171.167694,102.792671 170.433212,132.850327 153.424591,147.795822 C141.656784,158.136215 128.102982,160.950348 113.409637,155.753510 C98.478172,150.472458 89.942375,139.290756 87.034966,123.885498 C84.425507,110.058914 88.035187,97.185951 93.498413,84.598930 C95.669899,79.595901 98.064728,74.458656 98.901863,69.152786 C101.051315,55.529285 90.386612,47.201431 77.321594,51.840767 C69.012970,54.791126 63.996078,61.076324 61.003487,69.008354 C54.904366,85.174431 56.009861,101.377281 61.544781,117.421593 C66.464096,131.681427 74.949226,143.752502 85.124252,154.723938 C86.132973,155.811615 87.131157,156.909073 88.105537,157.970718 C82.523186,163.358337 77.082329,168.609390 71.312897,174.177551 C56.044582,158.838272 43.662613,141.006790 37.557827,119.322823 C32.000504,99.583427 31.737713,79.831253 39.124687,60.461739 C44.454792,46.485584 53.787693,36.021767 68.247482,30.108315z"/>
</svg>
}
    href="/integrations/billing/recurly"
  >
    Automate revenue recovery for your Recurly subscriptions.
  </Card>

  <Card title="Stripe Billing" icon={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32" width="26" height="26" fill="#6772e5"><path d="M111.328 15.602c0-4.97-2.415-8.9-7.013-8.9s-7.423 3.924-7.423 8.863c0 5.85 3.32 8.8 8.036 8.8 2.318 0 4.06-.528 5.377-1.26V19.22a10.246 10.246 0 0 1-4.764 1.075c-1.9 0-3.556-.67-3.774-2.943h9.497a39.64 39.64 0 0 0 .063-1.748zm-9.606-1.835c0-2.186 1.35-3.1 2.56-3.1s2.454.906 2.454 3.1zM89.4 6.712a5.434 5.434 0 0 0-3.801 1.509l-.254-1.208h-4.27v22.64l4.85-1.032v-5.488a5.434 5.434 0 0 0 3.444 1.265c3.472 0 6.64-2.792 6.64-8.957.003-5.66-3.206-8.73-6.614-8.73zM88.23 20.1a2.898 2.898 0 0 1-2.288-.906l-.03-7.2a2.928 2.928 0 0 1 2.315-.96c1.775 0 2.998 2 2.998 4.528.003 2.593-1.198 4.546-2.995 4.546zM79.25.57l-4.87 1.035v3.95l4.87-1.032z" fill-rule="evenodd"/><path d="M74.38 7.035h4.87V24.04h-4.87z"/><path d="M69.164 8.47l-.302-1.434h-4.196V24.04h4.848V12.5c1.147-1.5 3.082-1.208 3.698-1.017V7.038c-.646-.232-2.913-.658-4.048 1.43zm-9.73-5.646L54.698 3.83l-.02 15.562c0 2.87 2.158 4.993 5.038 4.993 1.585 0 2.756-.302 3.405-.643v-3.95c-.622.248-3.683 1.138-3.683-1.72v-6.9h3.683V7.035h-3.683zM46.3 11.97c0-.758.63-1.05 1.648-1.05a10.868 10.868 0 0 1 4.83 1.25V7.6a12.815 12.815 0 0 0-4.83-.888c-3.924 0-6.557 2.056-6.557 5.488 0 5.37 7.375 4.498 7.375 6.813 0 .906-.78 1.186-1.863 1.186-1.606 0-3.68-.664-5.307-1.55v4.63a13.461 13.461 0 0 0 5.307 1.117c4.033 0 6.813-1.992 6.813-5.485 0-5.796-7.417-4.76-7.417-6.943zM13.88 9.515c0-1.37 1.14-1.9 2.982-1.9A19.661 19.661 0 0 1 25.6 9.876v-8.27A23.184 23.184 0 0 0 16.862.001C9.762.001 5 3.72 5 9.93c0 9.716 13.342 8.138 13.342 12.326 0 1.638-1.4 2.146-3.37 2.146-2.905 0-6.657-1.202-9.6-2.802v8.378A24.353 24.353 0 0 0 14.973 32C22.27 32 27.3 28.395 27.3 22.077c0-10.486-13.42-8.613-13.42-12.56z" fill-rule="evenodd"/></svg>} href="/integrations/billing/stripe">
    Automate revenue recovery for your subscriptions managed by Stripe Billing.
  </Card>

  <Card
    title="Zuora"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="44" height="36" viewBox="0 0 542 468" fill="none"><path d="M75 234C75 105.318 179.318 1 308 0.99999C436.682 0.999979 541 105.318 541 234C541 362.682 436.682 467 308 467C179.318 467 75 362.682 75 234Z" stroke="#00D2B9" stroke-width="2"></path><path d="M234 -1.00607e-05C104.765 1.2374e-06 -1.2374e-06 104.765 1.00607e-05 234C2.13587e-05 363.235 104.765 468 234 468C363.235 468 468 363.235 468 234C468 104.765 363.235 -2.13587e-05 234 -1.00607e-05Z" fill="#103426"></path><path d="M328.269 275.335C322.068 269.229 313.768 265.723 304.967 265.723H259.555L332.538 207.075C337.284 203.33 339.193 196.986 337.046 191.357C334.923 185.728 329.676 181.984 323.499 181.984H271.672L297.359 161.091C302.105 157.108 304.013 151.002 301.866 145.373C299.72 139.745 294.497 136 288.319 136H173.24C164.463 136 156.139 139.506 149.962 145.612C143.522 151.956 140.207 160.161 140.207 168.842C140.207 177.524 143.522 185.728 149.724 191.834C156.139 197.916 164.463 201.446 173.24 201.446H308.282L228.407 265.723H169.687L209.159 233.12C213.19 229.59 213.905 223.484 210.328 219.262C206.774 215.279 200.597 214.588 196.304 218.094L145.192 260.095C140.446 264.078 138.776 270.183 140.923 275.812C143.069 281.441 148.293 285.185 154.47 285.185H203.912L177.533 306.532C172.787 310.3 170.879 316.62 173.002 322.249C175.148 327.878 180.372 331.646 186.573 331.646H304.967C313.768 331.646 322.068 328.355 328.269 322.249C334.685 315.929 338 307.7 338 299.042V298.565C338 289.645 334.446 281.441 328.269 275.335ZM240.523 181.745H173.24C169.687 181.745 166.347 180.577 163.748 177.977C161.363 175.401 159.932 172.11 159.932 168.604C159.932 165.098 161.124 161.806 163.748 159.23C166.347 156.869 169.687 155.462 173.24 155.462H273.103L240.523 181.745ZM318.276 299.042C318.276 302.549 317.083 305.84 314.459 308.416C311.86 310.753 308.521 312.16 304.967 312.16H202.028L235.299 285.424H304.967C308.521 285.424 311.86 286.592 314.459 289.168C316.845 291.768 318.276 295.036 318.276 298.565V299.042Z" fill="#00D2B9"></path></svg>
}
    href="/integrations/billing/zuora"
  >
    Automate revenue recovery for your Zuora subscriptions.
  </Card>

  <Card
    title="Custom"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 64 64">
<rect width="64" height="64" rx="12" fill="#7FF3D6" />
<path d="M40.236 42.982c-2.546 2.318-5.74 3.477-9.582 3.477-4.197 0-7.623-1.36-10.277-4.08-2.654-2.72-3.982-6.23-3.982-10.529 0-4.3 1.328-7.81 3.982-10.53 2.654-2.72 6.08-4.08 10.277-4.08 3.741 0 6.87 1.091 9.387 3.273l-2.85 4.284c-1.907-1.664-4.087-2.495-6.537-2.495-2.644 0-4.77.827-6.378 2.482-1.608 1.655-2.412 3.826-2.412 6.512 0 2.687.804 4.857 2.412 6.512 1.608 1.655 3.734 2.483 6.378 2.483 2.54 0 4.79-.876 6.754-2.63l2.829 5.32z" fill="#000000"/>
</svg>
}
    href="/integrations/billing/custom"
  >
    Integrate with a custom in-house billing system.
  </Card>
</CardGroup>

### Payment providers

We integrate with payment providers to gain more accurate insights into why payments fail and how to recover them.

<CardGroup>
  <Card
    title="Adyen"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 64 64"><path d="M51.128 0H1.073v16.1h32.894c2.145 0 3.575 1.788 3.575 3.575V47.9h-7.15c-2.145 0-3.575-1.788-3.575-3.575v-20.38H12.872A12.83 12.83 0 0 0 0 36.827V51.13C0 58.28 5.72 64 12.872 64H64V12.872C64 5.72 58.28 0 51.128 0z" fill="#35b454"/></svg>
    }
    href="/integrations/payments/adyen"
  >
    Sync Adyen payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Authorize.net"
    icon={
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 240 240" width="32" height="32">
<path d="M0 0 C79.2 0 158.4 0 240 0 C240 79.2 240 158.4 240 240 C160.8 240 81.6 240 0 240 C0 160.8 0 81.6 0 0 Z " fill="#202A43" transform="translate(0,0)"/>
<path d="M0 0 C1.48177982 1.1153469 2.93947889 2.26321329 4.375 3.4375 C5.35984375 4.20449219 6.3446875 4.97148438 7.359375 5.76171875 C17.23203514 14.04307223 24.36420272 28.10387524 25.61450195 40.88598633 C26.61313627 60.48626909 23.35762382 75.36187615 10.46875 90.70703125 C0.0074045 101.91867817 -14.78327763 108.73934857 -30.0703125 109.640625 C-46.654757 109.85189181 -62.60631585 105.12656745 -74.859375 93.40625 C-87.86415129 78.905349 -93.64192134 62.9815569 -92.97265625 43.55078125 C-91.95006174 27.76470762 -83.24535025 13.74368649 -71.625 3.4375 C-50.77883871 -13.38421108 -22.26602411 -15.04193629 0 0 Z " fill="#3773FB" transform="translate(132.625,55.5625)"/>
<path d="M0 0 C5.6567352 3.34361286 10.12160617 8.08345779 12.953125 14.00390625 C14.54594862 21.96802433 13.76674728 28.0837809 9.578125 35.12890625 C5.27241522 40.51104347 0.27901225 43.62928647 -6.546875 44.55078125 C-13.82853201 44.85418363 -18.94978221 44.0952843 -24.421875 39.12890625 C-29.79900802 33.73798571 -31.72832919 29.49498031 -31.859375 21.87890625 C-31.84077377 15.43125483 -31.05663101 10.80801399 -26.421875 6.12890625 C-18.86010642 -0.55016561 -10.02486548 -3.60571774 0 0 Z " fill="#FCC101" transform="translate(186.421875,149.87109375)"/>
</svg>
}
    href="/integrations/payments/authorize"
  >
    Sync Authorize.net payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Braintree"
    icon={
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
 viewBox="0 0 1000 1000" fill="#3f3d43" xml:space="preserve">
<path d="M60,990.5V847h119.6V148.4H60V4.9h473.5c215.3,0,349.2,95.7,349.2,267.9c0,109.9-67,177-153.1,210.5
C853.9,516.7,940,598.1,940,712.9c0.1,181.8-143.4,282.2-382.7,282.2H60V990.5z M342.2,148.5v267.9h177
c133.9,0,200.9-47.8,200.9-133.9c0-90.9-71.8-133.9-205.7-133.9L342.2,148.5z M342.2,847h200.9c157.9,0,234.4-47.8,234.4-143.5
S696.2,560,533.5,560H342.2L342.2,847z"/>
</svg>
}
    href="/integrations/payments/braintree"
  >
    Sync Braintree payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Checkout.com"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 400 400" xml:space="preserve">
<path d="M0 0 C132 0 264 0 400 0 C400 132 400 264 400 400 C268 400 136 400 0 400 C0 268 0 136 0 0 Z " fill="#0C1142" transform="translate(0,0)"/>
<path d="M0 0 C1.01515182 -0.00571014 2.03030365 -0.01142029 3.07621765 -0.01730347 C4.1993486 -0.01842133 5.32247955 -0.01953918 6.47964478 -0.02069092 C7.65515396 -0.02565582 8.83066315 -0.03062073 10.04179382 -0.03573608 C13.27530984 -0.04786955 16.50878965 -0.05530941 19.74232435 -0.05974674 C21.76101558 -0.06267408 23.77970108 -0.06677824 25.79838943 -0.07125092 C32.11004911 -0.08493208 38.42169575 -0.09459553 44.73336923 -0.09845281 C52.02727613 -0.10293439 59.32099571 -0.12048416 66.61484563 -0.1494534 C72.24714176 -0.17104926 77.87938511 -0.18115597 83.51172221 -0.18249393 C86.87821239 -0.18354353 90.24452664 -0.18948384 93.61097336 -0.20731354 C97.36552017 -0.22429191 101.11960684 -0.22251372 104.87417603 -0.21600342 C106.55279976 -0.22982559 106.55279976 -0.22982559 108.26533508 -0.243927 C109.28612656 -0.23835785 110.30691803 -0.2327887 111.35864258 -0.22705078 C112.24687399 -0.22851734 113.1351054 -0.2299839 114.05025291 -0.2314949 C116.79637391 0.22123555 117.67301751 0.91722359 119.30630493 3.14044189 C120.53860874 10.07884812 117.16063842 14.76452251 113.68130493 20.57794189 C113.09735962 21.58147705 112.51341431 22.58501221 111.91177368 23.61895752 C110.05678687 26.80091251 108.18199291 29.97065574 106.30630493 33.14044189 C104.54922928 36.14424127 102.79722348 39.15095867 101.0453186 42.15777588 C99.87811572 44.1597017 98.70898112 46.1605024 97.53799438 48.16021729 C93.04679617 55.83503397 88.6390324 63.55375659 84.30410767 71.31793213 C81.65968762 76.0400818 78.97254387 80.7273154 76.17192078 85.35827637 C74.74212646 87.72360866 73.32651662 90.09731187 71.9107666 92.47106934 C70.88923214 94.16898929 69.84612736 95.85387194 68.80264282 97.53839111 C68.18639038 98.57366943 67.57013794 99.60894775 66.93521118 100.67559814 C66.37906128 101.5870459 65.82291138 102.49849365 65.24990845 103.43756104 C63.98177877 107.07002253 64.74946792 108.68083577 66.30630493 112.14044189 C67.15424767 113.78466769 68.05463335 115.40275724 69.00161743 116.99200439 C69.8154187 118.37017334 69.8154187 118.37017334 70.6456604 119.77618408 C71.2349231 120.76263916 71.82418579 121.74909424 72.43130493 122.76544189 C73.70851357 124.92881586 74.98450747 127.09290734 76.25942993 129.25762939 C76.92523071 130.38652588 77.59103149 131.51542236 78.27700806 132.67852783 C81.63110741 138.38548483 84.90406456 144.13913427 88.18130493 149.89044189 C88.84800496 151.05925184 89.51475322 152.22803427 90.18154907 153.39678955 C91.53303313 155.76613876 92.88397745 158.13579461 94.23452759 160.50567627 C97.43259854 166.11715289 100.63460502 171.7263813 103.83786011 177.3348999 C104.83095143 179.07414729 105.82328197 180.81382902 106.81558228 182.55352783 C107.43255981 183.63408447 108.04953735 184.71464111 108.68521118 185.82794189 C109.28043579 186.87216309 109.8756604 187.91638428 110.48892212 188.99224854 C111.74230529 191.16344358 113.01503935 193.32354317 114.30337524 195.47418213 C114.93984985 196.53838379 115.57632446 197.60258545 116.23208618 198.69903564 C116.80741089 199.64834961 117.3827356 200.59766357 117.97549438 201.57574463 C119.84490834 205.17842186 120.14759314 207.18638733 119.30630493 211.14044189 C117.66912321 213.34660044 116.79191411 214.05767103 114.05863285 214.52355194 C113.1742979 214.52728065 112.28996294 214.53100937 111.37882996 214.53485107 C109.85414597 214.55187576 109.85414597 214.55187576 108.29866028 214.56924438 C106.62710625 214.56484848 106.62710625 214.56484848 104.92178345 214.56036377 C103.7475885 214.56883331 102.57339355 214.57730286 101.36361694 214.58602905 C98.14245206 214.60543754 94.92164215 214.61117484 91.7004292 214.60928154 C89.01150739 214.60916193 86.32263992 214.61772233 83.63373321 214.62605906 C77.29009727 214.64530006 70.94659292 214.64817446 64.60293579 214.64141846 C58.05836991 214.63477675 51.51436751 214.65764483 44.96991593 214.69473219 C39.3511227 214.72541861 33.73251084 214.73679042 28.11363548 214.73289537 C24.75766308 214.73082671 21.40212911 214.73632399 18.04623604 214.76078796 C14.30377286 214.78285521 10.56267836 214.77333602 6.82022095 214.75567627 C5.70787582 214.76893951 4.5955307 214.78220276 3.44947815 214.79586792 C-4.06151458 214.71327082 -4.06151458 214.71327082 -7.30780029 211.77175903 C-7.76514557 210.90342438 -8.22249084 210.03508972 -8.69369507 209.14044189 C-9.25081177 208.24406006 -9.80792847 207.34767822 -10.38192749 206.4241333 C-10.93211548 205.45653076 -11.48230347 204.48892822 -12.04916382 203.49200439 C-12.66670532 202.41225342 -13.28424683 201.33250244 -13.92050171 200.22003174 C-14.56753052 199.08001709 -15.21455933 197.94000244 -15.88119507 196.76544189 C-17.2357987 194.39440749 -18.5936007 192.02521068 -19.95150757 189.65606689 C-20.60151733 188.52104736 -21.2515271 187.38602783 -21.92123413 186.21661377 C-23.99185981 182.62296589 -26.10924984 179.06397778 -28.25619507 175.51544189 C-33.36206668 167.07630316 -38.3050552 158.54311654 -43.26791382 150.01934814 C-45.74634249 145.76308007 -48.23133398 141.51083889 -50.72958374 137.26617432 C-51.52960013 135.90664517 -52.32798105 134.5461521 -53.12460327 133.18463135 C-55.22073384 129.60831348 -57.35300752 126.05905632 -59.52963257 122.53106689 C-59.99595093 121.7652832 -60.46226929 120.99949951 -60.94271851 120.21051025 C-61.83355055 118.74891978 -62.73463307 117.2935075 -63.64779663 115.84576416 C-66.09150077 111.80990492 -67.6222296 108.96518017 -66.69369507 104.14044189 C-65.20598449 100.82424934 -63.38076007 97.75074558 -61.50619507 94.64044189 C-60.96374146 93.71682861 -60.42128784 92.79321533 -59.86239624 91.84161377 C-58.15132392 88.93404409 -56.42307387 86.03715139 -54.69369507 83.14044189 C-53.6611176 81.39122483 -52.6298297 79.64124577 -51.59994507 77.89044189 C-49.48785589 74.3032801 -47.36857583 70.72050427 -45.24447632 67.14044189 C-41.57136032 60.94316642 -37.92901041 54.72800511 -34.28915405 48.51116943 C-32.12589091 44.81694081 -29.96048832 41.12396593 -27.79522705 37.4309082 C-26.11832816 34.57078759 -24.44186751 31.7104146 -22.76644897 28.84942627 C-21.0157282 25.86150464 -19.26148941 22.87567839 -17.50619507 19.89044189 C-17.00217163 19.02870361 -16.49814819 18.16696533 -15.97885132 17.27911377 C-5.8116559 0.01947961 -5.8116559 0.01947961 0 0 Z " fill="#F8F8F9" transform="translate(155.69369506835938,92.85955810546875)"/>
<path d="M0 0 C0.66 0 1.32 0 2 0 C9.69859545 13.31522291 17.37706735 26.64131544 25 40 C30.41643161 49.49136774 35.85197548 58.97142435 41.3125 68.4375 C41.94091797 69.52740234 42.56933594 70.61730469 43.21679688 71.74023438 C46.33214788 77.22157252 46.33214788 77.22157252 49.75073242 82.51196289 C51 85 51 85 50.85424805 87.49291992 C49.91914207 90.23730495 48.76213414 92.58994208 47.33203125 95.11328125 C46.49768555 96.59538086 46.49768555 96.59538086 45.64648438 98.10742188 C45.04126953 99.16509766 44.43605469 100.22277344 43.8125 101.3125 C43.18537109 102.42044922 42.55824219 103.52839844 41.91210938 104.66992188 C37.10444718 113.13736289 32.20095207 121.54848443 27.27075195 129.94506836 C22.32719646 138.38276357 17.53565096 146.90110307 12.79296875 155.453125 C9.31522418 161.7114052 5.72579458 167.88600465 2 174 C-1.77788997 172.74070334 -2.06183096 171.64799092 -3.9765625 168.234375 C-4.55615723 167.21375977 -5.13575195 166.19314453 -5.73291016 165.14160156 C-6.3572998 164.02237305 -6.98168945 162.90314453 -7.625 161.75 C-8.62824441 159.97684411 -9.63494387 158.20567712 -10.64169312 156.43450928 C-11.34604972 155.19474794 -12.04933723 153.95437867 -12.75161743 152.71343994 C-16.6381523 145.85044188 -20.62776864 139.04891995 -24.625 132.25 C-25.34169267 131.02941263 -26.05832698 129.808791 -26.77490234 128.58813477 C-28.84807642 125.05766168 -30.92381868 121.52870548 -33 118 C-33.6384082 116.91444824 -34.27681641 115.82889648 -34.93457031 114.71044922 C-36.70477367 111.70184925 -38.47686213 108.69437125 -40.25 105.6875 C-41.01884521 104.38184082 -41.01884521 104.38184082 -41.80322266 103.04980469 C-42.28581543 102.23286133 -42.7684082 101.41591797 -43.265625 100.57421875 C-43.71744141 99.80255371 -44.16925781 99.03088867 -44.63476562 98.23583984 C-45.55571555 96.72760318 -46.52518708 95.24808826 -47.53710938 93.79931641 C-51.09929196 88.6495349 -51.09929196 88.6495349 -50.625 85.546875 C-50.08875 84.70640625 -49.5525 83.8659375 -49 83 C-48.24748598 81.65244249 -47.49779352 80.30330774 -46.75 78.953125 C-45.83689351 77.38334039 -44.92001414 75.8157462 -44 74.25 C-43.51088135 73.41162598 -43.0217627 72.57325195 -42.51782227 71.70947266 C-41.01570357 69.13738811 -39.50856818 66.56830616 -38 64 C-37.56026855 63.25008789 -37.12053711 62.50017578 -36.66748047 61.72753906 C-34.19549519 57.51247501 -31.71645219 53.30161312 -29.23388672 49.09277344 C-27.57109228 46.2725372 -25.91127545 43.45055459 -24.25170898 40.62841797 C-23.41944513 39.21322852 -22.58692693 37.79818861 -21.75415039 36.38330078 C-19.64191707 32.79436604 -17.53294886 29.20357599 -15.4296875 25.609375 C-12.96473024 21.39934431 -10.48581411 17.19774269 -8 13 C-7.60973633 12.33790527 -7.21947266 11.67581055 -6.81738281 10.99365234 C-5.71950001 9.13673371 -4.61160358 7.28622896 -3.5 5.4375 C-2.8709375 4.38433594 -2.241875 3.33117187 -1.59375 2.24609375 C-1.0678125 1.50488281 -0.541875 0.76367188 0 0 Z " fill="#0D1242" transform="translate(153,113)"/>
<path d="M0 0 C3.16876893 2.91432023 5.19702835 5.78370459 7.25 9.55859375 C8.15286743 11.20396118 8.15286743 11.20396118 9.07397461 12.88256836 C9.38769012 13.46166962 9.70140564 14.04077087 10.02462769 14.63742065 C11.35429581 17.09136371 12.6993539 19.53674971 14.04368591 21.98268127 C14.72619429 23.22465815 15.4079659 24.46704018 16.08900452 25.70982361 C18.98193635 30.98537654 21.94128942 36.22008618 24.9375 41.4375 C25.40124023 42.24662842 25.86498047 43.05575684 26.34277344 43.8894043 C27.89378005 46.59374361 29.44676056 49.29694249 31 52 C33.55099799 56.43991319 36.09987867 60.88102881 38.64553833 65.32400513 C39.73587313 67.22536513 40.82872002 69.12526638 41.92163086 71.02514648 C42.58851048 72.18856391 43.25526474 73.35205321 43.921875 74.515625 C44.51581055 75.54977539 45.10974609 76.58392578 45.72167969 77.64941406 C47 80 47 80 47 81 C16.31 81 -14.38 81 -46 81 C-39.17676768 67.35353535 -39.17676768 67.35353535 -35.5625 61.375 C-34.69294827 59.91469444 -33.82453586 58.45371009 -32.95703125 56.9921875 C-32.4873291 56.20166992 -32.01762695 55.41115234 -31.53369141 54.59667969 C-28.57279666 49.58361434 -25.66120722 44.54203308 -22.75 39.5 C-22.1202124 38.40937256 -21.4904248 37.31874512 -20.84155273 36.19506836 C-15.58148437 27.06007187 -10.41939696 17.87271382 -5.30371094 8.65625 C-4.75231445 7.66496094 -4.20091797 6.67367187 -3.6328125 5.65234375 C-3.14699707 4.77570068 -2.66118164 3.89905762 -2.16064453 2.99584961 C-1 1 -1 1 0 0 Z " fill="#0D1243" transform="translate(211,213)"/>
<path d="M0 0 C30.36 0 60.72 0 92 0 C87.70148061 8.59703879 83.45651945 16.90532597 78.5625 25.125 C77.33992374 27.19849866 76.11862405 29.27275042 74.8984375 31.34765625 C73.94855957 32.96244873 73.94855957 32.96244873 72.97949219 34.60986328 C69.85265269 39.96498085 66.78745396 45.35485587 63.72140503 50.74493408 C57.94037446 60.90776706 52.1053371 71.0279494 46 81 C43.3091852 77.76733025 41.06115192 74.57222803 39.0390625 70.88671875 C38.4925 69.89865234 37.9459375 68.91058594 37.3828125 67.89257812 C36.80273438 66.83490234 36.22265625 65.77722656 35.625 64.6875 C30.84926214 56.06408259 25.99605343 47.49767582 21 39 C15.96650317 30.41685716 11.00783979 21.79453187 6.125 13.125 C5.51140625 12.0421875 4.8978125 10.959375 4.265625 9.84375 C3.70617187 8.84601563 3.14671875 7.84828125 2.5703125 6.8203125 C2.07289551 5.93617676 1.57547852 5.05204102 1.06298828 4.14111328 C0 2 0 2 0 0 Z " fill="#0D1242" transform="translate(166,106)"/>
</svg>
}
    href="/integrations/payments/checkout"
  >
    Sync Checkout.com payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Cybersource"
    icon={<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 240.1 276.2" xml:space="preserve">
<g id="Layer_2_1_">
<g id="Layer_1-2">
<path d="M10.4,191c-3.3-8,0.5-17.2,8.5-20.6c8-3.3,17.2,0.5,20.6,8.5c3.3,8-0.5,17.2-8.5,20.6c-1.9,0.8-4,1.2-6,1.2
		C18.6,200.7,12.9,196.9,10.4,191" fill="#FFC300">
</path>
<path d="M170.1,257.3c-3.3-8,0.5-17.2,8.6-20.5c8-3.3,17.2,0.5,20.5,8.6c3.3,8-0.5,17.2-8.6,20.5
		c-1.9,0.8-3.9,1.2-6,1.2C178.3,267,172.5,263.2,170.1,257.3" fill="#202A44">
</path>
<path d="M137.9,276.2c-36.6,0.1-71.7-14.4-97.5-40.4c-6.1-6.1-6.1-16.1,0-22.2s16.1-6.1,22.2,0
		c19.9,20,47,31.3,75.3,31.2c8.7,0,15.7,7,15.7,15.7S146.6,276.2,137.9,276.2" fill="#202A44">
</path>
<path d="M213.2,235.8c-6.2-6.1-6.2-16.1,0-22.3c6.1-6.2,16.1-6.2,22.3,0s6.2,16.1,0,22.3c-3,3-7,4.6-11.2,4.6
		C220.2,240.4,216.2,238.8,213.2,235.8" fill="#202A44">
</path>
<path d="M10.4,85.2c-3.3,8,0.5,17.2,8.5,20.6c8,3.3,17.2-0.5,20.6-8.5c3.3-8-0.5-17.2-8.5-20.6c-1.9-0.8-4-1.2-6-1.2
		C18.6,75.5,12.8,79.4,10.4,85.2" fill="#FFC300">
</path>
<path d="M170.1,19c-3.3,8,0.5,17.2,8.6,20.5c8,3.3,17.2-0.5,20.5-8.6c3.3-8-0.5-17.2-8.6-20.5c-1.9-0.8-3.9-1.2-6-1.2
		C178.3,9.2,172.5,13.1,170.1,19" fill="#3874FD">
</path>
<path d="M137.9,0c-36.6-0.1-71.7,14.4-97.5,40.4c-6.1,6.2-6,16.1,0.2,22.2c6.1,6,16,6,22.1,0
		c19.9-20,47-31.3,75.3-31.2c8.7,0,15.7-7,15.7-15.7C153.7,7,146.6,0,137.9,0C138,0,138,0,137.9,0" fill="#3874FD">
</path>
<path d="M213.2,40.4c-6.2,6.1-6.2,16.1,0,22.3c6.1,6.2,16.1,6.2,22.3,0c6.2-6.1,6.2-16.1,0-22.3c-3-3-7-4.6-11.2-4.6
		C220.2,35.8,216.2,37.5,213.2,40.4" fill="#3874FD">
</path>
<path d="M0,138.1L0,138.1z M15.7,122.4C7,122.4,0,129.5,0,138.2c0,8.7,7.1,15.7,15.8,15.7c8.7,0,15.7-7.1,15.7-15.8
		C31.4,129.4,24.4,122.4,15.7,122.4C15.7,122.4,15.7,122.4,15.7,122.4z" fill="#FFC300">
</path>
</g>
</g>
</svg>}
    href="/integrations/payments/cybersource"
  >
    Sync Cybersource payments data t oget more accurate insights and recover revenue.
  </Card>

  <Card
    title="Pay.com"
    icon={
<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 64 64" fill="#0053EF">
<path d="M0 0 L20.5 0 L49.2 36.8 L48.2 39.2 L28.8 63.8 L0.8 63.8 L1 56 L40 39.8 L41.2 38.8 L41.5 36.8 L40 35.2 L0 22.8 Z"/>
<path d="M63.8 21.8 L63.8 52.8 L52.2 38 L52.5 36 Z"/>
</svg>
}
    href="/integrations/payments/paycom"
  >
    Sync Pay.com payments data to get more accurate insights and recover revenue.
  </Card>

  <Card title="Stripe" icon={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32" width="26" height="26" fill="#6772e5"><path d="M111.328 15.602c0-4.97-2.415-8.9-7.013-8.9s-7.423 3.924-7.423 8.863c0 5.85 3.32 8.8 8.036 8.8 2.318 0 4.06-.528 5.377-1.26V19.22a10.246 10.246 0 0 1-4.764 1.075c-1.9 0-3.556-.67-3.774-2.943h9.497a39.64 39.64 0 0 0 .063-1.748zm-9.606-1.835c0-2.186 1.35-3.1 2.56-3.1s2.454.906 2.454 3.1zM89.4 6.712a5.434 5.434 0 0 0-3.801 1.509l-.254-1.208h-4.27v22.64l4.85-1.032v-5.488a5.434 5.434 0 0 0 3.444 1.265c3.472 0 6.64-2.792 6.64-8.957.003-5.66-3.206-8.73-6.614-8.73zM88.23 20.1a2.898 2.898 0 0 1-2.288-.906l-.03-7.2a2.928 2.928 0 0 1 2.315-.96c1.775 0 2.998 2 2.998 4.528.003 2.593-1.198 4.546-2.995 4.546zM79.25.57l-4.87 1.035v3.95l4.87-1.032z" fill-rule="evenodd"/><path d="M74.38 7.035h4.87V24.04h-4.87z"/><path d="M69.164 8.47l-.302-1.434h-4.196V24.04h4.848V12.5c1.147-1.5 3.082-1.208 3.698-1.017V7.038c-.646-.232-2.913-.658-4.048 1.43zm-9.73-5.646L54.698 3.83l-.02 15.562c0 2.87 2.158 4.993 5.038 4.993 1.585 0 2.756-.302 3.405-.643v-3.95c-.622.248-3.683 1.138-3.683-1.72v-6.9h3.683V7.035h-3.683zM46.3 11.97c0-.758.63-1.05 1.648-1.05a10.868 10.868 0 0 1 4.83 1.25V7.6a12.815 12.815 0 0 0-4.83-.888c-3.924 0-6.557 2.056-6.557 5.488 0 5.37 7.375 4.498 7.375 6.813 0 .906-.78 1.186-1.863 1.186-1.606 0-3.68-.664-5.307-1.55v4.63a13.461 13.461 0 0 0 5.307 1.117c4.033 0 6.813-1.992 6.813-5.485 0-5.796-7.417-4.76-7.417-6.943zM13.88 9.515c0-1.37 1.14-1.9 2.982-1.9A19.661 19.661 0 0 1 25.6 9.876v-8.27A23.184 23.184 0 0 0 16.862.001C9.762.001 5 3.72 5 9.93c0 9.716 13.342 8.138 13.342 12.326 0 1.638-1.4 2.146-3.37 2.146-2.905 0-6.657-1.202-9.6-2.802v8.378A24.353 24.353 0 0 0 14.973 32C22.27 32 27.3 28.395 27.3 22.077c0-10.486-13.42-8.613-13.42-12.56z" fill-rule="evenodd"/></svg>} href="/integrations/payments/stripe">
    Sync Stripe payments data to get more accurate insights and recover revenue.
  </Card>

  <Card
    title="Worldpay"
    icon={<svg xmlns="http://www.w3.org/2000/svg" height="80" width="120" id="svg8195" version="1.1"
 viewBox="0 0 48 32">
<g transform="translate(79.6546 -150.1857)" id="layer1">
    <g transform="translate(-79.6477 150.1857) scale(.17764)" id="g8241" stroke-width="1.4895">
        <path class="st1"
              d="M60.5 63.1c-.6.9-1.3 1.8-2.1 2.7-1.7 1.9-3.7 3.7-5.9 5.2-2.8 1.9-5.7 3.4-8.7 4.5-2.6.9-4.9 1.4-6.9 1.5h-.7c-1 0-1.7-.1-2.1-.4l-.2-.1-.2-.2v-.1c0-.1 0-.3.1-.5.2-.5.5-.9.9-1.4.1-.1.3-.3.4-.5 1.5-.4 3-.9 4.7-1.4 1.5.3 3.1.4 4.5.3 1.8-.2 3.5-.7 5-1.5 1.8-1 3.4-2.3 4.7-3.9.8-1.1 1.5-2.2 2-3.5 2.7-2.1 5-4.3 6.8-6.5l.9-1.2c-.7 2.4-1.7 4.8-3.2 7m-10.3 4.5c.6-.3 1.1-.7 1.7-1-.8 1-1.8 1.9-2.8 2.6-1.4.9-2.9 1.6-4.4 1.9-.7.1-1.3.2-2 .3 2.5-1.1 5.1-2.4 7.5-3.8m18.3-25.1c0-2.9-.7-5.7-2.1-8.3-1.2-2.3-3-4.5-5.2-6.5-.5-2.7-1.9-5.2-4-7.5-1.7-1.8-3.8-3.4-6.4-4.8-2-1.1-4.2-2-6.5-2.7-1.9-.6-3.8-.9-5.6-1.1-1.7-.2-3.1-.1-4.4.1-1.3.3-2.5.7-3.6 1.3l-.2.1c-1.5-.2-3-.2-4.4-.1h-.4c-1.4.1-4.3.5-4.1 1.9 0 0 0 .8 1.8 1.4l2.5-1.5c-.2 0-.4-.1-.6-.1.8-.1 1.6-.2 2.2-.2h.5c-.2.1-.3.2-.5.3l-.8.5c-1.5.9-2 1.3-3.6 2.2-1 .6-1.9 1.2-2.9 1.7-1.9 1-3.8 2-5.8 3-1.6.7-3.2 1.5-5.3 2.4l-.2.1c-.5.2-1 .4-1.4.6h-.1c-.5.2-1.1.5-1.4 1.1l-.1.4v.4c0 .1.1.2.1.2l.3.3.3.2h.1c.3.1.7.1 1.1.1h1.8c.7 0 1.4-.1 2-.1 3.3-.1 6.3-.1 9.2 0 2.8.1 5.6.4 8.4.7l4.2.6c.9-.8 1.6-1.4 2.1-2-2.9-.6-5.8-1-8.6-1.3-2.9-.3-6-.5-9.1-.5h-1.1c-1.5 0-3.1 0-4.6.1 1.5-.7 2.8-1.4 4.1-2 1.9-1 3.8-2.1 5.7-3.3 1.4-.9 2.9-1.9 4.6-3.1l.3-.2c2 .4 4.4.8 6.8 1.3l5.1 1.2c-.7-1.7-2.8-2.7-4-3.2-1.7-.3-3.5-.7-5.6-1 .5-.4 1-.7 1.5-.9 1.7.2 3.1.5 4.4 1 1 .4 1.8.8 2.5 1.3.1.1.3.2.4.3 1.2 1 1.9 2.3 1.9 3.6.1 1.1-.2 2.3-.8 3.5-.3.7-.8 1.4-1.3 2.1-.1.2-1 1.5-3 3.2-1.9 1.8-4.2 3.4-7 5.1-1 .6-1.9 1.1-2.9 1.6-1.2.6-2.4 1.2-3.4 1.6-1.6.7-4.3 1.9-7.7 2.9-1.8.5-3.5 1-5.2 1.3-1.3.3-2.9.5-4.5.6 1.8-.8 3.8-1.3 5.9-1.6 4-.9 7.4-2.2 9.6-3.2-2.1 0-4.2.1-6.4.3-3.6.4-6.5.9-9.1 1.8-1.5.5-3.5 1.3-4 2.6-.1.7 0 1.2.2 1.7.4.8 1.2 1.2 2.5 1.4 1 .1 2.1.1 3.6-.1 2.7-.3 5.6-.9 8.9-2 2.9-.9 5.5-2 8-3.1 2.8.1 5.6.4 8.3.9 2.9.5 5.4 1.2 7.8 2.1 2.7 1 5 2.1 6.9 3.4.7-.5 1.3-1 1.8-1.4-.1 0-.1-.1-.2-.1-2.4-1.6-5.2-3-8.2-4.1-2.5-.9-5.2-1.6-8.2-2.2-1.4-.3-2.8-.5-4.3-.6 2.4-1.3 4.5-2.6 6.4-4.1 1.7-1.3 3.1-2.6 4.4-3.9 3.4.9 6.3 1.8 8.9 2.9 3.1 1.3 5.8 2.8 8.1 4.5l.2.1c.5-.7.9-1.5 1.2-2.1-2.1-1.5-4.4-2.8-6.9-4-2.8-1.3-5.9-2.4-9.3-3.3-.1 0-.2-.1-.4-.1 1.5-2.1 2.4-4.1 2.6-6 .1-.6.1-1.1 0-1.7 2.9.9 5.7 2 8.3 3.2 2.6 1.2 4.8 2.5 6.7 4l.1.1c-.5-2.1-1.6-3.7-2.2-4.4-1.2-.7-2.5-1.3-3.9-2-2.4-1.1-5.1-2.1-8-3-.6-.2-1.3-.4-1.9-.5h-.1c-.9-1.6-2.3-2.5-3.4-3.1-1.2-.6-2.6-1.1-4.2-1.4.7-.1 1.3-.2 2-.2h.2c.6 0 1.3 0 2 .1.2 0 .3 0 .5.1 1.7.2 3.4.6 5.3 1.2 2.2.7 4.3 1.6 6.1 2.7 2.3 1.3 4.2 2.8 5.7 4.5.5.6 1 1.2 1.4 1.8.1.1.2.2.2.4 0 0 0 .1.1.1.7 1.2 1.4 2.8 1.5 4.7.2 2-.2 4-.8 5.6 0 .1-.8 2.3-2.2 4.3-1.4 2.1-3.3 4.2-5.6 6.2-.5.5-2 1.8-4.1 3.2-2 1.4-4.1 2.7-6.3 3.9-1.7 1-3.5 1.8-5.7 2.8-.9.4-2.2.9-3.7 1.4-2.4.9-4.8 1.6-7.2 2.2-3.5.8-6.6 1.3-9.6 1.5-1.2.1-2.3.1-3.4 0-1.6-.1-3.3-.3-4.3-1.2l-.2-.2v-.2c.2-.6.7-1 1.2-1.4.7-.5 1.5-.9 2.5-1.3 2.3-.9 4.9-1.5 7.9-1.8 2.8-.2 5.7-.1 8.4.3 1.4.2 2.8.6 4.2 1 1-.3 2-.7 2.7-1-1.7-.7-3.6-1.3-5.6-1.8-2.8-.6-5.8-.8-8.8-.7-3.1.1-6 .6-8.6 1.4-2.1.7-4.4 1.6-5.8 3.4-.6.8-.9 1.7-.7 2.7.2 1.2 1.2 2 1.7 2.3 1.3.8 2.9 1.2 4 1.3 1.2.2 2.5.3 3.9.3h.7c2.9-.1 6-.5 9.7-1.3 3.1-.7 6.3-1.6 9.6-2.9.9-.4 1.9-.7 2.8-1.1 1.5 1 2.6 2.1 3.3 3.3.7 1.2 1 2.3 1 3.5 0 1.1-.3 2.2-.9 3.2-.1.3-.3.5-.5.8.7-.2 1.4-.5 2.1-.8l.3-.6c.5-1.3.7-2.7.5-4-.2-1.5-.9-3-2-4.3-.5-.7-1.2-1.3-1.9-1.9 3.2-1.5 6.1-3.1 8.7-4.8 1.3-.9 2.6-1.8 3.8-2.7 2 1.9 3.5 4 4.2 6.3.4 1.2.6 2.4.6 3.7.8-.7 1.5-1.3 2-1.8-.2-1.8-.8-3.5-1.8-5.2-.8-1.5-2-2.9-3.4-4.3 2.7-2.3 4.9-4.7 6.5-7.2.1-.1.2-.3.3-.4 2 2 3.5 4.2 4.5 6.4v.1c.2.4.3.9.5 1.3.7-1.6 1-3 1.1-3.9-.8-1.6-1.9-3.1-3.1-4.4-.5-.6-1.1-1.1-1.7-1.7 1.1-2.3 1.8-4.5 2-6.6.5.6 1 1.2 1.4 1.8 1.5 2.3 2.5 4.7 2.7 7 .1.9.1 1.7.1 2.6 0 .1 0 1-.3 2.4 0 .2-.1.5-.2.7-.3 1.1-.8 2.5-1.5 4-.1.1-.1.3-.2.4-.1.1-.1.3-.2.4-1.3 2.4-3.1 4.8-5.4 7-.3.3-.6.6-1 .9-.8.8-2 1.8-3.1 2.6-2.2 1.7-4.6 3.2-7.1 4.5-1.9 1-3.9 2-6 2.8-2.2.9-4.3 1.6-5.9 2-3 .8-5.9 1.4-8.7 1.7-2.6.2-4.6.2-6.5-.1-1.2-.2-2.1-.5-2.9-.9-.2-.1-.4-.3-.5-.4 0-.1-.1-.1-.1-.2v-.2c.4-1 1.7-1.5 3-1.9 1.2-.4 2.7-.6 4.3-.6h.2c1.5 0 3 .2 4.6.6 1.5.3 3 .8 4.3 1.3.1 0 .1.1.2.1.6-.1 1.3-.3 2.2-.6-.1 0-.2-.1-.4-.1-.6-.2-1.2-.5-1.8-.7-1.7-.7-3.1-1.1-4.5-1.5-1.7-.4-3.4-.7-5-.7-1.7-.1-3.4.1-5 .5-1.7.4-2.9 1.1-3.8 1.9-.6.6-.9 1.4-.9 2.2 0 .8.4 1.6 1.1 2.2 1.8 1.6 4.7 2 7 2.1 2.9.2 6-.1 9.4-.7.4-.1.9-.2 1.3-.3-.3.5-.6 1-.7 1.6-.1.9.4 1.8 1.4 2.3.9.5 2.1.8 3.7.8h.9c2.5-.1 5.1-.7 8-1.8 2.9-1 5.6-2.5 8.2-4.2 2.3-1.6 4.5-3.5 6.3-5.6 1.9-2.2 3.5-4.6 4.5-7.1 1.1-2.5 1.6-5.3 1.5-8 0-.4 0-.8-.1-1.2 1.8-2.9 2.5-5.9 2.5-8.8"
              id="path8239" fill="#e30613" stroke-width="1.4895"/>
    </g>
</g>
</svg>}
    href="/integrations/payments/worldpay"
  >
    >

    Sync Worldpay payments data to get more accurate insights and recover revenue.
  </Card>
</CardGroup>

### Missing an integration?

We're continuously expanding our integrations. If you have a specific integration in mind, please let us know by [contacting us](https://www.slickerhq.com/contact).


# Adyen
Source: https://docs.slickerhq.com/integrations/payments/adyen

Learn how to connect Adyen to Slicker

### Prerequisites

Slicker integrates with Adyen via their reporting features to sync payment data and provide insights into failed transactions. The setup is more complex than other integrations, but provides the most accurate payment data for revenue recovery.

To set up this integration, you need:

* An Adyen account with access to reports and API credentials
* Admin or Merchant admin permissions (which includes the required roles: `Merchant Report`, `Manage API credentials`, and `Merchant technical integrator`)
* Access to your Adyen Customer Area

### Create API credentials

Slicker needs to read reports from Adyen. Create a Report service user by following these steps:

1. Log in to your [Adyen Customer Area](https://ca-live.adyen.com/).

2. Follow the [official Adyen documentation](https://docs.adyen.com/reporting/automatically-get-reports/#create-api-credential) to create a Report service user API credential.

3. Copy the **Server Settings API Key** - you'll need this for the Slicker integration.

<Note>
  Keep your API key secure. Slicker only needs read permissions to sync payment data and analyze failed transactions.
</Note>

### Schedule automatic report generation

We use Adyen's [Received payment details report](https://docs.adyen.com/reporting/received-payment-details-report/) to sync payments data.

1. Follow the [official Adyen documentation](https://docs.adyen.com/reporting/automatically-get-reports/#automate-generating-reports) to set up automatic report generation.

2. Make sure to select the **Received payment details report** as the report type.

3. When prompted to select the columns for the report, select **all columns**.

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).

2. Select **Adyen** from the list of payment integrations.

3. Provide the following information:
   * **Integration name**: A descriptive name to help you identify this integration
   * **Description**: Optional description for additional context
   * **API Key**: The Report service user API key you copied from Adyen

4. Copy the **Endpoint URL**, **Basic Auth Username**, and **Basic Auth Password** from the Slicker integration page - you'll need these for webhook configuration.

### Configure webhooks

For real-time report notifications, configure webhooks:

1. In your Adyen Customer Area, follow the [official Adyen documentation](https://docs.adyen.com/development-resources/webhooks/) to create a webhook.

2. Configure the webhook with the credentials from the Slicker integration page:
   * **Webhook URL**: Use the Endpoint URL from Slicker
   * **Authentication**: Use Basic Auth with the username and password from Slicker

3. Copy the **Webhook HMAC Key** from Adyen and paste it into the Slicker integration page.

### Save the integration

1. Click **Submit** to create the integration.

### What data does Slicker sync?

Once connected, Slicker will sync the following data from Adyen:

* **Payment transactions**: Successful and failed payments with detailed information
* **Decline reasons**: Comprehensive acquirer responses and failure details
* **Customer data**: Shopper information needed for recovery campaigns
* **Risk scoring**: Risk assessment data to optimize recovery strategies
* **Payment methods**: Card types, issuer information, and payment method details

### Troubleshooting

**Connection failed error:**

* Verify your API key is correct and has not expired
* Ensure the key has sufficient permissions to read report data
* Check that your Adyen account is active and in good standing

**Missing transaction data:**

* Slicker syncs data from reports as they are generated
* New transactions typically appear after the next scheduled report
* Ensure automatic report generation is properly configured

**Webhook issues:**

* Verify the webhook URL and authentication credentials are correct
* Check that the HMAC key matches between Adyen and Slicker
* Ensure webhooks are enabled for your Adyen account

<Frame>
  <img alt="Failed integration creation message" />
</Frame>

For additional help, contact [Slicker support](https://www.slickerhq.com/contact) or check our [FAQ](/essentials/faq).


# Authorize.net
Source: https://docs.slickerhq.com/integrations/payments/authorize

Learn how to connect Authorize.net to Slicker

### Prerequisites

Slicker integrates with Authorize.net via their API. Credentials for this API are created via Authorize.net's Merchant Interface.

### Create credentials

Follow the [official Authorize.net documentation for creating a Transaction Key](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001271).
In the end you will need to have the following:

* Your API ID/Merchant name
* Transaction Key

<Note>Make sure you follow the steps for creating a Transaction Key, not Signature Key</Note>

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Authorize.net` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the merchant name and transaction key generated from the Merchant Interface.
5. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Authorize.net using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the provided credentials, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Braintree
Source: https://docs.slickerhq.com/integrations/payments/braintree

Learn how to connect Braintree to Slicker

### Prerequisites

Slicker integrates with Braintree via their API. Credentials for this API are created via Braintree's Control Panel.

### Create credentials

Follow the [official Braintree documentation for creating API keys](https://developer.paypal.com/braintree/articles/control-panel/important-gateway-credentials#api-keys).
In the end you will need to have the following:

* Public Key
* Private Key
* Merchant ID

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Braintree` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enable `Sandbox mode` to connect a Braintree sandbox account, or leave it off for production.
5. Enter the merchant ID and the public/private key pair from the selected environment's Control Panel.
6. Click the `Submit` button to create the integration.

The selected environment is used for credential validation and payment syncing, and is shown on the integration details page.
For API integrations, set the `integration.config.braintreeConfig.sandbox` query parameter to `true` for sandbox or `false` for production.
Omitting this field defaults to production when creating an integration and preserves the existing environment when updating one.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Braintree using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check that the provided credentials match the selected environment, make sure they have the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Checkout.com
Source: https://docs.slickerhq.com/integrations/payments/checkout

Learn how to connect Checkout.com to Slicker

### Prerequisites

Slicker integrates with Checkout.com via API keys to sync payment data and provide insights into failed transactions. To set up this integration, you need:

* A Checkout.com account with access to API keys
* Admin or Developer permissions to generate API credentials
* Access to your Checkout.com dashboard

### Create API credentials

1. Log in to your [Checkout.com dashboard](https://dashboard.checkout.com/).

2. Navigate to **Settings** → **Developers** → **Keys**.

3. Generate a new **Secret API Key** if you don't already have one:
   * Click **Create new key**
   * Give it a descriptive name like `Slicker Integration`
   * Configure the scopes to include the Payments scope, along with `reports` and `reports:view` permissions

4. Copy the **Secret API Key** - you'll need this for the Slicker integration.

<Note>
  Keep your Secret API Key secure. Slicker only needs read permissions to sync payment data and analyze failed transactions.
</Note>

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).

2. Select **Checkout.com** from the list of payment integrations.

3. Provide the following information:
   * **Integration name**: A descriptive name to help you identify this integration
   * **Description**: Optional description for additional context
   * **Secret API Key**: The key you copied from your Checkout.com dashboard

### Configure webhooks

For real-time payment updates, configure webhooks:

1. Copy the **Endpoint URL** from the Slicker integration page.

2. In your Checkout.com dashboard, go to **Settings** → **Channels** → **Webhooks**.

3. Click **Create webhook** and configure:
   * **Endpoint URL**: Paste the URL you copied from Slicker
   * **Events**: Select the **Gateway** and **Reports** categories

4. Copy the **Authorization Header Key** and **Signature Key** from Checkout.com into the Slicker integration page.

5. Save the webhook configuration.

### Save the integration

1. Click **Submit** to create the integration.

### What data does Slicker sync?

Once connected, Slicker will sync the following data from Checkout.com:

* **Payment transactions**: Successful and failed payments
* **Decline reasons**: Detailed information about why payments failed
* **Customer data**: Information needed for recovery campaigns
* **Payment methods**: Card types and other payment method details

### Troubleshooting

**Connection failed error:**

* Verify your Secret API Key is correct and has not expired
* Ensure the key has sufficient permissions to read transaction data
* Check that your Checkout.com account is active and in good standing

**Missing transaction data:**

* Slicker syncs data from the past 90 days on initial connection
* New transactions typically appear within 15 minutes
* Contact support if you're missing recent transactions

<Frame>
  <img alt="Failed integration creation message" />
</Frame>

For additional help, contact [Slicker support](https://www.slickerhq.com/contact) or check our [FAQ](/essentials/faq).


# Cybersource
Source: https://docs.slickerhq.com/integrations/payments/cybersource

Learn how to connect Cybersource to Slicker

### Prerequisites

Slicker integrates with Cybersource via their REST API. Credentials for this API are created via Cybersource's Business Center.

### Create credentials

Follow the [official Cybersource documentation for creating a Shared Secret Key](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-shared-secret-intro/restgs-shared-secret-create-intro/restgs-shared-secret-create-task.html).
In the end you will need to have the following:

* Merchant ID
* Key ID
* Secret Key

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Cybersource` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the Merchant ID, Key ID, and Secret Key generated from the Business Center.
5. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Cybersource using the provided credentials.
If the connection fails, you will see an error message like the one below.
Please double-check the provided credentials, make sure they have the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Pay.com
Source: https://docs.slickerhq.com/integrations/payments/paycom

Learn how to connect Pay.com to Slicker

### Prerequisites

Slicker integrates with Pay.com via an API key to sync payment data and provide insights into failed transactions. To set up this integration, you need:

* A Pay.com account
* Access to your Pay.com Dashboard, where API keys are managed

### Create an API key

1. Log in to your [Pay.com Dashboard](https://pay.com/).

2. Navigate to your API keys and create a new API key.

3. Under **Whitelist IP Addresses**, add all of Slicker's production IP addresses:
   * `13.135.80.39`
   * `13.43.168.68`
   * `13.43.107.33`

4. Under **API's Endpoint**, select **Read** for every endpoint. Slicker does not require write access.

5. Create the key and copy its secret value. Production keys are prefixed with `live_`.

<Note>
  Keep your API key secure. Slicker only needs read permissions to sync payment data and analyze failed transactions.
</Note>

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).

2. Select **Pay.com** from the list of payment integrations.

3. Provide the following information:
   * **Integration name**: A descriptive name to help you identify this integration
   * **Description**: Optional description for additional context
   * **API Key**: The key you copied from your Pay.com Dashboard
   * **Business Entity**: Optional. Leave empty if you have only a single business unit.

4. Click **Submit** to create the integration.

### What data does Slicker sync?

Once connected, Slicker will sync the following data from Pay.com:

* **Payment transactions**: Successful and failed payments
* **Decline reasons**: Detailed information about why payments failed
* **Payment methods**: Card types and other payment method details

### Troubleshooting

**Connection failed error:**

* Verify your API key is correct and has not been revoked
* Ensure all three Slicker production IP addresses are included under **Whitelist IP Addresses**
* Ensure **Read** is selected for every endpoint under **API's Endpoint**
* Check that your Pay.com account is active and in good standing

**Missing transaction data:**

* Slicker syncs your transaction history when the integration is first created, which can take a little while to complete
* New transactions typically appear shortly after they are processed by Pay.com

<Frame>
  <img alt="Failed integration creation message" />
</Frame>

For additional help, contact [Slicker support](https://www.slickerhq.com/contact) or check our [FAQ](/essentials/faq).


# Stripe
Source: https://docs.slickerhq.com/integrations/payments/stripe

Learn how to connect Stripe to Slicker

<Note> If you have already created a [Stripe Billing integration](/integrations/billing/stripe) for the same Stripe account you don't have to add another one. </Note>

### Prerequisites

Slicker integrates with Stripe via an API key. Creating a Stripe API key requires a Stripe user enough permissions to do so.
Stipe user roles that have this permission include `Administrator`, `Super Administrator`, and `Developer`.

### (Option 1: Stripe Marketplace App) Integerate via the Stripe Marketplace

1. Go to the [Slicker App page in the Stripe Marketplace](https://marketplace.stripe.com/apps/slicker).
2. Click on the `Install` button.
3. Follow the instructions to authorize Slicker to access your Stripe account.
4. Once authorized, you will be able to use click the `Link` button in the Slicker app page to link your Stripe account to your Slicker instance.

### (Option 2: API Key) Create credentials

1. Go to the Stripe dashboard to create a new restricted API key [here](https://dashboard.stripe.com/apikeys/create).

2. Give the key a name like `Slicker`.

3. For permissions select the following:

   * `Read` on `All core resources`

   <Frame>
     <img alt="Stripe read permissions on core resources" />
   </Frame>

   * `Read` on `All Connect resources`

   <Frame>
     <img alt="Stripe read permissions on connect resources" />
   </Frame>

   * `Read` on `All Reporting resources`

   <Frame>
     <img alt="Stripe read permissions on reporting resources" />
   </Frame>

4. Click the `Create key` button. If prompted confirm your password. Copy the generated key - we will need it later.

### (Option 2: API Key) Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Stripe` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the API key you copied earlier.
5. Leave Stripe Billing option unchecked. This integration is for syncing payment data only. If you are using Stripe Billing please refer to the [Stripe Billing integration guide](/integrations/billing/stripe).
6. Click the `Submit` button to create the integration.

### (Optional) Enable real-time webhooks

By default Slicker keeps your data in sync by polling the Stripe API on a schedule. Adding a webhook lets Stripe push payment changes to Slicker the moment they happen, for near real-time recovery tracking.

<Note>Webhooks are configured **per Stripe account**, in that account's own Stripe Dashboard. They're optional and can be added at any time after the integration is created.</Note>

1. In your Slicker integration settings, turn on **Webhooks** and copy the **Webhook URL** Slicker shows you. This URL is unique to your integration.

2. In the [Stripe Dashboard](https://dashboard.stripe.com/webhooks), go to **Developers → Webhooks** and click **Add endpoint**.

3. Paste the Slicker Webhook URL into the **Endpoint URL** field.

4. Under **Select events**, subscribe to **only the events Slicker uses** (below). You can pick **All events** to get started, but on high-volume accounts we recommend selecting just these — Slicker ignores anything else, so extra events are only wasted webhook traffic:

   * **Payments** — `payment_intent.succeeded`, `payment_intent.payment_failed`, `payment_intent.processing`, `payment_intent.requires_action`, `payment_intent.canceled`

5. Click **Add endpoint** to save it.

6. Open the endpoint you just created, reveal its **Signing secret** (it starts with `whsec_`), and copy it.

7. Back in Slicker, paste the signing secret into the **Webhook Signing Secret** field and save.

<Warning>Copy the **signing secret** (`whsec_…`) — not your API key (`sk_`/`rk_`) or the endpoint ID. If you ever rotate the secret in Stripe, update it in Slicker too.</Warning>

<Note>Using Stripe Billing? Follow the webhook steps in the [Stripe Billing guide](/integrations/billing/stripe) instead — it adds the invoice and subscription events.</Note>

### Troubleshooting

On integration creation, Slicker will attempt to connect to Stripe using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Worldpay
Source: https://docs.slickerhq.com/integrations/payments/worldpay

Learn how to connect Worldpay to Slicker

### Prerequisites

Slicker integrates with Worldpay via Worldpay's Access API. Credentials for this API are only created by Worldpay's implementation managers.

### Create credentials

Request credentials from your Worldpay Implementation Manager for the Payment Queries Access API.
They will provide you with a username and password which you can use to create a Slicker integration.

### Create integration in Slicker

1. Go to Slicker's [new integration page](https://app.slickerhq.com/integrations/new).
2. Select `Worldpay` from the list of integrations.
3. Give the integration a name and description to help you identify it later.
4. Enter the username and password given to you by Worldpay's Implementation Manager.
5. Click the `Submit` button to create the integration.

### Troubleshooting

On integration creation, Slicker will attempt to connect to Worldpay using the provided API key.
If the connection fails, you will see an error message like the one below.
Please double-check the API key, make sure it has the correct permissions, and try again.

<Frame>
  <img alt="Failed integration creation message" />
</Frame>


# Introduction
Source: https://docs.slickerhq.com/introduction

Slicker reduces involuntary churn and optimizes revenue recovery for subscription businesses.

## What is Slicker?

Slicker helps subscription businesses reduce involuntary churn and recover lost revenue. Our churn prevention platform combines industry knowledge and machine learning to create personalized strategies tailored to each business.

We analyze a wide range of data points, including payment error codes, issuer details, network error messages, customer behavior, and subscription history. This approach ensures recovery efforts are optimized and align with the specific needs of your business.

## Why Slicker?

Involuntary churn due to failed payments can significantly impact your subscription business. Slicker solves this by:

* **Optimizing payment retries**: Using data-driven insights to time retries when they are most likely to succeed.
* **5-minute setup**: We integrate directly with your payment processors and billing systems, no code changes required.
* **Automated recovery emails**: When retries aren't enough, Slicker sends targeted emails from your own domain to prompt customers to update their payment method or approve a transaction.
* **Your own team of payment experts**: Our platform analyzes transaction data, customer behavior, and industry trends to implement strategies tailored to your business, acting as an extension of your team.

## Useful links

Explore key sections of our documentation to get started and make the most of Slicker.

<CardGroup>
  <Card title="Account Setup" icon="users-gear" href="/account_setup">
    Learn how to set up your Slicker account and start recovering revenue.
  </Card>

  <Card title="Integration Setup" icon="plug" href="/integrations/overview">
    Step-by-step guide to integrate Slicker with your billing and payment providers.
  </Card>

  <Card title="Strategies" icon="chart-line" href="/essentials/strategies">
    Discover how Slicker optimizes payment recovery strategies.
  </Card>

  <Card title="Analytics" icon="chart-pie" href="/essentials/analytics">
    Dive into analytics to track your recovery performance and insights.
  </Card>

  <Card title="Emails" icon="envelope" href="/essentials/emails">
    Learn how automated recovery emails work alongside retries to recover failed payments.
  </Card>

  <Card title="Multi Gateway Routing" icon="split" href="/essentials/multi_gateway_routing">
    See how Slicker routes payments across multiple gateways to maximize success rates.
  </Card>
</CardGroup>