Upcoming Transaction Status Changes
Audience: Developers consuming transaction via webhooks and GET operations
Effective: June 30th 2025 July 8th, 2025
What's Changing
The status attribute in transaction objects is being updated to a more descriptive, lifecycle-aware model. This change is required to support a range of upcoming features and enhancements, and may necessitate updates to your current integrations.
Only transactions created after the release will return statuses from the new list. Older transactions will continue to return their original statuses, such as APPROVED.
Why This Matters
These status updates enable several powerful new capabilities coming to the platform, including:
- Separate APIs for Authorization, Capture, Void, and Refund — allowing for more precise control and visibility.
- Apple Pay and Google Pay support — expanding the ways customers can complete payments.
- Transaction synchronization — the ability to bring external transactions into the Authvia platform for unified visibility and management.
- Expanded status tracking — including new states like
SettledandFundedto better reflect transaction progression. - Batch processing support — submit and process transactions in bulk via FTP or API.
These features are part of a broader platform enhancement initiative. Full release notes will be shared at launch, but immediate action may be required to ensure compatibility with the new status model.
Current Values:
'AUTHORIZED' | 'APPROVED' | 'DECLINED' | 'ERROR' | 'FAILED' | 'NOT AUTHORIZED' | 'PAYMENT-IN-PROGRESS' | 'PROCESSING'
New Values:
| Action | Status | Description |
|---|---|---|
| AUTHORIZE | AUTHORIZING | The authorize is in progress. |
| AUTHORIZE | AUTHORIZED | The authorize transaction has completed. This is a final status. |
| CAPTURE | CAPTURED | The funds have been captured. |
| CAPTURE | SETTLING | The funds are held in a batch to be settled. |
| CAPTURE | SETTLED 🆕 | The captured transaction has been settled by the payment gateway. See Changelog |
| CAPTURE | FUNDED | The captured transaction funds are in the merchant bank account. |
| CHARGE | CHARGED | The charge has completed. |
| CHARGE | AUTHORIZING | The processor has separate AUTHORIZE and CAPTURE steps, and the AUTHORIZE is under way. |
| CHARGE | AUTHORIZED | The processor has separate AUTHORIZE and the AUTHORIZE is complete. A CAPTURE will be execute. |
| CHARGE | CAPTURED | The processor has separate AUTHORIZE and the CAPTURE is complete. |
| CHARGE | SETTLING 🆕 | The captured transaction has been settled by the payment gateway. See Changelog |
| CHARGE | SETTLED | The captured transaction has been settled by the payment gateway. |
| CHARGE | FUNDED | The captured transaction funds are in the merchant bank account. |
| PAYOUT | PAIDOUT | The payout was completed. This is a final status. |
| PAYOUT | PAYING | The payout is in progress. |
| REVERSAL | VOID | The transaction being reversed requires a VOID. |
| REVERSAL | VOIDING | The void request is in progress. |
| REVERSAL | VOIDED | The transaction was voided. This is a final status. |
| REVERSAL | REFUND | The transaction being reversed requires a REFUND. |
| REVERSAL | REFUNDING | The refund is in progress. |
| REVERSAL | REFUNDED | The refund was completed. This is a final status. |
| VOID | VOIDING | The void request is in progress. |
| VOID | VOIDED | The transaction was voided. This is a final status. |
| REFUND | REFUNDING | The refund is in progress. |
| REFUND | REFUNDED | The refund was completed. This is a final status. |
| - | DECLINED | The transaction was declined. This is a final status. |
| - | ERROR | An error occurred during the transaction. This is a final status. |
| - | FAILED | The transaction failed. This is a final status. |
| - | NOT AUTHORIZED | The transaction was rejected due to lack of authorization. This is a final status. |
| - | PROCESSING | The transaction is being processed, but has not yet executed against the gateway. Will likely be for when any transaction is created. |
Note: Transaction actions and statuses are likely to be added to in the future, to support additional capabilities. Additional details on statuses and FAQ can be found here.
What You Need to Do
- Review and update any client logic that parses or reacts to the
statusfield. - Ensure all webhook handlers and GET consumers can accommodate the new values, and possible future values.
- Update your webhook subscriptions to be specific to your current needs. See Use Webhook Conditions.
⚠️ This is a read-only field — it is never supplied by clients, only received from our platform.
Use Webhook Conditions
With the introduction of more granular transaction statuses, additional webhook events will be published. To avoid processing unnecessary events, you must update your webhook subscriptions to include filters that limit notifications to only the statuses your system requires. See the Create Webhook Subscription documentation for implementation details.
Temporary Backward Compatibility
For 90 days following the release, the platform will continue to announce the APPROVED status for CHARGE transactions that reach the CAPTURED state. This temporary overlap is intended to provide a longer runway for systems currently listening for APPROVED webhook events. After the 90-day period, this behavior will be removed, and systems must transition to using the updated status model.
July 9th, 2025 we updated this solution to also send APPROVED for PAIDOUT, VOIDING and REFUNDING statuses (and the corresponding actions) as well.
For questions or migration guidance, contact [email protected]