#henry-stripe-fee
1 messages · Page 1 of 1 (latest)
No there isn't as far as I'm aware
Ok, this extra stripe fee appearance broke the way we reported payouts to the user as we we expected fees associated to the connect customer to be associated with payments.
Just wonder if there was a way to setup this up for our staging env to verify the fix
Not sure I understand. Can you explain the issue a bit more so I can see if I have a recommendation?
dualshift-stripe-fee
@worn bough we don't support this today unfortunately in Test mode
I know it's not great but those fees are really only assessed monthly in production
henry-stripe-fee
@unique sluice It looks like radar fees are assessed daily, or whenever there is a payout
yeah possibly, we have lots of different pricing rules but unfortunately those do not happen in Test mode (that I know of)
@sour heart I justed wanted to see if there was a way to generate fake fees or any other entries outside of payment entries in test, to verify that our code accounts and reports these extra entries properly to the customer
We missed this, because we didn't have an example before.
Until our radar for fraud teams trial expired, which broke a job in production due to the unexpected fee
We have a fix for it in our test env, but no way for QA to test it looks like.
Beyond the developer unit testing and inserting their own fake fees into their queries.
I understand that's your ask. This is not possible unfortunately