- 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
string
default:"integrated"
Collection type. Currently only “integrated” is supported for public API
string
required
Unique identifier from your payment provider (e.g., Paystack transaction ID)
object
required
Payment amount object
number
required
Payment amount as a number
string
required
ISO currency code (e.g., “NGN”, “USD”, “GHS”)
object
required
Customer information. Contact will be auto-created if not exists, or found by
phone/email if already exists
string
required
Customer’s first name
string
required
Customer’s last name
string
required
Customer’s phone number (E.164 format recommended)
string
required
Customer’s email address
array | object
Metadata can be an array or object in any format. Must include a
description field when metadata is provided.number
default:"1440"
Collection expiration time in minutes (default: 1440 = 24 hours)
object
Payment options configuration
boolean
default:"false"
Whether to generate payment options
array
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 instructionsstring
Slug of the payment provider (must exist in your providers list)
object
Follow-up configuration
boolean
Whether to enable automated follow-up messages
number
Minutes to wait before sending first follow-up
string
Follow-up frequency. Options:
every_5m, every_10m, every_15m,
every_30m, every_1h, every_2h, every_4h, every_6h, every_12h,
dailyarray
Array of communication channels. Options:
whatsapp, sms, emailstring
Message tone. Options:
gentle, professional, urgentExample Request
Response
string
Response status (“success”)
string
Success message
object
Collection object
string
Collection ID
string
Collection type
object
Contact information
string
External payment reference
object
Payment amount
string
Collection status (pending, completed, expired, overdue, cancelled)
object
Payment options (if enabled)
array
Array of generated payment options
array
Array of collection events
string
ISO 8601 timestamp
string
ISO 8601 timestamp
string
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