Billing guide

Developer-paid billing

Developers receive 100 successful prints free across all customer sites, then pay centrally through Stripe or an approved direct-invoice arrangement. Customers never enter payment details.

100 shared free prints

Developer registration is free and does not request billing details. The developer can create multiple customers immediately. The first 100 successfully completed print jobs are shared across the entire developer organisation; failed jobs do not consume the allowance.

Choose a billing arrangement when ready

For Stripe billing, the developer adds their legal billing details and completes Stripe Checkout once. Stripe securely retains the default payment method, so creating another customer does not ask for card details again. AppClickPrint administrators can instead enable direct invoicing for an approved developer without requiring Stripe billing information.

Customer sites and safeguards

Each paid customer site costs $2.50 USD monthly. Developers set a hard maximum customer count. The provisioning API returns customer_limit_reached instead of creating a site beyond that cap.

Monthly print-data limits

Every paid site starts at 50 MB. Developers can configure 100 MB, 150 MB or another 50 MB increment. Each additional 50 MB costs $1 USD monthly. The limit is a hard ceiling; AppClickPrint rejects printing beyond it rather than creating an unplanned overage.

Up to 25,000 direct-URL jobs: gateway-direct documentUrl jobs use a fixed 2 KB of allowance, so the standard 50 MB plan supports 25,600 such jobs per monthly period. Uploaded and inline jobs depend on their actual file size. Learn how to get more from the allowance.

PATCH /v1/developer/customers/customer-4821/usage-limit
Authorization: Bearer acm_YOUR_MANAGEMENT_KEY
Content-Type: application/json

{"monthlyLimitMb":100}

Usage calculation fine print

Gateway-direct delivery is normally the most allowance-efficient option for larger documents because the Android gateway downloads from your storage and AppClickPrint handles only the print-control workflow. Use a short-lived signed HTTPS URL and keep it valid long enough for an offline gateway to reconnect.

Billing API responses

Fair use: the monthly allowance does not replace reasonable burst control or acceptable-use protections. Print submission is limited to 300 requests per minute per API credential.