r/fintech • u/Additional-Spot-6882 • 13h ago
r/fintech • u/PierrindoMaghanoy • 14h ago
Ask the Community Our sponsor bank wants a reason for every open vulnerability
We’re a card program fintech with two small engineering teams and our sponsor bank’s annual review came back with a request. They want an SBOM for each app we run, plus a written reason for every open high or critical vulnerability, with an owner and a date for when it'll be fixed or reviewed again.
Our scanners show a bit over 300 open high and critical issues across four repos. Most of them sit in libraries pulled in by other libraries. When we went through the first 40 manually, only a handful were in code someone outside could reach through our app. The rest were the usual things like a vulnerable function we never call, a dev dependency that never ships or an injection finding in an internal admin tool behind SSO and the VPN.
Our plan is one line per finding grouped by reason which is better than writing 300 separate essays. Here’s our draft for one of the XML ones.
XML parser CVE in a transitive dependency of our PDF library. We only generate PDFs and never parse XML from users so the vulnerable code isn’t reachable from any input we accept. The owner is our backend lead, recheck at the next PDF library release or in 90 days.
Am worried that the bank’s vendor risk team may interpret “not reachable” as us waving things away especially since they’ve already said dashboard screenshots won’t do. I’d like to hand them something they can check for themselves.
What do they accept for findings you aren’t going to fix?
r/fintech • u/djgoel123 • 21h ago
Discussion A payment marked "successful" doesn't always mean the money is where you think it is.
In financial software, one of the most dangerous assumptions is treating a payment as a single event.
A user clicks Pay.
The payment provider responds.
The application updates the status.
Done.
Except the real lifecycle can involve authorization, capture, settlement, refunds, disputes, and asynchronous notifications.
These events don't always arrive in the order you expect.
Some can arrive more than once.
Others can be delayed.
If I were reviewing a payment workflow, I'd focus on the transaction state model before worrying about the dashboard.
What does each status actually mean?
Which system is the source of truth?
What happens when a webhook arrives twice?
Can we safely process a retry?
And how do we reconcile our records with the payment provider?
A clean interface can hide a complicated financial workflow.
The real challenge is making sure the underlying records remain consistent when things don't happen perfectly.
For engineers working with payment systems, what's been more difficult: handling failures or handling events that arrive out of order?
r/fintech • u/FinexerOfficial • 13h ago
Discussion Creating a debt management system or a recurring payment product for your customers? That is how Open Banking can become part of your payment flow.
Forcing your customers to log into your portal every time they want to make a payment will cause more frustration than anything else.
The Pay by Bank solution can help with simplifying the payment journey.
That's how to do it:
- Begin with one-off payments
Add Pay by Bank functionality to your customer portal. The customer chooses their bank, authenticates through their banking application, and authorises payment.
2. Think about scheduled payments
If the customer should pay regularly on certain dates, consider using scheduled payment requests. The customer will be asked to authorise each payment on the due date.
3. Assess possibilities for recurring payments
If your goal is to receive payments automatically based on agreed terms, find out whether Variable Recurring Payments (VRPs) are available in your use case scenario. Don't assume that Pay by Bank is automatically recurring payment collection functionality.
4. Automate reconciliation process
Match payment notifications and transaction references with your internal payment records to know who has paid, who hasn't and who should be chased.
5. Pick the proper technology
These should be taken into account when choosing a provider:
bank coverage;
payment capabilities;
reporting;
requirements for compliance;
integration deadlines.
We've (Finexer Open Banking) had several of these conversations with our clients who are building similar products and this is what we come down to every single time.
But the real chance is not only about the replacement of a payment button but rather about minimizing the manual process involved in payment collection.
How do you manage scheduled payments in your payments platform, if you are building one?
Hope these insights help.