| ||||||||||
Shopping cart software Solutions for online shops and malls | ||||||||||
|
X-Cart Home | FAQ | Forum rules | Calendar | Mark Forums Read | User manuals | Login |
3.1.2 API Changes Amount Behavior | |||
|
|
Thread Tools |
#1
|
|||||||
|
|||||||
3.1.2 API Changes Amount Behavior
In 3.1.2, XPayments API now expects the "amount" field to be the total, where in earlier versions, it was the total minus tax, assuming a tax amount was transmitted separately.
I'm using the same modified sample code (I haven't updated it in months) and this behavior changed when we upgraded our server to 3.1.2.
__________________
X-Cart version 4.7.12 |
|||||||
|
#2
|
|||||||||
|
|||||||||
Re: 3.1.2 API Changes Amount Behavior
Quote:
The "amount" field was always used to be a "Grand total" that includes taxes and etc, and it was only related to recurring charge requests. For initial payment requests "totalCost" field is used, and it was for "Grand total" as well. The only thing that is changed is that previously if both "amount" and cart's "totalCost" is specified in recurring charge request, then the "totalCost" is used, but now in 3.1.2 the "amount" value will override it.
__________________
Sincerely yours, Vladimir Petrov Senior X-Payments Developer |
|||||||||
|
Thread Tools | |
|
|
|
|||
X-Cart forums © 2001-2020
|