ORDER_CREATEDOrderOrder confirmation
B2B Transaction Management
Orders, payments and billing in one workflow.
Adionexus gives businesses a single system for managing customer orders, payment events, invoices and operational notifications.
09:58:32
payment.confirmed200 receipt sent09:58:33
invoice.created200 invoice sent09:58:34
order.processing→ status updated
Product
Built around transaction events, not promotional campaigns.
Every notification Adionexus sends starts with something a customer or account actually did: an order was placed, a payment cleared or failed, an invoice was issued, an email address was verified, a password reset was requested.
There is no audience builder and no send schedule. Messages go to the customer the event belongs to, at the moment the event is recorded, and each one is logged against the order or account that caused it.
Orders
Payments
Invoices
Account verification
Security events
Workflows
From transaction to notification.
Each event follows the same path. Your system records what happened; Adionexus validates it, updates the related records and sends the matching notification.
-
01
Customer action
A customer places an order, pays, or updates their account.
-
02
Transaction event
Your backend posts a typed event to the Adionexus API.
-
03
Adionexus processing
The event is validated, linked to the order and customer, and logged.
-
04
Notification
The template mapped to that event type is rendered with order data.
-
05
Customer receives update
Delivery status is recorded on the event for later reference.
Event to notification mapping
Default templates. Each mapping can be edited per workspace.
PAYMENT_CONFIRMEDPaymentPayment receipt
INVOICE_CREATEDBillingInvoice notification
PAYMENT_FAILEDPaymentPayment failure notice
ORDER_SHIPPEDFulfillmentShipping notification
ACCOUNT_VERIFIEDAccountAccount activation
PASSWORD_RESETSecurityPassword reset email
Platform
The records behind every transaction.
Orders, payments, invoices and accounts share one data model, so a single order page shows everything that happened to it.
Order Management
Track orders, status changes and customer activity.
- pending → paid → shipped
- Per-order activity feed
Payment Events
Record successful, failed and pending payment events.
- Failure reason codes
- Linked to order and invoice
Billing & Invoices
Generate and track transaction-related invoices.
- Sequential invoice numbers
- Open, paid, void states
Customer Accounts
Handle registration, verification and account security.
- Email verification flow
- Password reset tokens
Operational Notifications
Automatically notify customers when important transaction events occur.
- One template per event type
- Delivery status per message
Event Logs
Keep a clear history of transaction and notification events.
- Filter by type, order, customer
- Full payload per event
Transactional Email
Email that follows the transaction.
Adionexus uses event-driven notifications for messages directly related to a customer's activity. Each message is sent to the account holder involved and contains the details of the order, payment or account change that triggered it.
Security
Transaction data with clear operational controls.
Access to orders, payments and customer records is scoped by role, and every change is written to a log you can review.
Encrypted connections
The dashboard and API are served over HTTPS only.
Role-based access
Limit who can view payments, issue invoices or manage users.
Event logging
Every transaction and notification event is stored with its payload.
Account verification
Customer accounts confirm ownership of their email before activation.
Secure authentication
Hashed credentials, expiring reset links and scoped API keys.
Audit history
See who changed what, and when, across your workspace.
API
Designed around events.
Send one request when something happens in your system. Adionexus handles the record updates and customer notification that follow.
- 01Post the event with its type and the IDs it relates to.
- 02Adionexus links it to the existing order and customer records.
- 03The mapped workflow runs: status update, invoice, notification.
Example event types
order.created
payment.confirmed
payment.failed
invoice.created
order.shipped
account.verified
POST /api/v1/events
Authorization: Bearer adx_test_••••••••••••
Content-Type: application/json
{
"type": "payment.confirmed",
"order_id": "ADX-10482",
"customer_id": "cus_28491",
"amount": 1284.00,
"currency": "USD"
}HTTP/1.1 202 Accepted
{
"id": "evt_7Hq2Lw9XbN",
"type": "payment.confirmed",
"status": "accepted",
"order_id": "ADX-10482",
"workflows": [
"order.mark_paid",
"invoice.generate",
"notify.payment_receipt"
],
"received_at": "2026-10-02T09:58:32Z"
}curl https://api.adionexus.web.id/api/v1/events \
-H "Authorization: Bearer $ADIONEXUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "payment.confirmed",
"order_id": "ADX-10482",
"customer_id": "cus_28491",
"amount": 1284.00,
"currency": "USD"
}'application/jsonv1
When a transaction event is recorded, Adionexus processes the event and triggers the appropriate operational workflow.
Use cases
Where Adionexus fits.
Any business that takes orders or payments from other businesses and needs to keep customers informed about them.
Online Commerce
Order confirmations, payment receipts and shipping updates.
order.createdorder.shippedB2B Distribution
Orders, invoices and account notifications.
invoice.createdaccount.verifiedSubscription Billing
Billing events, payment status and account updates.
payment.confirmedpayment.failedService Platforms
Customer accounts, transaction records and operational notifications.
account.verifiedpassword.reset
Documentation
Connect your transaction workflow.
Start with the API documentation and integrate Adionexus into your existing order and billing workflow.
// integration steps
- Create a workspaceTest mode is enabled by default.
- Generate an API keyScope it to
events:write. - Send your first event
POST /api/v1/events - Review the event logCheck the record update and notification.