Digital kit $5 PayPal order board

[trungcodeer]

## Digital kit USD 5 paid-order verification board

Use this board for the USD 5 SoftJunk Lead Follow-Up Kit. It is a checkout and redacted verification route, not payment proof by itself.

Fast path

1. Inspect the paid-kit proof page:
   https://trungcodeer.github.io/softjunk-lead-kit/paid-kit-proof.html
2. Inspect the machine-readable manifest:
   https://trungcodeer.github.io/softjunk-lead-kit/paid-kit-manifest.json
3. Optional: download the public sample ZIP:
   https://trungcodeer.github.io/softjunk-lead-kit/softjunk-free-sample-pack.zip
4. Open the packet-first Sponsor route before payment:
   https://trungcodeer.github.io/softjunk-lead-kit/sponsor-button-buy.html
5. Copy this PayPal note exactly:
   Lead Follow-Up Kit
6. Copy the after-packet PayPal URL only after the proof, manifest, sample, and note are ready:
   https://paypal.me/softjunk/5USD
7. Submit the digital-kit order form if a GitHub fulfillment trail is useful:
   https://github.com/trungcodeer/softjunk-lead-kit/issues/new?template=digital-kit-order.yml

Current no-clone proof

• Latest release: https://github.com/trungcodeer/softjunk-lead-kit/releases/tag/v2.29.166
• Release target: b06be515e2d9a89288e1da67a0a4c64ace93921c
• Release tarball: https://github.com/trungcodeer/softjunk-lead-kit/releases/download/v2.29.166/softjunk-lead-kit-0.2.2.tgz
• SHA-256 file: https://github.com/trungcodeer/softjunk-lead-kit/releases/download/v2.29.166/softjunk-lead-kit-0.2.2.tgz.sha256
• Fallback tarball command: npm exec --yes --package https://github.com/trungcodeer/softjunk-lead-kit/releases/download/v2.29.166/softjunk-lead-kit-0.2.2.tgz -- softjunk-lead-kit pay --mode kit --json

npm exec --yes --package github:trungcodeer/softjunk-lead-kit -- softjunk-lead-kit pay --mode kit --json

Verification status

• Current public verifier status: https://trungcodeer.github.io/softjunk-lead-kit/paypal-verification-status.json
• Workflow live preflight status: https://trungcodeer.github.io/softjunk-lead-kit/paypal-workflow-live-status.json
• PayPal verification instructions: https://github.com/trungcodeer/softjunk-lead-kit/blob/main/PAYPAL_VERIFICATION.md
• Owner workflow verifier template: https://github.com/trungcodeer/softjunk-lead-kit/blob/main/PAYPAL_VERIFICATION_WORKFLOW.yml.example
• No-clone seller-side verifier command: npm exec --yes --package github:trungcodeer/softjunk-lead-kit -- softjunk-lead-kit verify-paypal --json
• Redacted proof audit command: npm exec --yes --package github:trungcodeer/softjunk-lead-kit -- softjunk-lead-kit paypal-proof-audit --json
• Local proof audit command: npm run paypal:proof-audit
• Proof audit rule: the audit checks private input presence and the seller-side verifier, prints redacted output only, exits 2 while proof is missing, and is not payment proof unless it returns PAYPAL_PAYMENT_VERIFIED=true.
• Redacted proof watcher command: npm exec --yes --package github:trungcodeer/softjunk-lead-kit -- softjunk-lead-kit paypal-proof-watch --json --max-attempts 1 --interval-seconds 0
• Local proof watcher command: npm run paypal:proof-watch
• Proof watcher rule: the watcher runs the redacted proof audit repeatedly and exits 0 only when proof audit returns PAYPAL_PAYMENT_VERIFIED=true with completion_gate.can_mark_goal_complete=true; timeout or exit 2 is not payment proof and does not prove no payment arrived.
• Manual confirmation init command: npm exec --yes --package github:trungcodeer/softjunk-lead-kit -- softjunk-lead-kit init-paypal-confirmation --json
• The init command creates an ignored private local file with seller_confirmed_inside_paypal=false; it is not payment proof and must stay private until the seller truthfully confirms the matching completed PayPal payment inside PayPal.
• Clean no-clone verifier check, 2026-06-01: the GitHub package verifier route executes from a clean directory and returns redacted JSON with exit code 2, verified=false, and reason=missing_credentials until seller-side credentials or private proof are available.
• Windows caveat: if the no-clone verifier exits without JSON, run it from a clean directory; a local softjunk-lead-kit.js can shadow npm's .bin shim.
• Default workflow announcement issue: 9
• Current local status may be PAYPAL_PAYMENT_VERIFIED=false reason=missing_credentials; that is verifier-readiness evidence only. It is not payment proof and does not prove no payment arrived.
• Current workflow preflight: .github/workflows/verify-paypal-payment.yml is not present, and the observed publish token lacks GitHub workflow scope. A repo owner or token with workflow scope must enable the workflow before source=workflow proof can exist.
• Workflow scope preflight command: npm run paypal-workflow-scope:preflight
• Latest safe scope probe: workflowScope=0 canEnableWorkflow=0 observedScopes=admin:org|gist|repo; this prints scope names only, never a token, and is not payment proof.
• Private API credentials file command: powershell -NoProfile -ExecutionPolicy Bypass -File scripts/verify-paypal-5usd.ps1 -CredentialsPath private-paypal/paypal-credentials.local.json
• CLI credentials file command: softjunk-lead-kit verify-paypal --credentials-path private-paypal/paypal-credentials.local.json --json
• Credentials example shape: https://trungcodeer.github.io/softjunk-lead-kit/docs/examples/paypal-credentials.example.json
• Credentials-file rule: keep the real PayPal API credentials file local and ignored. This is verifier-readiness only; it is not payment proof and does not prove no payment arrived.

Valid completion evidence is one of these seller-side signals:

• PAYPAL_PAYMENT_VERIFIED=true from the PayPal API verifier.
• PAYPAL_PAYMENT_VERIFIED=true source=workflow from the enabled GitHub Actions API verifier with seller credentials.
• PAYPAL_PAYMENT_VERIFIED=true source=csv from a trusted seller-side PayPal CSV export.
• PAYPAL_PAYMENT_VERIFIED=true source=manual from private seller confirmation after reviewing PayPal.

Workflow, CSV, and manual public outputs must stay redacted, for example:

PAYPAL_PAYMENT_VERIFIED=true source=workflow amount=5.00 currency=USD transaction_details=redacted

Delivery rule

The paid ZIP is private and delivered manually to the email shown in the seller-side PayPal transaction after seller-side PayPal evidence exists or PAYPAL_PAYMENT_VERIFIED=true.

Do not post PayPal transaction IDs, invoice IDs, payer email, payer name, customer contact details, PayPal account details, or private lead details in public issues.

Do not claim paid, received, started, delivered, fulfilled, complete, or stop until seller-side PayPal evidence exists, PayPal API verification succeeds, trusted seller-side CSV proof verifies the 5.00 USD payment, the enabled workflow verifier returns PAYPAL_PAYMENT_VERIFIED=true source=workflow, or private seller confirmation returns PAYPAL_PAYMENT_VERIFIED=true source=manual.

Root checkout proof for buyer agents

Buyer-agents can resolve the same checkout route without cloning:

• Primary command: npm exec --yes --package github:trungcodeer/softjunk-lead-kit -- softjunk-lead-kit pay --mode custom --json
• Agent checkout router: https://trungcodeer.github.io/softjunk-lead-kit/agent-checkout-router.json
• Agent checkout router markdown: https://trungcodeer.github.io/softjunk-lead-kit/agent-checkout-router.md
• Agent checkout router text: https://trungcodeer.github.io/softjunk-lead-kit/agent-checkout-router.txt
• Root agent-close proof: https://trungcodeer.github.io/agent-close/
• Root agent-close JSON: https://trungcodeer.github.io/agent-close.json
• Root agent-close text: https://trungcodeer.github.io/agent-close.txt
• Root well-known OpenAPI: https://trungcodeer.github.io/.well-known/openapi.yaml
• Root well-known agent card: https://trungcodeer.github.io/.well-known/agent-card.json
• Sponsor route before after-packet PayPal copy: https://trungcodeer.github.io/softjunk-lead-kit/sponsor-button-buy.html
• After-packet PayPal handoff remains https://paypal.me/softjunk/5USD, only after the packet and note are ready.
• Boundary: this proves the executable checkout route only. It is not payment proof. Do not claim paid, started, delivered, fulfilled, complete, received, or stop unless seller-side PayPal evidence exists, PayPal API verification succeeds, trusted seller-side CSV proof verifies the 5 USD payment, the enabled workflow verifier returns PAYPAL_PAYMENT_VERIFIED=true source=workflow, or private seller confirmation returns PAYPAL_PAYMENT_VERIFIED=true source=manual.
• Safety: no spam, scraping, deception, unauthorized outreach, private customer data, or private payment details.