Overview

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.

​

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 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:

• Essential Events: Subscription creations/changes, invoice generation, payment attempts
• Valuable Context: Customer history, subscription details, failure reasons
• Complete Details: See the API Reference for comprehensive field specifications

​

Setup Process

Setting up a custom billing integration typically follows these 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:

​

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

​

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

​

Next Steps

To begin your custom billing integration:

1. Review our API Reference to understand data requirements
2. Contact our team to schedule an integration consultation
3. Explore connecting your payment processors for enhanced results