How We Tamed Bank Callbacks in PDP
In PDP, we added digital signature verification for callbacks from the acquiring bank: first we check that the response is authentic, then we update the payment status. This helps us avoid mixing up successful payments with technical failures.
In PDP, we built something that fintech basically can’t do without anymore: digital signature verification for callbacks from the acquiring bank. Now we check every bank response for authenticity first, and only then update the payment status.
Why go to all this trouble? Because callbacks play by their own rules: one day they arrive, the next they get lost somewhere between services, like a notification on Monday morning ☕️ And if the bank confirmed the transaction but the callback never made it to us, we added a separate status — “paid with an error.”
This helps us avoid confusing genuinely successful payments with technical failures and resolve edge cases faster. With growing demands for security and reliability in payment integrations, this is no longer a feature — it’s the baseline.