Some of our successful payments are not leaving a trace in the database. I’m using a custom Axis Bank payment gateway integration and have confirmed that it’s the transaction records themselves—not customer details or status flags—that occasionally fail to save. The problem has been visible for over a month, so I need a thorough audit as well as a clean fix, not a temporary patch. You’ll start by reviewing the current callback/response flow, tracking how data moves from the Axis Bank API through to the insert statement. I expect you to pinpoint where records are being dropped, harden that logic, and add any missing error-handling or idempotency checks so every approved payment reliably lands in the transactions table. Deliverables: • Updated gateway code with the skip issue resolved • SQL or migration script if schema tweaks are required • Log or monitoring hook showing each payment’s journey from gateway response to database row • Brief read-me summarising the root cause, changes made, and how to test Please bring solid experience with payment gateways and database troubleshooting so we can get this live quickly and finally trust our numbers again.