--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+unsubscribe@googlegroups.com.
To post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/f7bd8937-1372-448d-a497-571de16ffce8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3Dm6Zw9nxbyH7P%3Da-nwKLjCHnOPQEJf%3DevigA78z9vmtqQ%40mail.gmail.com.
--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+unsubscribe@googlegroups.com.
To post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DmLPAt5NqFH1Kr%3D-YOx0vv7C00kx4q0K0j2nMhjdJE6yA%40mail.gmail.com.
Do you control the specification?
You need to realize, transactions get forwarded and at some point the standard 12 will be needed.
You could use a private custom field to send the amount and the receiver needs to be aware of it, then it's his headache to forward it ;-)
You could define the field as binary and cram in twice the number of digits. But at the end of the day the receiving entity needs to be aware of the format and size to handle and forward appropriately.
-chhil
And also countries with long history of high inflation rate. Exceeding 12digit amount is very possibleSo what is the best practice?
On Dec 7, 2016 6:09 AM, "Alejandro Revilla" <a...@jpos.org> wrote:
--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DmLPAt5NqFH1Kr%3D-YOx0vv7C00kx4q0K0j2nMhjdJE6yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: sa...@jpos.org
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAL8bJ0EjwCXSHduA8czDTjV4ffhcJYUWcD3sgiB8aSauT6gopQ%40mail.gmail.com.
You could define the field as binary and cram in twice the number of digits.
79228162514264337593543950335
:-)