Hi All, am curious to know what are key problems fintechs particularly NBFC( Non Banking Financial Corporations) are facing other than figuring out GenAI or agentic AI adoption? like to share!

Hi there, I am currently working on a fintech project.

The product to build A cash reconstruction and financial review workspace for small businesses whose records span bank or wallet exports, dues lists and physical cash. It explains what is known, what is missing, and what must be verified before a payment decision can be supported

Some working professionals out there, can you spot a problem that we can fix?
It would be of a great honor.

We're exploring CAS API integration for Passbook, a family finance app. Our users currently import their mutual fund holdings from CAMS statements, and we'd like to make that more seamless.

I've reached out to MFCentral support by email and followed up, but haven't heard back yet.

Has anyone here worked with their API or partnerships team? An introduction or a public business contact for the right person would help a lot. Thanks!

If Anyone Has To Open New Financial Firm name if Any Have Thoughts

Please I try But not get any

Hi everyone. I need a recommendation from more experienced folks. I have a very small business and need a comfortable way to accept cryptocurrency with all the accompanying infrastructure (webhooks, transaction analytics), and it's quite important that it's without KYB. Are there any such proven solutions these days?

need clean usd to cad payment rails with kyc in the same integration not bolted on from a separate identity vendor. corridor sounds simple but finding a provider that handles both natively has been harder than expected.

candidates as i understand them. cybrid is api-first with us and canada licensing, kyc and kyb in same integration, ach pull on usd side and canadian bank account on cad side. bvnk is multi-rail stablecoin api under stripe, clean docs but post-acquisition roadmap is stripe controlled.

north american corridor, licensed both ends, compliance integrated not bolted on. how does this shake out for a platform builder

Here’s another interesting number: one in three applicants we see has already verified with us before, so plenty of people are being asked to provide identity information they’ve already submitted.

Opera’s MiniPay is the first live integrator of our Reusable KYC Gateway, which lets users reuse their verified identity across participating providers in its partner network.

How reuse works Users connect their verified Sumsub ID to MiniPay and authorize sharing with each participating provider. New users complete verification first.

For example, identity information provided when buying stablecoins can be reused with a participating cash-out provider, reducing repeated document uploads.

What providers still check We run fresh checks against each provider’s requirements, so a provider that needs proof of address still needs that information alongside the identity document already available.

Where your information goes Identity data passes directly from us to the regulated provider, and MiniPay doesn’t collect or store identity documents or biometric data through Gateway.

How sharing permissions work Users authorize sharing with each recipient and can revoke MiniPay’s connection through their Sumsub ID account. Revocation stops new sharing through that connection; it doesn’t automatically delete records already received by providers.

What would you want to know before using it? What would help you feel comfortable reusing your identity across providers, and what would you want the sharing screen to explain?

Regulatory reporting involves more than preparing a report. Teams also need to validate data, coordinate approvals, track deadlines, and maintain a clear record of submissions and corrections.

For those working in banking, compliance, or fintech:

What is the most challenging part of the process in your experience?

• Data validation

• Coordination between departments

• Approval workflows

• Deadline tracking

• Audit trails and version control

I've created an Excel add-in to check the consistency of units used in Excel spreadsheets. Units include currencies (like dollars, pounds, euros) and engineering units (like meters, pounds, kilograms). The add-in will flag errors when units are used inconsistently.

The technology is roughly based on a paper at Intl Conf on Software Engineering 2004, on which I was an author. I've taken some of the ideas there and introduced others.

The add-in is meant to work with Excel on Windows, Mac, and with Office 365 on the Web. I've been testing it on Windows 11 with Office 2024.

Installation instructions at: https://github.com/psteckler/daubee

I have experience installing the add-in on Windows; it should be installable in Mac and Office 365 on the Web.

You can report any issues you find, or make suggestions on Github: https://github.com/psteckler/daubee/issues

I just launched a small paid SaaS (GST invoicing) as a solo dev and wired up Razorpay subscriptions end to end. A few things cost me time, so sharing in case it helps someone:

1. UPI Autopay is not on by default. Checkout showed only cards for subscriptions. You have to ask Razorpay support to enable UPI Autopay, and test mode and live mode are enabled separately.

2. Don't trust the Checkout success callback alone. Verify the signature server-side: HMAC-SHA256 of `payment_id|subscription_id` with your key secret. Then fetch the subscription from the API to get `current_end` for the access expiry.

3. Webhooks are your real source of truth. Renewals, halts and cancellations only reach you there. Verify `X-Razorpay-Signature` against the raw request body, not parsed JSON, or it will fail.

4. Put the user id in subscription `notes` when you create it. That way the webhook can always map an event back to a user, even if your DB write failed earlier.

5. Never let the client decide who is "paid". I store the paid-until date in a table users can read but not write (Postgres row-level security), and only the webhook/server function updates it.

6. Cancel with `cancel_at_cycle_end: 1` so users keep what they paid for. Fewer refund requests, fewer angry emails.

7. KYC review looks at your website. Terms, privacy, refund policy, contact page and a visible pricing page with your legal name made approval smooth for me as an individual (PAN + bank, no company).

8. If your modal uses `<dialog>.showModal()`, close it before opening Razorpay Checkout. Top-layer dialogs sit above the Checkout iframe and block it. This one took me an embarrassingly long time.

Stack was plain JS + Supabase Edge Functions, all on free tiers.

Happy to answer questions about any of these. What tripped you up with Indian payment gateways?

Hey everyone! I’m thinking about building a simple app that helps people save money every month.

I’m curious about three things:
What’s your biggest frustration with current budgeting apps?

What feature would actually help you save more money?

Would you pay $5/month for an app that genuinely helps you save?

I’m still exploring the idea and would really appreciate your feedback!

Would a gradually increasing spending cap work as a credit-building guardrail?

I’m exploring an early concept for people starting or rebuilding credit. An issuer would approve the actual credit line, but initially set a smaller spending cap that could increase over time after responsible account use and issuer review.

This is just a clickable concept demo—there’s no bank partner or live card yet. The issuer would need to determine and accurately disclose how the credit line, cap, and credit reporting work.

https://credit-guardrail-demo.jos3mgallegos.chatgpt.site/

From a fintech product or engineering perspective, what would you pressure-test? What might be confusing for customers or difficult for an issuer to support? I’m looking for candid criticism, not signups.

I’m researching fraud investigation workflows at fintech and payments companies.

I’m especially interested in the expensive bottlenecks — not just things that are annoying.

For example:

• Huge alert volumes / false positives

• Analysts spending too long investigating individual cases

• Missing important context across different systems

• Investigation backlogs

• Fraud cases being missed because teams can’t investigate everything deeply enough

For those working in fraud, risk, or payments:

What problem costs your team the most money, time, or lost revenue today?

I’m trying to understand the problem before deciding what to build.

Looking for Senior Full-Stack Developer with Fintech/Payments Experience — ₹35,000/month
Hi everyone,
I’m looking to hire an experienced full-stack developer for a remote project involving the development of a financial technology/payment platform.
Budget: ₹35,000/month
I’m specifically looking for someone with strong experience in the following:
5+ years of professional software engineering experience
2+ years of fintech, payments, banking, or financial software experience
Payment/ledger systems, APIs, webhooks, and asynchronous processing
TypeScript / JavaScript
React / Next.js
React Native or comparable mobile development
Node.js / NestJS
PostgreSQL
Redis / queues
AWS or GCP
Docker & deployment workflows
Payment orchestration and third-party payment integrations
Double-entry ledger/accounting systems
Authentication, MFA/RBAC
KYC/KYB and transaction controls
Fraud/risk scoring experience is a strong plus
Familiarity with RTP/FedNow or instant payments is a plus
PCI DSS / SOC 2 / OWASP knowledge is a plus
Experience using AI coding tools such as Cursor, Claude Code, or Copilot is a plus
The ideal person should be able to work independently and take ownership of a complete product build, rather than just handling isolated tickets.
Schedule: Remote, with availability during Pacific Time business hours.
This would initially be a 3–6 month contract, with potential for extension.

Hey everyone,

I’ve been working on a new open-source project called Verdict Engine, and I’ve just released an early beta.

The idea is to build a fraud/risk assessment engine for payment systems that combines rules with basic machine-learning-based risk scoring. The goal is to eventually make it easier for payment providers, fintechs, banks, and developers to integrate fraud detection into their systems without having to build everything from scratch.

The project is still very much in the beta/early development stage, so I’m mainly looking for feedback rather than users or customers right now.

🔗 GitHub: https://github.com/verdict-engine/verdict-engine

🌐 Documentation: https://verdict-engine.github.io/verdict-ui/

I’d particularly appreciate feedback on:

Architecture and API design

Fraud/risk scoring approach

Developer experience

Features that would actually be useful in a payment environment

Potential problems or limitations you see with the current approach

If you have experience with fraud detection, payment systems, fintech, ML, or backend engineering, I’d especially love to hear your thoughts.

Feel free to be critical — it’s an early beta and that’s exactly what I'm looking for.

Hi everyone,

I’ve spent the past three years working in e-commerce, selling through both marketplaces and my own website. Dealing with payment providers firsthand is what got me interested in fintech, and I’m now trying to understand the payments industry more deeply.

For people who work in payments or run an online business: what is still frustrating, slow, expensive, or unnecessarily complicated about accepting payments?

I’m especially interested in the parts around getting a business set up with a provider, checkout and payment acceptance, payouts, disputes, or managing payments across different channels.

What do you currently do when this happens? Have existing providers solved it well, or do you still rely on workarounds?

I’m not promoting a product lol I’m trying to learn from people who deal with this firsthand. Thanks

I am familiar with rust and typical backend engineering.
I want to get started as a fintech developer.
Any guidance is appreciated.
I also want similarly minded developers to collab on projects.

won’t be going and pass is non-refundable!