Before accepting real payments, confirm every item on this list is complete. Work through Account Setup to Testing in order — each of those sections depends on the one before it. The sections after that are independent: complete the ones that apply to your setup.
Account Setup
Baseline settings for your Admoji account. Complete these before anything else.
Timezone set: Settings > Account settings > General Settings > Timezone.
Payment method added for your Admoji subscription: Settings > Payment Methods > Add New.
API key copied for developer integration: Settings > Account settings > API Keys.
Products
What you sell. Products are created at the account level and become available to every campaign from there.
At least one product group created: CRM > Products > Add group.
At least one product added with the correct Billing Type (One Time or Recurring) and Type (Sale, Upsell, or Shipping).
Campaign
The container that holds your offer — this is where products, users, and payment methods come together.
Campaign created: CRM > Campaigns > New.
Product group(s) assigned to the Campaign: Edit Campaign > Products tab — check the product groups this campaign will sell. This is what links your products to the Campaign.
Processor(s) assigned to the Campaign: Edit Campaign > Processors tab. Only needed if you accept alternative payment methods such as ACH, PayPal, Square, or Sezzle — standard credit card transactions are routed by the rules in Merchants > Management.
All users granted access to the Campaign (via Grant Permission To Users during creation, or Settings > edit user > Campaigns tab).
Merchant Account
The MID that will process your charges. Connect it before linking it to products.
Processor connected: Merchants > Processors > New.
Merchant Management
This is what tells Admoji which MID charges which product. Until a product is covered by a rule it cannot be charged, in testing or live.
Rule created: Merchants > Management > Add Rule, with a Rule Name that identifies it.
Products added to the rule: Products card > Edit > Add Products.
MID(s) added to the rule: Add MID > Add Processors.
Management type selected: Weighted Management (split by percentage) or Priority Queue (in order, with failover).
Testing
Verify the whole path before real traffic reaches it: test cards first, then a real card.
Test card added: Settings > Account settings > Test Cards > Add New.
Test transactions processed and verified (approvals and declines).
Test Mode turned OFF on your live processor.
Live transaction tested end-to-end with a real card.
Test cards disabled or test customers marked before going live.
Email Autoresponders
Skip this section if you are not sending automated emails.
SMTP server configured: Administration > Plugins > SMTP Setup > New.
Email template created: CRM > Autoresponders > Templates > New.
Email event created with at least one product assigned: CRM > Autoresponders > Events > New.
Event attached to your Campaign: Edit Campaign > Email Autoresponders tab.
Test email confirmed sent after a test transaction.
Fulfillment
Skip this section if you are managing fulfillment manually or not using a fulfillment provider.
Fulfillment provider connected: Administration > Plugins > Fulfillment tab.
Fulfillment enabled on each product: CRM > Products > edit product > Fulfillment tab.
Fulfillment tested with a live transaction (test credit card orders are not sent to fulfillment).
Alerts
Optional, but worth setting up — this is how you find out something is wrong without checking manually.
Alert System configured for chargebacks, declines, and processing limits: Administration > Alert System > New.
API Integration
Developer work on your own checkout and confirmation pages. There are no Admoji screens for this section.
Add Order endpoint integrated on your checkout page.
Mark as Complete endpoint added to your thank-you or confirmation page.
If using upsells, the same OrderID from the initial sale is passed when submitting upsell transactions.
Gateway-specific frontend integration completed (e.g., Square checkout form, NMI tokenization, Sezzle SDK).
Affiliate variables coded and passing correctly (if using affiliate traffic).
Idempotency IDs generated uniquely per API request.
Related articles