Project description
We run an online store and take card payments through a payment gateway, but matching incoming transactions with orders in our accounting system is still done by hand. Every day someone opens the settlement report and compares it against the order list line by line, trying to figure out which payment belongs to which order. It takes hours, and mistakes happen: a payment gets attached to the wrong order, or sits unmatched for weeks before anyone notices.
We need a script or small tool that regularly pulls transactions from the gateway, either through its reporting interface or by importing the settlement file, and automatically matches each transaction to the right order by order number, amount and date, with reasonable tolerance for small timing differences. Matched pairs should be marked closed. Anything unmatched — amount mismatches, duplicate charges, payments with no order, orders never paid — must go into a separate list for our accountant.
The result should run unattended on a schedule and leave a readable discrepancy report plus a log of what was matched and when. Open to Python or PHP, whichever suits our stack; describe your approach and give an estimate first.
What matters most:
— reliable matching with configurable tolerances
— a clear report of unmatched payments
— correct handling of duplicate and refunded transactions
We need a script or small tool that regularly pulls transactions from the gateway, either through its reporting interface or by importing the settlement file, and automatically matches each transaction to the right order by order number, amount and date, with reasonable tolerance for small timing differences. Matched pairs should be marked closed. Anything unmatched — amount mismatches, duplicate charges, payments with no order, orders never paid — must go into a separate list for our accountant.
The result should run unattended on a schedule and leave a readable discrepancy report plus a log of what was matched and when. Open to Python or PHP, whichever suits our stack; describe your approach and give an estimate first.
What matters most:
— reliable matching with configurable tolerances
— a clear report of unmatched payments
— correct handling of duplicate and refunded transactions
Web programming Cash, Bank transfer
