ACO HQ unifies custom Discord webhook routing, checkout processing, member identity, live drops, orders, PAS, and reporting—so your operation stays fast without becoming scattered.
Real-time roster and product performance.
The Webhook Configuration Center acts as the control plane for your relay. Add or disable scraper sources, target exact Discord webhook users, define where success messages should go, test destinations, and inspect every delivery result.
ACO HQ can route matched members to their group destination, unmatched checkouts to a dedicated channel, and use the original environment webhook as a final fallback.
ACO HQ preserves the context behind every checkout and turns it into a complete workflow your team can operate, audit, and improve.
Configure scraper sources, destination routing, relay health, fallback behavior, test delivery, and audit history without editing the relay.
Connect multiple checkout profile names to one Discord member while preserving the immutable Discord user ID used for reliable mentions.
Capture unmatched checkouts instead of losing them, route them to a dedicated Discord destination, and assign them to a member later.
Detect drops from incoming activity, create manual drops, manage target rosters, and monitor checkout progress as the release happens.
Convert successful webhook events into organized checkout and order records with bot, runner, retailer, profile, member, and drop context.
Set PAS by product, track outstanding balances, manage member invoices, verify completion, and maintain payment history.
Surface the newest activity, failed webhooks, missing PAS, unmatched profiles, open drops, and other operational priorities.
Review member and bot performance, monitor drop outcomes, and generate branded share images directly from verified drop data.
A successful checkout is only the beginning. ACO HQ keeps member identity, drop progress, order details, and PAS responsibilities connected.
Use the profile name from the incoming checkout as the primary account match while retaining the Discord user ID for dependable mentions.
See target progress, successful members, unit counts, product performance, and the newest checkout activity.
Assign different PAS values by product, group the results into member invoices, and track payment completion.
ACO HQ surfaces operational priorities before they turn into cleanup work.
Every step is designed to preserve attribution, prevent duplicate work, and keep the next action obvious.
The Railway relay watches only the Discord servers, channels, and webhook users enabled in ACO HQ.
The protected ingest endpoint authenticates the relay, detects the program, parses the checkout, and blocks duplicates.
ACO HQ matches the checkout profile to the correct account record, Discord member, member group, product, and drop.
Checkout and order records are created with their full operational context while live drop and dashboard metrics update.
The success notification is delivered to the member group destination or the dedicated unassigned checkout channel.
Delivery status, destination source, relay activity, webhook payload, and processing results remain visible for review.
Secure by design
Operational routes require a valid ACO HQ session.
Relay configuration, status, and ingest calls use the shared webhook secret.
Discord webhook values are not exposed as plain text throughout the interface.
Successes, failures, destination sources, and timestamps remain traceable.
New ACO HQ registrations are temporarily paused. Existing customers still have full access and can sign in normally.