domain: peecho.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Peecho test (or production) account and locate your merchant_api_key and product offering_id under Dashboard > Settings.
Set your business address under Dashboard > Settings > API > Company details, since tax is calculated partly from your company's location.
POST to https://test.www.peecho.com/rest/v3/order/ (or the production host) with merchant_api_key, purchase_order, currency, an item_details array (item_reference, offering_id, quantity, file_details), and address_details with a shipping address.
Either supply file_details.content_url at order-creation time, or leave it blank and attach files afterward via the Set files asynchronously endpoint.
After creation the order is in the Open state; capture the returned orderId, then call the Payment endpoint with the orderId and a SHA-256-encoded secret to submit it to production.
Known gotchas
Test and production environments use completely separate merchant_api_key and offering_id values — mixing them causes the order to fail.
Submitting payment requires purchased credits in your Peecho account (test credits/test cards in sandbox) — an order stays in Open state indefinitely without a successful Payment call.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?