Payment API and administration
GoPay Merchant QRIS Gateway
Connect QRIS payment requests, payment matching, and order updates. Unofficial and not affiliated with or endorsed by GoPay.
Outcome
Combines dynamic QRIS payments, transaction matching, signed webhooks, and a separate administration service.
My role
Open-Source Developer
How I helped
- Built and published the open-source project.
Product
The workflow in context
Generated product visualization, not a live screenshot.
The solution
Connect QRIS payment requests, payment matching, and order updates. Unofficial and not affiliated with or endorsed by GoPay.
What changed
Combines dynamic QRIS payments, transaction matching, signed webhooks, and a separate administration service.
Source
This project uses unofficial private APIs. Accounts risk suspension; use official payment providers for critical production workloads.
AI system implementation
No AI model participates in payment creation or settlement. TypeScript code generates QRIS payloads, matches transactions, and signs webhooks; SQLite tracks state and prevents duplicate claims. The SvelteKit admin service stays separate from the gateway. Payment decisions rely on validated amounts and transaction records, not probabilistic model output.
Could a similar approach help your business?
Tell me where work gets stuck. We can identify a practical first improvement and what success should look like.
Discuss your challenge