Chargekit Chargeback Integration Tool
Budget: $750 – $1,500 USD
I’m developing a new SaaS called Chargekit to keep chargebacks under control, and I need a developer who can connect the platform directly to major payment services. The core objective is straightforward: make chargeback data flow seamlessly into Chargekit so my team has everything in one place without manual uploads.
Scope of work
• Build secure API connectors that listen for chargeback-related webhooks and events from at least one mainstream payment platform (PayPal, Stripe, Square, or another you recommend).
• Normalize the payloads and insert them into our PostgreSQL database while preserving every dispute field.
• Expose a REST/GraphQL endpoint so the front-end team can query disputes by status, reason, and date range.
• Include basic authentication (JWT) plus role scaffolding, leaving room for Administrator, Customer Support, and Finance Manager profiles.
• Provide a concise setup guide and Postman collection so I can reproduce the integration in staging.
Tech preferences
The back-end is entirely up to you—Node.js, Python (FastAPI), or a similar modern framework are all acceptable as long as the code is readable and well-documented. Database migrations should be handled with an industry-standard tool (e.g., Prisma, Alembic). Dockerization is a plus because it simplifies deployment to AWS.
Deliverables
1. Source code in a private Git repo.
2. Documentation covering environment variables, database schema, and webhook testing steps.
3. A short demo video or live walkthrough proving chargeback records move end-to-end from the payment provider into the database.
This is a focused, mid-sized build: I’m not expecting a polished front-end yet, just the working integrations and clean, maintainable code that lets my team layer on the UI later. If you’ve built payment platform connectors before, I’d love to see an example of your work when you apply.
Scope of work
• Build secure API connectors that listen for chargeback-related webhooks and events from at least one mainstream payment platform (PayPal, Stripe, Square, or another you recommend).
• Normalize the payloads and insert them into our PostgreSQL database while preserving every dispute field.
• Expose a REST/GraphQL endpoint so the front-end team can query disputes by status, reason, and date range.
• Include basic authentication (JWT) plus role scaffolding, leaving room for Administrator, Customer Support, and Finance Manager profiles.
• Provide a concise setup guide and Postman collection so I can reproduce the integration in staging.
Tech preferences
The back-end is entirely up to you—Node.js, Python (FastAPI), or a similar modern framework are all acceptable as long as the code is readable and well-documented. Database migrations should be handled with an industry-standard tool (e.g., Prisma, Alembic). Dockerization is a plus because it simplifies deployment to AWS.
Deliverables
1. Source code in a private Git repo.
2. Documentation covering environment variables, database schema, and webhook testing steps.
3. A short demo video or live walkthrough proving chargeback records move end-to-end from the payment provider into the database.
This is a focused, mid-sized build: I’m not expecting a polished front-end yet, just the working integrations and clean, maintainable code that lets my team layer on the UI later. If you’ve built payment platform connectors before, I’d love to see an example of your work when you apply.