These release notes apply to both the ICS test and production servers.
For merchants using AmeriNet or TeleCheck and also using the Simple Order API: With this release you now have the option to specify the type of transaction (either Internet or MOTO) when requesting an electronic check debit or credit. You do this by using the ecDebitService_commerceIndicator field (for debits) or the ecCreditService_commerceIndicator field (for credits). For more details about the fields, see the Electronic Check Services Implementation Guide, which is available on the Support Center.
For merchants using American Express Phoenix: This release fixes an issue in which even though you were already correctly configured with CyberSource and American Express to use the CID, a value of 1 (which means card verification is not supported for this processor or card type) was incorrectly returned for the CV result. The correct response now being returned in this situation is a value of 3 (which means the processor did not return a card verification result code).
For merchants using FDMS South and processing Chilean pesos (CLP) and Indonesian rupees (IDR): This releases fixes an issue in which CyberSource handled the exponents for CLP and IDR currencies differently than FDMS South. Now, CyberSource provides transaction amounts to FDMS South with 0 exponents for IDR and 2 exponents for CLP.
For merchants using FDMS as their underwriter for Bill Me Later transactions: This release fixes an issue in which the product type delivery indicator you provided in your authorization request was mapped to an incorrect value when sent to the processor. The origin of this issue was an error in the FDMS specification. For more information about Bill Me Later, see the Credit Card Services Implementation Guide, which is available on the Support Center.
For merchants using the CyberSource Tax Calculation service to determine tax rates in Canada: When calculating tax in Canada, you can provide an override value for the Provincial Sales Tax (PST) for an item instead of having the Tax Calculation service calculate the item's PST for you. This release fixes an issue in which the API field in the Tax Calculation service reply that shows the PST for the item incorrectly showed the actual calculated PST value instead of the override value that you provided in the request. The PST value appears in the taxReply_item_#_countyTaxAmount reply field (for the Simple Order API) and the tax_county_tax# reply field (for the SCMP API). For more information about the Tax Calculation service, see the Tax Calculation Implementation Guide, which is available on the Support Center.
Version 1.18 of the Simple Order API has been released. For information about what has changed, see the Simple Order API Release Notes, which are available on the Support Center.