integrate-easypaisa
Skill8 starsChanged 3 months agoMITView on GitHub
Design, implement, review, and troubleshoot secure Easypaisa merchant payment integrations for Pakistani websites, mobile apps, and commerce platforms. Covers Easypaisa Mobile Account and OTC flows, approved hosted or direct integration methods, callbacks/postbacks, transaction verification, reversals, settlement, merchant reporting, plugins, reconciliation, onboarding, and production rollout. Use when adding Easypaisa payments, repairing an existing Easypay/Easypaisa gateway, migrating outdated code, or preparing a merchant integration for certification and launch.
In this repository8 other files it gives its agents.
- architect-backendSkill
- audit-backend-securitySkill
- improve-backend-codeSkill
- optimize-databaseSkill
- integrate-1billSkill
- integrate-jazzcashSkill
- integrate-stripeSkill
- screenshot-to-codeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 16 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If an integration exists, identify the guide/version it implements, enabled modes, environment, signing/canonicalization rules, endpoints, …
- Distinctive: line 15
If no integration exists, design it using the project's existing stack and the merchant's latest onboarding/integration pack.
- Distinctive: line 16
Never invent or copy credential names, request fields, endpoint URLs, hash ordering, algorithms, response codes, status values, or callback …
- Distinctive: line 22
Do not confuse the Online Payment Gateway with a personal wallet transfer, merchant QR/Till, payment link, bulk disbursement, bank card …
- Distinctive: line 28
Create an internal pending order with a unique merchant order/reference ID before starting payment.
- Distinctive: line 32
Treat the browser return as user experience only.
- Distinctive: line 35
Test in staging with approved cases and complete merchant certification/approval before live mode.
- Distinctive: line 39
Never expose merchant credentials or hash/signing keys in browser code, mobile apps, repositories, logs, screenshots, or errors.
- Distinctive: line 40
Never mark an order paid from query parameters, a success page, client JSON, SMS, screenshot, or redirect alone.
- Distinctive: line 41
Verify message integrity using the exact official canonicalization.
- Distinctive: line 43
Treat timeout or lost response as unknown—not failed—until verified.
- Distinctive: line 44
Use integer minor units or the exact decimal formatting required by the guide.
- Distinctive: line 45
Do not retry charge/payment creation blindly.
- Distinctive: line 46
Do not perform live payments, reversals, refunds, or credential changes without explicit approval.
- Very specific: line 50
Read references/integration-workflow.md for order states, hosted/mobile-account/OTC flows, callbacks, verification, plugins, and testing.
- Distinctive: line 51
Read references/security-and-operations.md before implementing signing, secrets, idempotency, reconciliation, monitoring, or production …
- Distinctive: line 52
Read references/research-notes.md for dated official sources, current public claims, community evidence, and details that must be …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Integrate Easypaisa
Build Easypaisa payments from the merchant's current approved integration guide, not from copied legacy snippets. Easypaisa documentation and enabled payment modes can differ by merchant agreement and environment.
First: detect the existing integration
Inspect the repository for Easypaisa/Easypay packages, plugins, gateway clients, merchant/store IDs, hash-key configuration, environment URLs, hosted checkout forms, mobile-account or OTC flows, return/callback/postback routes, transaction-status verification, reversal handling, order fields, settlement jobs, tests, and deployment secrets.
- If an integration exists, identify the guide/version it implements, enabled modes, environment, signing/canonicalization rules, endpoints, order lifecycle, and known failures. Repair it incrementally and preserve certified behavior.
- If no integration exists, design it using the project's existing stack and the merchant's latest onboarding/integration pack.
- Never invent or copy credential names, request fields, endpoint URLs, hash ordering, algorithms, response codes, status values, or callback rules. Verify each against current merchant documentation and test vectors.
Confirm the product and merchant eligibility
Official Easypaisa material currently advertises Online Payment Gateway onboarding for a business/entity with a live website or mobile app, subject to application, documentation, KYC/due diligence, and integration. Publicly listed modes include Easypaisa Mobile Account and OTC; plugins are listed for WooCommerce, OpenCart, Magento, and PrestaShop. Actual enabled modes, fees, settlement, limits, and technical contracts must come from the merchant agreement.
Do not confuse the Online Payment Gateway with a personal wallet transfer, merchant QR/Till, payment link, bulk disbursement, bank card acquirer, escrow, or recurring-subscription engine. Confirm the required Easypaisa product before coding.
Workflow
- Obtain the latest merchant integration guide, sandbox/staging details, approved payment modes, credentials, test accounts/data, signature examples, callback rules, status/reversal APIs, certification cases, settlement terms, and production cutover pack.
- Record the exact guide/API/plugin version and compare it with existing code.
- Create an internal pending order with a unique merchant order/reference ID before starting payment.
- Calculate product, quantity, amount, currency, discounts, delivery, and customer ownership on the server. Never accept authoritative payment values from the client.
- Generate the request and integrity value exactly from the documented fields, order, encoding, and algorithm. Keep signing secrets server-side.
- Send customers only through the contracted hosted/direct/mobile-account/OTC flow. Use HTTPS return and server-notification URLs.
- Treat the browser return as user experience only. Verify and deduplicate the server callback/postback, then confirm ambiguous outcomes with the approved status mechanism or merchant portal.
- Fulfill once after server-side verification. Record transaction, order, channel, status, and settlement identifiers for support and reconciliation.
- Implement failure, cancellation, timeout, duplicate, delayed callback, reversal, refund where supported, and settlement-mismatch paths.
- Test in staging with approved cases and complete merchant certification/approval before live mode.
Non-negotiable rules
- Never expose merchant credentials or hash/signing keys in browser code, mobile apps, repositories, logs, screenshots, or errors.
- Never mark an order paid from query parameters, a success page, client JSON, SMS, screenshot, or redirect alone.
- Verify message integrity using the exact official canonicalization; timing-safe comparison is required where the application compares digests.
- Enforce unique order and external transaction identifiers and make fulfillment idempotent.
- Treat timeout or lost response as unknown—not failed—until verified.
- Use integer minor units or the exact decimal formatting required by the guide; never binary floating point.
- Do not retry charge/payment creation blindly.
- Do not perform live payments, reversals, refunds, or credential changes without explicit approval.
Reference routing
- Read references/integration-workflow.md for order states, hosted/mobile-account/OTC flows, callbacks, verification, plugins, and testing.
- Read references/security-and-operations.md before implementing signing, secrets, idempotency, reconciliation, monitoring, or production rollout.
- Read references/research-notes.md for dated official sources, current public claims, community evidence, and details that must be re-verified.
Verification and output
Run relevant formatter, static analysis/type checking, tests, and builds. Report whether Easypaisa was found or added from scratch, the product/modes and guide version used, flows implemented, callback verification, idempotency, transaction-status recovery, reconciliation, certification status, and remaining merchant-portal configuration. Clearly separate public research, merchant-provided specifications, staging evidence, and live approval.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

