Invoice delivery decision guide

When building your integration with Payabli, you need to decide how to create, deliver, and collect payment on invoices. This guide helps you choose between using Payabli’s native invoicing system or building custom invoice delivery based on your specific use case and requirements.

Decision tree

Use this interactive decision tree to walk through the best approach for invoice delivery in your integration.

Recommended strategy by use case

Choose the right invoice delivery approach based on your needs. Here’s a quick reference to help you decide:

Payabli native invoicing

Payabli native invoicing is ideal when you need complete invoice management with minimal development effort. The system handles invoice creation, delivery, payment collection, and status tracking. Use native invoicing when:

• You need standard invoice functionality without custom design requirements
• You want to minimize development effort and technical overhead
• You’re processing recurring invoices with autopay enrollment
• You need built-in payment tracking and reconciliation
• You want automated email delivery with payment links

Native invoicing is reliable when:

• You can use Payabli’s standard invoice template
• Your customers accept email delivery with hosted payment pages
• You don’t require custom invoice layout or branding
• Standard invoice workflows meet your business needs

Implementation overview

Native invoicing requires only API integration to create and send invoices. Payabli handles all other aspects of the invoice lifecycle.

Key features

Understanding what Payabli native invoicing provides helps you determine if it meets your requirements.

Native invoicing best practices

Follow these best practices to build reliable native invoicing implementations.

• Set up webhooks for immediate payment notifications rather than polling invoice status
• Include detailed line items for customer clarity and proper accounting
• Set appropriate due dates and configure reminder notifications
• Enable autopay enrollment for recurring billing scenarios
• Monitor invoice status through dashboard for customer service inquiries

Custom invoice with embedded components

Custom invoicing with embedded components is ideal when you need complete control over invoice design and want customers to pay without leaving your page. You host custom invoice pages and use the temporary token flow with Payabli embedded components to collect payment securely. Use embedded components when:

• You need complete branding control over invoice presentation
• You’re building SaaS platforms with existing invoice systems
• You want customers to pay directly on your invoice page
• You have frontend and backend development resources
• You need custom invoice workflows or business logic
• You need complete control over transaction parameters

Embedded components with temporary token flow are reliable when:

• You can manage component lifecycle and error handling
• You implement proper invoice status tracking in your system
• You handle customer confirmations and receipt delivery
• You can make secure API calls from your backend

Implementation overview

Custom invoicing with embedded components uses the temporary token flow to give you complete control while maintaining PCI compliance. This approach combines the security of embedded components with the flexibility of direct API calls.

1
    var payabliConfig = {
2
      type: "methodEmbedded",
3
      rootContainer: "payment-container",
4
      defaultOpen: 'card',
5
      token: "YOUR_API_TOKEN",
6
      temporaryToken: true, // Generate temporary token
7
      hideComponent: false,
8
      // Additional styling and configuration
9
    };

1
    // Component returns temporary token
2
    response.responseData = {
3
      "referenceId": "30e7658e-5c2c-4638-8308-b48edec0718b-1647",
4
      "resultCode": 1,
5
      "resultText": "Added",
6
      "customerId": 1647
7
    }

1
    // Use temporary token to process payment
2
    POST /api/MoneyIn/getpaid
3
    {
4
      "paymentMethod": {
5
        "method": "card",
6
        "storedMethodId": "30e7658e-5c2c-4638-8308-b48edec0718b-1647"
7
      },
8
      "orderId": "INV-2025-001",
9
      "entryPoint": "invoice_payment",
10
      "paymentDetails": {
11
        "totalAmount": 1500.00
12
      },
13
      "customerData": {
14
        "customerId": 1647
15
      }
16
    }

Component options

Understanding which embedded component to use helps you choose the right approach for your invoice payment collection.

Embedded components best practices

Follow these best practices to build reliable embedded component implementations.

• Use temporary token flow for complete control over transaction parameters
• Implement proper error handling for declined payments and validation errors
• Use webhooks in addition to API responses for reliable payment confirmation
• Apply custom styling to match your invoice design and brand guidelines
• Track invoice status changes in your system for accurate reporting
• Send branded confirmation emails with transaction details to customers
• Make secure API calls from your backend, never expose API credentials in frontend
• Set up webhooks for payment notifications and status updates

Custom invoice with payment links

Custom invoicing with payment links is ideal when you need control over invoice design with minimal technical complexity. You create custom invoices and include links that redirect customers to Payabli’s hosted payment page. Use payment links when:

• You need custom invoice design without embedded component complexity
• You’re delivering PDF invoices via email
• You want to minimize PCI compliance scope
• You have limited frontend development resources
• You’re building email-based invoice workflows

Payment links are reliable when:

• Customer redirect to payment page provides acceptable experience
• You can manage invoice status tracking in your system
• You implement webhook handling for payment notifications
• Your invoice format supports clickable links

Implementation overview

Custom invoicing with payment links requires invoice design capability and payment link generation.

Link configuration options

Understanding payment link configuration helps you create the best customer experience.

Payment link best practices

Follow these best practices to build reliable payment link implementations.

• Generate unique payment links for each invoice to track payment accurately
• Configure return URLs to provide confirmation pages after payment
• Customize hosted page appearance to match your invoice branding
• Use webhooks for reliable payment notification rather than return URL only
• Include clear payment instructions and support contact in invoices

Choosing the right approach

Selecting the appropriate invoice delivery method is crucial for meeting your business needs and providing a seamless customer experience. Consider the following factors when making your decision:

Decision framework

Start with your requirements to determine the best approach.

Need standard invoicing with minimal development? Use Payabli native invoicing for complete invoice management with API-only integration.

Need complete branding control with inline payment? Use custom invoices with embedded components for seamless customer experience on your pages.

Need custom design with easy implementation? Use custom invoices with payment links for branding control without component integration complexity.

Comparison matrix

Compare approaches across key factors to make the best decision for your integration.

Best practices

Follow these best practices to ensure successful invoice delivery and payment collection regardless of the approach you choose.

Quick reference

This section provides quick links to relevant API endpoints, webhook events, and integration guides mentioned in the decision tree and throughout this guide.