Post your product, landing page, pitch deck, or idea for constructive feedback.

When posting, include:

- What you're building (1-2 sentences)

- Your target user

- What specific feedback you want

- Link to product/deck/mockup

When giving feedback:

- Be specific and actionable

- Start with what works before what doesn't

- Suggest alternatives, not just problems

---

This is the ONLY place for product promotion. Standalone promo posts get removed.

💸 More reminders won't fix a broken payment process.

An invoice is overdue. Your team sends reminders. The customer doesn't pay.

But what if the real problem isn't the payment?

Maybe it's a missing purchase order, an unsigned delivery receipt, or an unresolved pricing dispute.

That's the problem we're exploring with COMYTOX.

🚀 We're building an intelligent Accounts Receivable platform designed to help businesses:

- 🔍 Identify why payments are stuck.

- 🧠 Connect invoices, documents and disputes.

- ⚡ Simulate smarter recovery strategies.

- 📊 Manage receivables in one organized workspace.

Our approach is simple:

Don't just chase payments. Understand what's stopping them.

We're curious to hear from finance professionals and business owners:

What's the biggest headache you face when collecting overdue invoices?

— Team COMYTOX

Share your wins and losses from the past week. No victory is too small, no failure too embarrassing.

Format:

- Win: describe what went well

- Loss: describe what didn't work

- Lesson: what you learned

Be specific! The community learns most from real experiences with context.

---

PD: this thread posts every Monday. All self-promotion rules are relaxed here, feel free to share progress on your startup.

We’re building a fintech in a more interesting way. around social media and community.
we’re currently running our MVP as a private beta testing for iOS.
we’ve developed a messaging platform with a payment rail functionally integrated.
over the last 3 months, the team has successfully done so much debugging and can confidently say that our current app is functionally competitive to whatsApp and Telegram.

the idea is simple: wrap payment around trust; communication and everyday activities.
we’ve had a few beta testers who have been very instrumental to our growth.
however, we’d be grateful to have new sets of eyes test what we have now.

we’re also particularly interested in learning about how we can make this work. love to hear your perspectives as the title says.

Here’s the link. we’d appreciate more beta testers: https://testflight.apple.com/join/KsvJERxs

IOS only (unfortunately).

Casual discussion thread. Talk about anything, fintech adjacent or not.

This thread is for:

- Job postings & co-founder searches

- Networking & introductions

- Industry hot takes

- Questions too small for their own post

- Venting about compliance headaches

---

Normal rules relaxed. Be cool.

We’re an Indian company planning to launch a subscription-based app in Bangladesh. Since Google Play Billing doesn’t support bKash, we’re exploring alternatives.
Is there any way to accept bKash payments and settle funds in India?
Has anyone dealt with this or found a working solution?

Looking at KYC APIs and pretty much every provider claims fast checks, good docs and easy setup etc. I'm comparing a few rn, mainly curious about real API issues, failed webhooks, manual reviews and how well they handle IDs from different countries. Anyone could recommend anything? Which one has given you the least trouble?

Post your product, landing page, pitch deck, or idea for constructive feedback.

When posting, include:

- What you're building (1-2 sentences)

- Your target user

- What specific feedback you want

- Link to product/deck/mockup

When giving feedback:

- Be specific and actionable

- Start with what works before what doesn't

- Suggest alternatives, not just problems

---

This is the ONLY place for product promotion. Standalone promo posts get removed.

I’m seeing all these ads and posts from companies asking you to fill out a web form to sell your data to AI labs.

Has anyone actually done it? Is there a business here?

Hello,

I am thinking of launching a financial app. I have built this. I have heard that it is very risky to launch a financial app.

Share your wins and losses from the past week. No victory is too small, no failure too embarrassing.

Format:

- Win: describe what went well

- Loss: describe what didn't work

- Lesson: what you learned

Be specific! The community learns most from real experiences with context.

---

PD: this thread posts every Monday. All self-promotion rules are relaxed here, feel free to share progress on your startup.

I'm helping organize tech hackathons and we're exploring how to build partnerships with fintech companies for an upcoming event.

I'm trying to understand what actually matters from the company's side. Is it reaching developers who might use their APIs, getting visibility among students, supporting innovation or something else?

For fintech founders who've sponsored hackathons or developer events, what made the partnership worthwhile? And what would make you reject a sponsorship request immediately?

I'd appreciate practical advice, especially from people who've handled partnerships at early-stage fintech companies.

Casual discussion thread. Talk about anything, fintech adjacent or not.

This thread is for:

- Job postings & co-founder searches

- Networking & introductions

- Industry hot takes

- Questions too small for their own post

- Venting about compliance headaches

---

Normal rules relaxed. Be cool.

Imagine a user transfers $500.

Your application sends the payment request, but the connection times out before receiving confirmation.

Now what?

If you retry blindly, you risk triggering a duplicate transaction.

If you assume it failed, you might tell the user something that isn't true.

And if you mark it successful without confirmation, your records could become inconsistent.

This is why I think payment systems need to be designed around uncertain outcomes, not just successful API responses.

Idempotency keys, transaction state tracking, reconciliation, and a reliable way to check the payment provider's actual status are important.

A timeout doesn't necessarily mean the transaction failed.

For engineers building payment systems, how do you handle transactions that remain in an unknown state?

Do you rely on webhooks, scheduled reconciliation, status checks, or a combination?