Merchant page
Your existing Pay with MARCO control.
Keep your own product page and checkout. When a customer chooses MARCO, send them to a verified MARCO-hosted payment and receive the result on your server.
Your product, pricing and order flow remain unchanged.
Representative current flow · no embedded payment terminal
Your existing Pay with MARCO control.
MARCO shows the verified order and opens the user's wallet.
The transfer is confirmed on-chain before the payment completes.
The browser returns to the validated merchant website.
The hosted checkout prepares the verified MARCO token transfer for the user's wallet.
Amount, currency, order reference and receiver stay under registered server authority.
A browser click cannot mark an order paid. MARCO completes only after verified chain proof.
Connect is complementary, not required. A Passport can be recognised during checkout, but payment remains available without one. The checkout does not claim fiat settlement, additional tokens or additional payment networks.
M-Credits on an eligible verified purchase when the payer wallet is recognised to a Passport.
Partner reward under the current MARCO Pay model. Eligibility and attribution are checked from stored payment truth.
Every badge reflects a live check of the MARCO runtime. Nothing here is decorative.
Last verification Never · Reports published by Melega Space.
Your server creates the payment at /api/public/pay/session using the registered application, timestamp and signature headers. The response supplies the approval URL used by your Pay with MARCO control.