Most work is engineering in your repo; owners mainly supply secrets, URLs, and approvals. Download the .txt or copy the box below — it pairs one human checklist with only the AI prompts that are usually hard to write (status summary + completion note).
Download
Same text as below — save as payshare-ai-handoff.txt and attach to your AI or repo.
Human prerequisites: production PayShare base URL https://payshare2.vercel.app; partner dashboard access to copy credentials; canonical HTTP contract docs/14-INTEGRATION-CONTRACT.md in your repo clone (or export).
PayShare Mode 2 — integration handoff
=== What you (the business / operator) need to do ===
1. Have or create access to the PayShare partner dashboard (register when self-serve signup is enabled, or use credentials from your PayShare operator).
2. Open My setup (or equivalent after provisioning) and copy integration id, API base URL, API key, and webhook signing secret when PayShare shows them. Store values only in your secrets manager / deployment env / password manager — never commit them or paste them into frontend code.
3. Confirm whether your integration should use test or live sessions for now; align with dashboard Settings and operator policy before sending real customer traffic.
4. Add the production and staging URL prefixes PayShare may redirect users back to (success and cancel flows) to the return URL allowlist in Partner Settings.
5. Provide a stable public HTTPS URL that reaches your backend webhook route; enter it in Partner Settings / the integration wizard so PayShare can deliver signed events.
6. Coordinate with whoever maintains your PSP/booking stack so record-payment calls use stable external references from your payments layer (mapping details stay in your systems).
7. When ready, run the partner Integration wizard self-test (and staging checks per docs/15-INTEGRATION-SELF-TEST.md). Enable live session creation only when policy and readiness checks allow.
8. Keep docs/14-INTEGRATION-CONTRACT.md (from your repo clone or an export from the operator) available for whoever implements the HTTP calls.
=== AI prompt helper (writing only; no coding) ===
Use these only when you need wording help.
Prompt 1: What should our status summary look like?
You are assisting a non-technical business owner.
Task:
- Write a short "Status summary" I can send to my developer.
- Keep it plain English and concrete.
- Mention only business/operator facts I provide (do not invent technical details).
Output format:
1) One paragraph (max 6 lines) with current status.
2) Bullet list "Still needed from us" (max 5 bullets).
3) Bullet list "Questions for developer" (max 5 bullets).
Important rules:
- Do NOT write code.
- Do NOT suggest editing files yourself.
- If info is missing, call it out clearly as "unknown".
Prompt 2: What should our completion/update note look like?
You are assisting a non-technical business owner.
Task:
- Draft a "completion/update note" after a developer says work is done.
- Help me confirm what was actually completed and what is still open.
Output format:
1) "What was completed" (max 6 bullets).
2) "How to verify" (max 5 bullets, plain language).
3) "What remains / risks" (max 5 bullets).
4) "Message to send back to developer" (short paragraph I can copy).
Important rules:
- Do NOT write or change code.
- Do NOT assume completion if evidence is missing.
- Mark unclear items as "needs confirmation".
What you need to do
Same numbered list as in the downloadable file — for owners and operators, not code.
Have or create access to the PayShare partner dashboard (register when self-serve signup is enabled, or use credentials from your PayShare operator).
Open My setup (or equivalent after provisioning) and copy integration id, API base URL, API key, and webhook signing secret when PayShare shows them. Store values only in your secrets manager / deployment env / password manager — never commit them or paste them into frontend code.
Confirm whether your integration should use test or live sessions for now; align with dashboard Settings and operator policy before sending real customer traffic.
Add the production and staging URL prefixes PayShare may redirect users back to (success and cancel flows) to the return URL allowlist in Partner Settings.
Provide a stable public HTTPS URL that reaches your backend webhook route; enter it in Partner Settings / the integration wizard so PayShare can deliver signed events.
Coordinate with whoever maintains your PSP/booking stack so record-payment calls use stable external references from your payments layer (mapping details stay in your systems).
When ready, run the partner Integration wizard self-test (and staging checks per docs/15-INTEGRATION-SELF-TEST.md). Enable live session creation only when policy and readiness checks allow.
Keep docs/14-INTEGRATION-CONTRACT.md (from your repo clone or an export from the operator) available for whoever implements the HTTP calls.
AI prompt: status summary
Use when you want the AI to draft a plain-English update for your developer.
You are assisting a non-technical business owner.
Task:
- Write a short "Status summary" I can send to my developer.
- Keep it plain English and concrete.
- Mention only business/operator facts I provide (do not invent technical details).
Output format:
1) One paragraph (max 6 lines) with current status.
2) Bullet list "Still needed from us" (max 5 bullets).
3) Bullet list "Questions for developer" (max 5 bullets).
Important rules:
- Do NOT write code.
- Do NOT suggest editing files yourself.
- If info is missing, call it out clearly as "unknown".
AI prompt: completion/update note
Use after a developer says work is done; this helps you ask for proof and remaining risks.
You are assisting a non-technical business owner.
Task:
- Draft a "completion/update note" after a developer says work is done.
- Help me confirm what was actually completed and what is still open.
Output format:
1) "What was completed" (max 6 bullets).
2) "How to verify" (max 5 bullets, plain language).
3) "What remains / risks" (max 5 bullets).
4) "Message to send back to developer" (short paragraph I can copy).
Important rules:
- Do NOT write or change code.
- Do NOT assume completion if evidence is missing.
- Mark unclear items as "needs confirmation".