NextCommerceCo / NextCommerceCo/docs
Payments Guide: how several MIDs on one processor are modelled
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 0
- Forks
- 0
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 6
Description
Gap: gateway groups (weighted routing, soft-decline retry across members) are documented, but nothing states whether a merchant with, say, three NMI merchant accounts adds three NMI gateway instances and groups them. The word "MID" does not appear in the payments docs.
How it surfaced: the agent consultation probes for nextcommerce-site#154 (2026-09-16). The Sticky.io persona (3 NMI MIDs + 1 Authorize.net) is the common funnel/CRM migration shape; both agents inferred the gateway-instances-in-a-group pattern and then flagged it as unverified in the open questions.
Ask: a short section on the Payments Guide (or the NMI page) using the merchant's vocabulary: multiple MIDs on one processor = multiple gateway instances, grouped; note any limits.
Evidence: probe matrix, sticky transcript (Claude), sticky transcript (Codex).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Payments Guide and the NMI page, then review the linked probe matrix and Sticky.io transcripts for the terminology and open question. Add a short section explaining that multiple MIDs on one processor use multiple gateway instances grouped together, including any documented limits; the guide should explicitly use “MID.”
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100