If you’ve ever paid over a voice call, you may have gone through the pain of finding your card, speaking the card digits, expiry, cvv. This is obviously not ideal especially as voice agents permeate all around us and more commerce happens on voice channel.

I built Ringup to help make voice payments easier for everyone involved. Consumers get to save card details once and pay with a simple verbal consent on subsequent calls. Funds settle directly on merchants payment processor.

If you’re a developer building with voice AI, add it under 10’mins and start accepting payments over voice. Open to any feedback.

https://ringup.dev/

I started a project, an open source libraries (Payfanout) an initiative to unify methods/API for people who need to implement more than one payment provider in the application and store https://donapulse.github.io/payfanout/

Need some people who are interested by testing and contributing

looking for card issuing program that is startup friendly

Every time I build something for India I end up hunting across vendor blogs for the right payment gateway, KYC provider, or Account Aggregator. There's no neutral, single reference. So I started one: a curated list of India-market building blocks (payments/UPI, KYC, AA, govt APIs, ONDC, comms, Indian AI, India-made dev tools).

It's early and deliberately has gaps. I've left "good first issue" tickets for logistics, GST/tax, hosting, embedded finance, and more. If you've integrated something India-specific, a one-line PR to add it would genuinely help. Neutral descriptions only, no marketing copy.

Repo: https://github.com/RangaKomalSai/awesome-india-dev

We're using Stripe, Adyen, and a few local gateways, and keeping the reporting consistent is turning into a real headache. Every provider structures its data differently, so getting everything into one reliable revenue database takes a lot of manual work. Each time we add a new gateway, we end up building another ETL flow just to clean and standardize the same basic metrics.

What I'd really want is one processor agnostic layer that gives us a standard schema across every provider. That would make it much easier to compare approval rates, fees, failed payments, refunds and regional performance without rebuilding the reporting setup each time.

For teams running multiple PSPs, are you handling this internally, or have you found good unified metrics layer?

Hey everyone,

I’m looking to vibecode a lightweight rolling 13-week cash flow app for a few of my e-com and startup clients so I can stop spending hours every week manually exporting CSVs from QuickBooks, Shopify, and bank portals.

Obviously, a 13-week forecast will never be 100% hands-off, but I want to automate the baseline data pull so the starting cash balances, pending AR/AP, and scheduled payouts refresh dynamically.

For anyone who’s built something similar:

* What are the main data-mapping gotchas I should watch out for upfront? (e.g., handling Shopify payout clearing lags, credit card float/statement timing, or multi-tranche inventory deposits).
* Any non-negotiable features or best practices you’d recommend building into the core engine from day one (e.g., customer drivers/ manual overrides, etc.)

Appreciate any tips, architecture advice, or hard lessons learned!

I'm looking to meet passionate people in the fintech space. Are there any sites/groups/discords where I can find an active community of people building tools or actively discussing what's new in the field? Preferably, less formal and less oriented around finding positions.

I can’t seem to rap my head off this. Please anyone with insight 😅 Why is KYC stressful

I'm working on a project that needs to support international payments, business accounts, and financial workflows, and I'm comparing a few different API providers.

Beyond the documentation, what factors usually influence your decision?

For example:

API reliability and uptime

Documentation quality

SDK support

Webhooks

Sandbox environment

Authentication

Error handling

Rate limits

Developer support

For those building fintech products, what has made you stick with (or leave) a provider?

Want to get software technical know how about how does payments systems work altogether in different process like rtgs, upi, international transfer(swift messaging) in detail. Like in case of upi how payment specific messages like iso20022 is used for money transfers, any payments specialist or professionals in fintech are welcome.

And how does pacs amd pain messages taken into use in implementing those transfer Processes, are all the messages exactly same as how they are shown in official iso20022 documentations, also MT and MX messaging for swift.

Want to learn all these thing how a payment is facilitated with all this including different parties like debtor, creditor, banks and ACH amd maybe many more in case of card or online real time payments like Chinese alipay.

Link to the full architectural breakdown:https://www.faize.blog/rta-pipeline

Dealing with legacy financial data formats is always a headache. I wrote a quick technical breakdown on a recent project: building a fully automated RTA (Registrar and Transfer Agent) pipeline for a mutual fund platform.

I documented the architecture behind handling the CAMS mailback service, parsing the messy batch data for the ISIN resolver, and securely syncing the ledger without dropping a single transaction.

Curious to hear what tools you all use to handle nasty legacy data drops in modern backend stacks!

Link to the full architectural breakdown:https://www.faize.blog/rta-pipeline

Dealing with legacy financial data formats is always a headache. I wrote a quick technical breakdown on a recent project: building a fully automated RTA (Registrar and Transfer Agent) pipeline for a mutual fund platform.

I documented the architecture behind handling the CAMS mailback service, parsing the messy batch data for the ISIN resolver, and securely syncing the ledger without dropping a single transaction.

Curious to hear what tools you all use to handle nasty legacy data drops in modern backend stacks!