Subproject Roadmap

MAKO PayFlow — Payment Collection (PayFlow Collect)

Last Updated: October 21, 2026 at 08:55 PM EDT

Source POA&M last reviewed (docs/MAKO-PAYFLOW-POAM-V1.md): 2026-10-20 20:51 EDT

A standalone payment-collection utility any MAKO tool can use to accept payment for its services — MAKO directly on Loop Network, or BNB on BSC delivered to the deployer wallet as MAKOv2 through MAKO's real MAKOv2 bridge adapter — always deposited to the deployer wallet. Built by the MAKO Posse Team as its own project; a separate SDK Integration Document is the handoff artifact for any team wiring a utility to it, starting with the MAKO Web Team's own tools.

Shelved by the operator on 2026-10-10 (YELLOW). This payment-collection design is now called PayFlow Collect and is not PayFlow V1; it stays a separate future module and reopens only if a MAKO utility asks to charge through PayFlow and the operator says so. No milestone below is being worked. PayFlow's active work is tracked in the PayFlow V2 roadmap, which is PayFlow's registered plan since 2026-10-14. This page is a shelved record of the earlier plan (14 milestones, corrected 2026-09-12 and republished 2026-10-04). Integration into any specific utility is a separate, later effort owned by the consuming team.

Design correction (2026-09-12)

PayFlow accepts payment two ways: directly in MAKO on Loop Network (a trivial deposit to the deployer wallet), or in BNB on BSC, which is collected, swapped for MAKOv2 on BSC, and delivered one-way (BSC to Loop) through the real MAKOv2 bridge adapter. The original design needed a separate attestation contract and a capped escrow-release contract; both were removed, not deferred on 2026-09-12, because the real adapter already provides what was needed. A $5 USD-equivalent per-transaction cap applies, adjustable by the operator, and the recipient is always the deployer wallet. BNB-side payment collection reuses the quote, pay, independently-re-verify pattern already live in production for Contract Scan and Wallet Trace.

Milestones

M1
Project DescriptionPayment model, two-path architecture, the $5 cap, and what is reused versus new — confirmed. Done 2026-08-17.
Done
M2
SDK Integration Document (v1)The API contract (quote / confirm / status / config) a consuming team builds against; v1 is design-stage. Done 2026-08-17.
Done
M3
POA&MTracks PayFlow's own build, milestones, and completion gate. Done 2026-08-17.
Done
M4
Main roadmap updatedPayFlow added as stage 1 on the main Development Roadmap; the earlier Bridge Wizard items moved to the hold list. Done 2026-08-17, live and verified.
Done
M5
This page publishedThe PayFlow subproject roadmap. Done 2026-08-17, live and verified.
Done
M6
Design correctionEscrow and attestation model replaced by direct reuse of the real MAKOv2 bridge adapter; the attestation and escrow-release contracts were removed, not deferred. Done 2026-09-12.
Done
M7
BNB payment-collection backendPath A and the shared Path B collection logic, reusing the Contract Scan and Wallet Trace pattern.
M8
Path A shippable independentlyDirect MAKO deposit, with no external blocker.
M9
Blocked: BSC MAKOv2 pool pairing decidedExternal dependency, tracked in the MAKO Liquidity Pools project.
Blocked — external
M10
Bridge Wizard V8 deployedVerified on-chain 2026-10-04: the MAKOv2 BSC token and adapter registry is live, with a nonzero approved ceiling. PayFlow's own live-validation of V8 is still unverified separately.
Done
M11
Path B integration glueSwap trigger plus the adapter call, once M9 and M10 clear.
M12
Site5 deploymentStandalone hosting, with the same PHP/cron-driven constraints as the existing MAKO Website utilities.
M13
Real end-to-end testOne real, small-value test, Path A first and Path B once unblocked. Go-live gate: the operator's own explicit words, not an inferred pass.
M14
SDK Integration Document finalizedFinalized against the real, deployed API (v1 is design-stage).

PayFlow V2 — Buy LOOP

A separate feature on the same project: a user buys BSC-native LOOP with BNB, instantly or through dollar-cost averaging, with a 1% fee to the deployer. The BNB-to-LOOP part is built and tested locally; nothing is deployed, and the scope was widened on 2026-10-05. V1's milestones and blockers above are unaffected by V2's status either way.

PayFlow V2 roadmap →

Relationship to MAKO Web

PayFlow is built and owned by the MAKO Posse Team as a standalone project — it does not live inside the MAKO Website repository and is not integrated into any utility by this team. Once the SDK Integration Document is finalized against a real, deployed API (M14 above), wiring it into Contract Scan, Wallet Trace, or any future utility is the MAKO Web Team's own responsibility, tracked in that team's own integration POA&M — following the same pattern already used for Contract Scan's own MAKO Web integration.

← Back to Development Roadmap

MAKO Posse Team is responsible for keeping this POA&M and all milestone status current.