diff options
| author | Nicolas Lempereur <nle@odoo.com> | 2019-04-04 12:22:29 +0000 |
|---|---|---|
| committer | Nicolas Lempereur <nle@odoo.com> | 2019-04-04 12:46:00 +0000 |
| commit | 95c9227cb327912645e855767ed0e4daed6cadd5 (patch) | |
| tree | b7b62523223eecedda263102289a25eb5106888b /addons/mail/static/src/xml/thread.xml | |
| parent | fde76dd9b8f88b322f73a09bf5758b7c3ef28975 (diff) | |
[FIX] payment_authorize: >1m partner ok transaction
When creating a customer profile in Authorize.Net we specify a field
merchantCustomerId that is composed of:
ODOO-{partner-id}-{8-random-characters}
But the limit of this field is of 20 characters:
https://developer.authorize.net/api/reference/index.html#payment-transactions
So if we have 1 million partner, we may have eg. a partner 1000005 that
would result in an ID `ODOO-1000005-af123c5b` that is too long and
results in an error.
With this changeset, the generated ID is truncated to 20 characters so
this should theorically be alright for up to 9.99*10^15 partners (the
postgres limit for an integer is 2.15*10^9 so this should be safe
enough).
opw-1962422
closes #32423
Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
Diffstat (limited to 'addons/mail/static/src/xml/thread.xml')
0 files changed, 0 insertions, 0 deletions
