This guide walks through the core flow:
- Create a Payer and Setup Request
- Securely capture and store the payment method using Payment Element
- Charge the payment method using Payment Requests
Collecting Payment Details
Creating a Payer
A Payer represents the individual or organization you want to collect money from. Typical examples include policyholders, brokers, employers, or business partners.
Creating a payer helps you tie payment activity and reconciliation back to a specific entity. The full list of request parameters can be found here.
Example
Creating a Setup Request
A Setup Request lets your payer securely provide payment details through an Acclaim-hosted interface. Payment details never pass through your backend. The Create Setup Request documentation has more details about this endpoint.
Response: (abbreviated)
Collecting Details Securely with the Payment Element
Processing Payments
Processing payments in Acclaim Collect happens in two major steps:
- Create a Payment Request: an instruction to collect money from a payer
- Confirm the Payment Request: by either (a) confirming a payment method supplied via UI, or (b) charging a previously saved token
Payment Requests provide a consistent flow for collecting premiums, deductibles, fees, or partner remittances across multiple PSPs.
Creating a Payment Request
The full list of request parameters can be found here.
Confirming a Payment Request
Once the payment request has a payer and payment method assigned, or collected, it is ready to be confirmed, which will attempt to collect payment. The Confirm Payment Request documentation has more details.
Response: (abbreviated)
Tracking Payment State
You can track the status of a payment request in two ways:
- Polling from your backend
Useful for synchronous flows or to verify final state after a redirect.
- Listening for webhooks
Acclaim sends webhook events for all major lifecycle changes:
payment_request.succeeded
payment_request.failed
setup_request.succeeded
Handling Failed Payments
When a payment request moves to a failed state:
You may:
- Present the payer with a link to re-enter payment details
- Trigger a new setup request
- Retry with a fallback PSP (if configured)
- Mark the invoice as overdue in your internal billing system
Acclaim returns granular error codes to help categorize failed payments (insufficient funds, authentication failed, payment method unsupported, network issues, etc.). See Payment failures for the complete list of codes and messages.
Summary
- A Payment Request is the core object for charging payers.
- Payments can be confirmed immediately using a saved token, or interactively using the Payment Element.
- Acclaim manages the full lifecycle, including PSP routing, authentication, and error handling.
- Use webhooks to reliably update your systems when payments succeed or fail.
Last modified on June 14, 2026