- Create a payment collection linked to an external payment provider
- Automatically create or find contacts based on customer information
- Generate payment options (payment links, virtual accounts, etc.)
- Configure automated follow-up messages
- Track payment metadata and events
Request Body
Collection type. Currently only “integrated” is supported for public API
Unique identifier from your payment provider (e.g., Paystack transaction ID)
Payment amount object
Payment amount as a number
ISO currency code (e.g., “NGN”, “USD”, “GHS”)
Customer information. Contact will be auto-created if not exists, or found by
phone/email if already exists
Customer’s first name
Customer’s last name
Customer’s phone number (E.164 format recommended)
Customer’s email address
Metadata can be an array or object in any format. Must include a
description field when metadata is provided.Collection expiration time in minutes (default: 1440 = 24 hours)
Payment options configuration
Whether to generate payment options
Array of payment methods to generate when enabled: -
payment_link: Generates
a payment link URL - virtual_account: Creates a dedicated virtual bank
account - mobile_money: Generates mobile money payment instructions -
card: Card payment option - bank_transfer: Bank transfer instructionsSlug of the payment provider (must exist in your providers list)
Follow-up configuration
Whether to enable automated follow-up messages
Minutes to wait before sending first follow-up
Follow-up frequency. Options:
every_5m, every_10m, every_15m,
every_30m, every_1h, every_2h, every_4h, every_6h, every_12h,
dailyArray of communication channels. Options:
whatsapp, sms, emailMessage tone. Options:
gentle, professional, urgentExample Request
Response
Response status (“success”)
Success message
Collection object
Collection ID
Collection type
Contact information
External payment reference
Payment amount
Collection status (pending, completed, expired, overdue, cancelled)
Payment options (if enabled)
Array of generated payment options
Array of collection events
ISO 8601 timestamp
ISO 8601 timestamp
ISO 8601 timestamp (null if not completed)
Example Response
Notes
- If
followUpis not provided, AI will intelligently determine the best follow-up strategy based on the collection context - Contact is automatically created or found based on phone/email
- Payment options are only generated if
payable.enabledis true - The reference must be unique within your account
metadatacan be an array or object in any format, but must include adescriptionfield when provided