#madmac4000

1 messages · Page 1 of 1 (latest)

slender pantherBOT
rough nimbus
lime ruin
#

No workaround?

rough nimbus
#

Hm...

#

You're using direct charges, right?

#

With Standard accounts?

lime ruin
#

Yes

rough nimbus
#

Nothing comes to mind, no, sorry.

lime ruin
#

Seems like a massive limitation. Am I missing something obvious?

rough nimbus
#

Not that I'm aware of. It's fairly uncommon to have an application fee require more than two decimal points of precision. I can flag it as a feature request interally for you though.

lime ruin
#

With the same code and a higher amount the application fee percent is being rounded to 0.

#

Yes please.

#

I must be doing something wrong with the decimal places in the equation this can't be correct. I will review.

rough nimbus
#

My only suggestion would be to approach the calculations differently and determine what the most ideal two-decimal-place value for the fee would be and use that. For example, if you have a fee that would round to zero and you don't want that, find the closest two-decimal value that would be non-zero and use that instead.

lime ruin
#

Ah I am a fool haha.
Should be:
46/4992 * 100 = 0.921474358
4992 * 0.92%

I was thinking the application_fee_percent was a decimal 0-1 not a percent 0-100

#

This gives the precision I need. Sorry for wasting your time 🤦‍♂️

rough nimbus
#

Ah, okay, glad it's working for you!