gitlabEdit

โš ๏ธProvider Issues

Comprehensive guide to debugging provider-specific problems across all 12 Docs-Dispatcher providers.

Overview

This guide covers:

  • Provider-specific error patterns for all 12 providers

  • Configuration issues by provider

  • Credential validation

  • Provider API errors

  • Sandbox vs production issues

  • Rate limits per provider

  • Fallback strategies

  • Provider health checks

Provider Troubleshooting Matrix

Quick reference for common issues:

Provider
Common Issues
Config Check
Status Page

iPaidThat

Duplicate invoice, invalid API key

/admin/configs

No public status

PennyLane

SIRET requirement, tax validation

/admin/configs

No public status

Qonto

Org slug, sandbox mode

/admin/configs

status.qonto.com

SuperPDP

Certification, archiving

/admin/configs

No public status

Signaturit

Signer validation, webhooks

/admin/configs

No public status

Universign

Qualified signature, French compliance

/admin/configs

No public status

Yousign

Multi-signer, sequential flow

/admin/configs

status.yousign.com

MySendingBox

Address validation, tracking

/admin/configs

No public status

Brevo

SMS credits, sender ID

/admin/configs

status.brevo.com

OVH

API credentials, account credits

/admin/configs

status.ovh.com

SMS Factor

Phone format, delivery

/admin/configs

No public status

SMS Magic

International routing

/admin/configs

No public status

Invoicing Providers (4)

iPaidThat

Configuration Structure

Common Errors

1. Invalid API Key

Solution:

2. Duplicate Invoice Number

Solution:

3. Missing Customer Information

Solution:

PennyLane

Configuration Structure

Common Errors

1. SIRET Required for French B2B

Solution:

2. Invalid Tax Rate

Solution:

3. Invalid Company Configuration

Solution:

Qonto

Configuration Structure

Common Errors

1. Invalid Organization Slug

Solution:

2. Sandbox vs Production Mismatch

Solution:

3. Rate Limit Exceeded

Rate limits:

  • Sandbox: 10 requests/minute

  • Production: 100 requests/minute

SuperPDP

Configuration Structure

Common Errors

1. Missing Entity Code

Solution:

2. Government Invoice Requirements

Solution:

eSign Providers (3)

Signaturit

Configuration Structure

Common Errors

1. Invalid Signer Email

Solution:

2. Webhook Verification Failed

Solution:

3. Document Already Signed

Prevention:

Universign

Configuration Structure

Common Errors

1. Qualified Signature Not Available

Solution:

2. French Compliance Requirements

Solution:

Yousign

Configuration Structure

Common Errors

1. Sequential Signing Order Error

Solution:

2. Document Size Limit Exceeded

Solution:

Postal Provider (1)

MySendingBox

Configuration Structure

Common Errors

1. Invalid Address

Solution:

2. International Shipping Restrictions

Solution:

3. Tracking Not Available

Solution:

SMS Providers (4)

Common SMS Issues (All Providers)

1. Invalid Phone Number Format

All SMS providers require E.164 format: +[country code][number]

2. Message Length Exceeded

Provider-Specific Rate Limits

Provider
Requests/min
Burst
Best For

Brevo

100

200

High volume, marketing

OVH

50

100

European coverage

SMS Factor

100

150

French market, analytics

SMS Magic

200

300

Global, high throughput

Configuration Debugging

Check Provider Configuration

Test Provider Credentials

Provider Status Checks

Fallback Strategies

Summary

Key troubleshooting steps:

  1. Check configuration - Verify provider is configured and active

  2. Validate credentials - Test API keys and credentials

  3. Check provider status - Verify provider API is operational

  4. Validate data - Ensure data meets provider requirements

  5. Test in sandbox - Use sandbox mode for testing

  6. Implement fallbacks - Have backup providers configured

  7. Monitor rate limits - Respect provider limits

  8. Log provider errors - Track provider-specific errors

Provider-specific requirements:

  • PennyLane: SIRET for French B2B e-invoices

  • Qonto: Organization slug required

  • SuperPDP: Entity code and PO numbers

  • Universign: French compliance notices

  • MySendingBox: Address validation per country

  • All SMS: E.164 phone format

Always test with validation endpoint before production dispatch.

Last updated