There's an inherent ubiquitous nature to the strategy. Kinda like the golden ratio or the elliott wave theory. They've been published and are ubiquitous but they still occur in charts.
But I understand that once the algos know about the strategy, it becomes targeted to oblivion. So maybe I need to muster out the strength and use it without publishing its source.
It's also good to be skeptical about the backtesting itself, there are lots of ways for backtesting to overestimate gains and then you'd lose real money. Don't bet the farm (yet!)
My old man is in his 80s. I run a small brick & mortar business. I figured I'd bring him in and keep him busy -- do him a favor and perhaps help slow down his cognitive decline. But it turns out I was the one who needed him around. He's meticulous with the bookkeeping and really good at crunching numbers with pen & paper. It dawned on me... they don't make people like this anymore...
Slightly OT, but my opinion is they do still make people like this, our businesses just don't demand high-quality work as consistently as they used to, particularly for the kinds of work where software is marketed as the solution (across many functions).
I think it's more like software is able to handle the cognitive dissonance of managing years of a company's books and seeing in plain numbers that they don't make any money and are just burning investor cash until the party ends.
> You may not have reduced them enough to be eligible for service by Stripe
Not really. I made the changes while my account had payouts and payments paused by Stripe. I haven't been given the chance to show Stripe we take this seriously.
Well, if you did take it seriously then you would have reacted well before Stripe paused your account. I've had a business relationship like yours with another PSP (like Stripe) for many years and I was watching the CB rate like a hawk to make sure we never even got close to being labeled 'high risk'. This can be very hard, especially when customers engage in soft fraud, where all of the burden is placed on the merchant. There are a ton of things you can do to ensure that your rates are as low as they can be but even then it might simply not be enough. In your case I hope that you will be able to push things down to the point where you can continue your business and I also hope that Stripe will be able to work with you to determine if and if so under what conditions you will be able to work with them. But if Stripe can't then you have a much larger problem because every other PSP will have the same basic criteria and you'll end up with really low repute PSPs if you can't satisfy those. Typically those are the property of other parties that are unable to get normal processing in line so they make their own throwaway PSPs that get blown up in due course.
The account has been paused for an obvious reason. I made it clear from the get-go: it's due to chargebacks. And yes it falls on me.
But if any of my long term clients were to genuinely mend their ways about whatever issue that affects the relationship, I'd definitely give them a second chance.
Here's to hoping then. Regardless of the outcome: consider setting up an entirely different payment route, one that does not have the the chargeback possibility and verify your customers identity by first having them pay a small amount (or even their first invoices) until the relationship is established.
Why not publicly? But yes: my username@stripe.com. You mention something about reducing chargebacks, was your chargeback rate high for a particular reason? If so, you know we can't support businesses with excessively high chargeback rates. If you exceed the chargeback thresholds set by card networks, they can place you in a "dispute monitoring program" and the fines imposed on businesses can be very high.
The post was made here with no detail, making it look as though Stripe arbitrarily closed an account without cause. If you choose to post here, you should share details. If not, you should use our support channels (chat, email, phone, and @stripesupport on Twitter).
>If you choose to post here, you should share details. If not, you should use our support channels (chat, email, phone, and @stripesupport on Twitter).
An unhappy Stripe user has zero obligation to do any damn thing you prefer for the sake of helping you with your PR. They were counting on you for a vital service and you failed to continue providing it through a very abrupt termination of that service with no further internal recourse available. Despite this they should keep their complaints private unless they detail them in just the way you'd prefer, where you prefer? Fuck outta here...
Stripe already has a burgeoning track record of shitty behavior to users from what many of us have seen reported here and elsewhere, but this smugness from one of its own staff on a third party site is a nice bonus.
I'm happy to take a look at this for you. I also won't share any more details on this post unless you want to provide them yourself.
I will reiterate that we'd like to grow with any user we have (particularly a long-tenured one!). However, we can't support businesses with excessively high chargeback rates, no matter what. Keeping chargebacks at an acceptable level is a financial obligation for every business: https://stripe.com/docs/disputes/monitoring-programs.
I hear you. This is why I've gotten on top of this. I've essentially turned Stripe automation off in my system. So each and every customer wishing to go with Stripe for payment is fraud-checked and dd'ed.
Using Visa monitoring program as an example here, high dispute rates thresholds are as follows: 0.75% is an early warning, 0.9% is standard and can lead to fines, 1.8% is excessive. Dispute counts and other signals are also taken into account, not just the rate. https://stripe.com/docs/disputes/monitoring-programs#vdmp
That’s rough when some percent of users will chargeback just out of regret for the purchase without even contacting the merchant. As a SaaS app on stripe the disputes are virtually unwinnable.
I don't disagree—chargebacks can be abused by end-users, especially if you don't make it easy to get a refund or your communication is lacking. That being said, Stripe doesn't own any part of the process, we're an intermediary that communicates evidence and outcomes between a cardholder and their bank. The same painful fraudulent chargeback patterns exist with any PSP.
So, we make it as easy as possible to submit evidence. The cardholder's bank decides whether the chargeback is won in favor of the business or not. The card networks are aware that "friendly fraud" is increasing too, hence the introduction of Compelling Evidence 3.0 (more to come on this): https://support.stripe.com/questions/how-does-stripe-support....
Is there a way in the stripe dashboard to see my chargeback rate? I think I’m closer to .1% than the .75% you said is a problem, but hard to know 100% how you are calculating it on recurring revenue.
You can make sure to always collect enough evidence such as agreeing to TOS (including date, ip/location), invoices, providing easy refund paths as well as a way to demonstrate usage, etc. you can also automate dispute evidence submission. But the business model is often what determines whether you’ll have higher cb rates.
With a SaaS, maybe try a trial period and monitor is the customer actively uses the service, and make sure you notify them before you start charging. Often I signup for a trial, find out the service is useless but forget to cancel. That first charge is a prime cb candidate.
Traditionally the business is the source of spreadsheets (data comes from the biz side of the equation). The data analyst then has to make sense of the data.
So to convince a BA to input their data on Neptyne because the DA might need to python script it at some point is maybe premature optimization.
That's an uphill battle... But I definitely see it a good case for me personally as someone who both originates data (nothing fancy) and needs to process it further...
(co-founder of Neptyne) - It's definitely not the easiest market to break in, I am sure you are right there. The Python side of things does allow for easy import of data from anywhere though - you can just go:
A1 = requests.get(SOME_URL).json()
to make a REST API call for example. Right now that's often done by running some script that produces a .csv that then gets emailed around and imported into a spreadsheet.
This could be part of the Bitzlato crackdown [0]. Localbitcoins was referenced as one of the top counterparties.
*...Similarly, Bitzlato’s top three sending
counterparties, by total amount of BTC sent between May 2018 and September 2022 were (1) Hydra; (2) Local Bitcoins, a VASP based/incorporated in Finland; and
(3) “TheFiniko.”*
But I understand that once the algos know about the strategy, it becomes targeted to oblivion. So maybe I need to muster out the strength and use it without publishing its source.