PAYCOW / DOCUMENTATION

AI & developer tools

AI agent integration and related resources.

AI Agent Integration Prompt

Choose a prompt that matches the model's context and reasoning capacity

The full prompt gives large coding models the complete architecture. The compact prompt gives 5B-8B models one constrained implementation path so security rules remain visible throughout the task.

Full Architecture Prompt Large context models
Download .MD Download .TXT
View Prompt Content Click to expand
# PayCow Non-Custodial Crypto Payment Gateway
## Master AI Coding Agent Integration Blueprint

[Role & Directive for the AI Agent]
You are acting as the Principal Web3 & Payment Integration Architect. Integrate PayCow's Non-Custodial crypto payment gateway cleanly and securely.

PayCow is a Non-Custodial payment infrastructure:
- Monitors on-chain deposits and settles directly into merchant wallets
- Never holds private keys or custody of funds
- All API calls over HTTPS (https://paycow.net)
- Supports USDT (TRC20, ERC20, BEP20, POLYGON, ARBITRUM, AVAX) and USDC (ERC20, BEP20, POLYGON, ARBITRUM, BASE, AVAX)
- USDC is not supported on TRC20; USDT is not supported on BASE

Create Payment: POST https://paycow.net/api/payment/create
  Headers: x-api-key, x-api-secret, Idempotency-Key
  Body: { "amount": 50.00, "userId": "...", "network": "TRC20" }

Verify Payment (Pull): GET https://paycow.net/payment/data/:sessionId (public)
Verify Payment (Push): signed server-to-server webhooks

Webhook Setup:
1. Build a public HTTPS POST receiver that preserves the exact raw body.
2. Verify PayCow-Timestamp and PayCow-Signature using HMAC-SHA256.
3. Store event.id with a unique constraint and fulfill payment.paid exactly once.
4. Dashboard → Developer → Webhooks → save URL and copy the one-time whsec_ secret.
5. Send a test webhook and confirm a 2xx result in Delivery History.

Signature input: timestamp + "." + rawBody
Headers: PayCow-Event-Id, PayCow-Timestamp, PayCow-Signature
COMPACT SAFE PROMPT · 5B-8B

Less context. Fewer unsafe choices.

A shorter integration contract with a fixed build order, mandatory raw-body signature verification, database idempotency, atomic fulfillment, and ten focused security tests.

  • Stops and asks for four missing project facts
  • Forbids invented endpoints and frontend fulfillment
  • Uses one explicit webhook implementation path
Download .MD Download .TXT
View Compact Prompt Click to expand
# PayCow Compact Safe Integration Prompt

For small coding models (5B-8B).

Inspect the repository first. Keep the change small. Do not invent endpoints, fields, statuses, or event types.

Security rules:
- Keep every PayCow credential on the backend.
- Derive amount from trusted database data.
- Send a stable Idempotency-Key.
- Verify HMAC-SHA256 over timestamp + "." + exact rawBody.
- Store event.id under a unique database index.
- Fulfill only signed payment.paid events with PAID status.
- Make fulfillment atomic and exactly once.
- Never fulfill from browser polling or webhook.test.

Build order: database → backend service → checkout route → raw webhook receiver → dashboard test → focused security tests.