Server Release Notes for October 28, 2005

These release notes apply to the ICS test and production servers.

Credit Card Services: UATP Gateway

With this release, CyberSource offers an additional credit card processing gateway: UATP. With this gateway, you can process UATP credit cards and include airline data in the settlement request. If you want to use UATP, contact your CyberSource account representative. For information about the features available with the gateway, see the Credit Card Services Implementation Guide, which is available on the Support Center.

Credit Card Services: Maestro Cards

With this release, when you process a Maestro card, you should now specify the card type as 042. For a list of the supported card types, see the description of the card_cardType field (for the Simple Order API) or the card_type field (for the SCMP API) in the Credit Card Services Implementation Guide, which is available on the Support Center.

Credit Card Services: Retail Point of Sale Transactions

With this release, CyberSource has relaxed the requirements for including API fields for the customer's name, email address, and billing address for retail point of sale (POS) transactions with the Vital processor. Previously, you were required to provide that information in specific API fields for all retail transactions with Vital. Now, those fields are optional in most situations. For details, see the "API for Retail POS Transactions" addendum to the Credit Card Services Implementation Guide. The addendum is available on the Support Center.

Bill Me Later

Before this release, when you created a new Bill Me Later account, you provided CyberSource with the account number 5049900000000000. Now, when you create a new Bill Me Later account, you can use that number or the new account number 6219930000000000. Which one to use depends on your contract with i4Commerce.

New ICS Service: Void

You can now access CyberSource's void service (voidService in the Simple Order API, or ics_void in the SCMP API). You can use the void service to cancel these types of requests:

  • Credit card captures and credits
  • Electronic check debits and credits
  • Bill Me Later captures and credits

A transaction can be voided only if we have not already submitted the information to your processor. Usually we submit that type of information to your processor once a day, so your window for successfully performing a void is relatively small. We will decline your void request if we have already sent the transaction information to the processor.

When you void a transaction, the transaction is at the end of its life and cannot be the source of another follow-on capture or credit. For example, if you authorize and capture a transaction, and then you void the capture, you cannot submit another capture request that uses the authorization code or CyberSource request ID from the original authorization. If you still want to capture that transaction, you must re-authorize the transaction and capture the new authorization.

You cannot undo a void. Also, you cannot perform a follow-on credit for a transaction that has been voided.

If you are using the Simple Order API, you receive two new reason codes related to the void service: 246 (if the transaction cannot be voided) and 247 (if you try to credit a transaction that has been voided).

If you are using the SCMP API, you can receive a new rflag if the transaction cannot be voided: DNOTVOIDABLE. If you try to credit a transaction that has been voided, you receive a DINVALIDDATA.

For information about the void service and its API fields, see the Credit Card Services Implementation Guide, which is available on the Support Center.

Simple Order API (formerly the Web Services API)

Version 1.17 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.