Verification trail for MnemoPay's agent payment infrastructure.
If you reached this page from a trust warning, here is the calm version: the site is archived, the SDK is open source, Google Safe Browsing has returned a clean status, and the Scamadviser/IPQS dispute is being handled in writing.
Current status
Scamadviser/IPQS has been disputed with supporting evidence. Google Safe Browsing has checked the domain clean, public archives are available through the Wayback Machine, and the SDK remains auditable at github.com/mnemopay/mnemopay-sdk.
Why the classifier reacted
IPQS's phishing classifier was built to detect consumer-facing fraud sites that impersonate banks or payment processors. It looks for: payment-adjacent vocabulary, recently-registered domains, no reciprocal links from known-good sites, and minimal organic search history. All four of those signals are true of any new product launch in the agent-payment category — including this one. The classifier is doing its job; the job was specified for a different threat model.
We are not a consumer payment site. We do not solicit funds from end users. We do not impersonate any bank or processor. We are a developer SDK + protocol, Apache-2.0 open source, with the entity behind it on the public record. The classifier cannot tell that from the domain alone — and that is the gap we are closing in writing here.
The entity behind this domain
| Field | Value |
|---|---|
| Operating entity | J&B Enterprise LLC |
| Verification | Entity documentation, tax documentation, payment-account verification, and authorized-signer proof are available to qualified buyers during vendor review. |
| Contact | info@getbizsuite.com |
What MnemoPay actually is
MnemoPay is the control and evidence layer for AI agents that handle money or consequential web actions. The open-source SDK governs authority and payment rails; the controlled browser runtime records supported interactive actions; the native browser exports operator inspection evidence for independent anchoring. The SDK is published under Apache-2.0 at github.com/mnemopay/mnemopay-sdk.
Phishing operations do not publish their own source code, attach their legal entity to it, and ship semantically-versioned release notes for two years. The classifier could not check those signals — you can.
Verify it yourself
1. Open-source code
155+ commits, Apache-2.0, semantic-versioned releases on npm.
github.com/mnemopay/mnemopay-sdk2. npm provenance
Live SDK on npm under the mnemopay user. Current stable v1.11.0.
npmjs.com/package/@mnemopay/sdk3. MCP Registry
Listed at the official Model Context Protocol Registry. DNS-authenticated publish.
registry.modelcontextprotocol.io5. Apple Developer presence
Active Apple Developer account, Team ID KGP4KJ59CP. Apple's identity verification confirms a real operator.
6. Stripe live
Stripe Payments live mode, KYB completed under J&B Enterprise LLC. Stripe terminates phishing accounts within hours.
mnemopay.com/pricing (live Stripe checkout)7. Knowledge graph
Live 971-page knowledge graph dogfooding @mnemopay/sdk/recall.
8. Hosted gateway
Health endpoint on the MnemoPay gateway. NameCheap CNAME → Fly Let's Encrypt cert.
api.mcp.mnemopay.com/health9. AugEngine
MnemoPay's flagship internal dogfood — the runtime behind a 12-20 min third-person narrative-action vertical slice that exercises our recall primitives in production. P0 gaps named honestly in the brief.
augengine.com/brief10. Browser evidence
Native Browser v0.2.0 case study, installer distribution, and independently checkable notary identity.
mnemopay.com/browserArchitecture, in one paragraph
Governed agent actions are signed with an Ed25519 keypair and recorded in a Merkle-chained audit bundle. Before an agent moves money, FiscalGate verifies the action against its Charter. For supported interactive web work, @mnemopay/browser records actions inside a controlled session. For human review, MnemoPay Native Browser performs verified inspection and exports signed evidence; its external gateway notary can sign a separate receipt after validating the browser's own signature. Direct WebView browsing is not represented as completely mediated evidence.
What we are doing about the flag
- Direct dispute filed with Scamadviser and IPQS — two written evidence packets have been sent with entity verification, public source links, registry links, and security-status evidence.
- This page — published at
mnemopay.com/trustso anyone landing on the Scamadviser warning can read the full story before forming an opinion. - Independent verification path — every claim above should resolve to an artifact you can check without trusting us: GitHub repo, npm registry, MCP Registry, PyPI, Stripe checkout, and live health endpoints.
- Ongoing correction — if a third-party classifier remains stale after the evidence review window, we continue escalation through the vendor's formal correction process.
If you are an enterprise buyer
Qualified buyers can request the verification packet during vendor review: entity documentation, tax documentation, payment-account verification, code-signing evidence, and a live technical walkthrough. Contact info@getbizsuite.com.
MnemoPay's commercial offer is on /pricing: free self-hosted SDK, $49/month Pro, $200/month Growth, $299/month Enterprise. Custom contracts with multi-region SLA on request.
Last word
We're building cryptographically-verifiable trust infrastructure for autonomous agents handling money. The fact that legacy reputation systems can't process that yet is the problem we are solving. If you want to verify everything we say above, every link on this page lands at an artifact you can audit independently. Don't trust us — trust the math, the public ledger, the published source code, and the entity on file with the State of Texas.
This page is updated whenever the dispute status changes. Last updated 2026-05-22.