Reply to thread

Message

<blockquote data-quote="Hacker News" data-source="post: 69137" data-attributes="member: 365">I have a Stripe account that has been going along nicely, regular transactions at a steady but moderate pace -- a few transactions a week at a consistent amounts. I'm a one-person-shop, not a developer, and I integrate with Stripe through my invoicing software. I've been building momentum towards a new product launch that will hopefully change that transaction velocity to dozens, hopefully a couple hundred transactions per day, through a storefront.Now, I am concerned that a significant change in velocity/volume like this is going to set off a flag with Stripe, and I fear that my Stripe account will get nuked, kill the launch, all the momentum I've been building, my reputation, and all my regular business to boot -- if I lose access to Stripe I lose a very significant portion of my business. Even if its just for a couple weeks while I'm &quot;being reviewed&quot;.There seem to be many threads here on HN about getting killed by Stripe without explanation, without easy recourse, without customer support or quick resolution -- especially as a small fry like me.Are there any suggestions for a non developer, one-person-shop to avoid this seemingly common pitfall?Why do I think I'll get flagged? In recent history had one invoice that was unusually large for my transaction history -- I landed a really good project. I feared this would set off a trigger with Stripe, and sure enough I was flagged &quot;as a part of our ongoing account review process&quot;.Stripe sent very vague and *very &quot;phishy&quot;* seeming emails. After logging into Stripe I had to give access to my bank accounts and get through a &quot;review&quot; of my business.I really feared I was going to be cut off then. So, I harbor no illusions that it will happen again next time should I enjoy a modicum of unusual success. I certainly learned that in the future I have to invoice large projects in smaller incremental chunks and not in the one-lump that the client preferred.But I don't know how to handle if the velocity of transactions changes.<hr />Comments URL: <a href="https://news.ycombinator.com/item?id=32856237" target="_blank">https://news.ycombinator.com/item?id=32856237</a>Points: 13# Comments: 2<a href="https://news.ycombinator.com/item?id=32856237" target="_blank">Continue reading...</a></blockquote>

[QUOTE="Hacker News, post: 69137, member: 365"] I have a Stripe account that has been going along nicely, regular transactions at a steady but moderate pace -- a few transactions a week at a consistent amounts. I'm a one-person-shop, not a developer, and I integrate with Stripe through my invoicing software. I've been building momentum towards a new product launch that will hopefully change that transaction velocity to dozens, hopefully a couple hundred transactions per day, through a storefront. Now, I am concerned that a significant change in velocity/volume like this is going to set off a flag with Stripe, and I fear that my Stripe account will get nuked, kill the launch, all the momentum I've been building, my reputation, and all my regular business to boot -- if I lose access to Stripe I lose a very significant portion of my business. Even if its just for a couple weeks while I'm "being reviewed". There seem to be many threads here on HN about getting killed by Stripe without explanation, without easy recourse, without customer support or quick resolution -- especially as a small fry like me. Are there any suggestions for a non developer, one-person-shop to avoid this seemingly common pitfall? Why do I think I'll get flagged? In recent history had one invoice that was unusually large for my transaction history -- I landed a really good project. I feared this would set off a trigger with Stripe, and sure enough I was flagged "as a part of our ongoing account review process". Stripe sent very vague and *very "phishy"* seeming emails. After logging into Stripe I had to give access to my bank accounts and get through a "review" of my business. I really feared I was going to be cut off then. So, I harbor no illusions that it will happen again next time should I enjoy a modicum of unusual success. I certainly learned that in the future I have to invoice large projects in smaller incremental chunks and not in the one-lump that the client preferred. But I don't know how to handle if the velocity of transactions changes. [HR][/HR] Comments URL: [URL]https://news.ycombinator.com/item?id=32856237[/URL] Points: 13 # Comments: 2 [url="https://news.ycombinator.com/item?id=32856237"]Continue reading...[/url] [/QUOTE]

Verification