Amount in price should be int and in paise for INR

[mahoriR]

The problem is float comparison.
1.0 != 1.000000001 but with floats passing around without bounded with decimal points, we will run into these problems.

The 2 most popular payment gateway (Strip and Razorpay) use paise/cents instead thus forcing these to be integers. That works wonderfully well.

Another alternative solution if to fix the maximum possible decimal points to 2 (Cashfree does this).
Current unbonded decimal space amount though will lead to trouble in future.

Links below for reference --
https://stripe.com/docs/api/orders_v2/object
https://docs.cashfree.com/reference/createorder
https://razorpay.com/docs/api/orders/

@BLR-0118 @core-wg-admin

[amitabhdhiwal]

Cryptocurrencies have decimals beyond the traditional two. Floats should be fine.

[BLR-0118]

@batramanuj - your comments?

[BLR-0118]

Hi @batramanuj pls share your comments on this

[batramanuj]

Along with the problem mentioned above, arithmetic operations on two float/Double values can result in loss of precision which is certainly how we don't want to handle money.Using a long data type we can represent amount as integers in their lowest currency denominations without having to ever worry about precision. Same approach gets followed in UPI.

[BLR-0118]

@pramodkvarma @core-wg-admin - for your comments

[pramodkvarma]

I generally prefer the amount to be represented as two separate integer values. At base protocol level we can support both integer and decimal representations. We should also ensure we explicitly capture currency. @core-wg-admin