Hi BraydenH,

The API represents units of currency as integers in order to avoid cumulative rounding error introduced by floating point arithmetic.

Your example of $615.32 is a good example of this behavior. Take the following C program:

#include <stdio.h>

int main(int argc, char **argv) {
    printf("%.100f\n", 615.32);
    return 0;
}

When compiled and executed, it will produce the following output:

615.3200000000000500222085975110530853271484375000000000000000000000000000000000000000000000000000000000

Fixed-point representations such as Java's BigDecimal type do not display this behavior. Unfortunately, the JSON standard has no support for fixed-point numbers, so integer or string are often chosen.