Server Release Notes for May 25, 2005

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

Decision Manager

If you are using Decision Manager and are reviewing a transaction in the Enterprise Business Center, you can enter comments about the transaction in the Transaction Details page. Now with this release, those comments will appear in the Conversion Detail Report. For more information about the report, see the Decision Manager Implementation Guide (either standard or advanced version), which is available on the Support Center.

Credit Card Services: Bill Payment with Visa Cards

Customers may pay bills by using their Visa cards. Visa now requests that you include a special bill payment flag in your authorization or credit request so that Visa can separate the transactions from normal credit card purchases or credits. Although CyberSource accepts the bill payment flag no matter which processor you are using, currently CyberSource forwards the information only to Vital and Citibank Global.

If you are using the Simple Order API, the new optional field to use in the authorization request is ccAuthService_billPayment. The field to use in the credit request is ccCreditService_billPayment. Set the field to N if the transaction is not a bill payment (default) or Y if it is a bill payment.

If you are using the SCMP API, the new optional field to use in the authorization or credit request is bill_payment. Set the field to N if the transaction is not a bill payment (default) or Y if it is a bill payment.

For more information, see the Credit Card Services Implementation Guide, which is available on the Support Center.

Credit Card Services: $0 Authorization with FDMS South

If you are using FDMS South as your processor, you can now request authorizations for $0 to check if the card account is valid. You receive address verification (AVS) results and an authorization code as if it were a normal authorization. Note that you may not send the card verification number with the authorization request. If you do, the request will be declined. For more information, see the Credit Card Services Implementation Guide, which is available on the Support Center.

Credit Card Services: Forced Capture with Vital

If you are using Vital as your processor, you can perform forced captures with this new release of the ICS services. A forced capture occurs when you process an authorization outside the CyberSource system but then capture the order by using CyberSource. Follow these steps to perform a forced capture:

1. After you have processed the authorization outside the CyberSource system, request a CyberSource authorization. As part of the request, you must include the authorization code and a specific flag that indicates you received the authorization code outside of CyberSource. (This authorization request does not get sent to the processor; CyberSource simply stores the information so that it can be used later for the capture.)

2. When ready, request the capture just like you would a normal capture. You do not need to provide the authorization code in the capture because CyberSource already has it in the database.

The capture is processed.

If you are using the Simple Order API, in the authorization request, set the field ccAuthService_authType=verbal, and set the field ccAuthService_verbalAuthCode to the authorization code you received.

If you are using the SCMP API, in the authorization request, set the field auth_type=verbal, and set the field auth_code to the authorization code you received.

For more information, see the Credit Card Services Implementation Guide, which is available on the Support Center.

Credit Card Services: New Features for Citibank Global

If you are using Citibank Global as your processor, you may now process retail transactions. For more information, contact your CyberSource Account Representative.

You may also now use a merchant descriptor with authorization, capture, and credit requests. The merchant descriptor appears on the customer's credit card statement. CyberSource supports two fields: one for the merchant's descriptor (up to 22 characters; use for the merchant's name), and one for the merchant's contact information.

The merchant descriptor can be up to 22 characters long. If you are using the Simple Order API, the field is invoiceHeader_merchantDescriptor; if you are using the SCMP API, the field is merchant_descriptor.

For the merchant descriptor contact, the field can be 13 characters long and must follow a specific format (see below). If you are using the Simple Order API, the field is invoiceHeader_merchantDescriptorContact; if you are using the SCMP API, the field is merchant_descriptor_contact. You can use the field to display a city, telephone number, or URL; and/or the state. Use one of the formats below. Note that the delimiter is a pipe ( | ).

  • <up to 10 characters for the city, phone number, or URL>|<2 characters for the state code>
  • <up to 13 characters for the city, phone number, or URL>
  • |<2 characters for the state code>

These are valid examples:

  • 6509656000|CA
  • (650)965-6000
  • San Jose|CA
  • San Jose
  • |CA
  • help@name.com

Credit Card Services: Household Bank Private Label Cards with Paymentech

If you are using Paymentech as your processor, you may now process Household Bank private label cards. The card type value to specify in the authorization request is 041.

Bill Me Later: Stand-Alone Credits with FDMS

If you use Bill Me Later with FDMS, you may now perform stand-alone credits. A stand-alone credit is a credit that you perform more than 60 days after the payment. With a stand-alone credit you must provide all of the customer's billing and account information as well as a special transaction identifier that you received in the payment reply. For more information, see the Credit Card Services Implementation Guide, which is available on the Support Center.

Electronic Check Services: AmeriNet

If you are using AmeriNet as your processor, you can now use CyberSource's Payment Events Report to help determine when a check has cleared. For more information, see the Electronic Check Services Implementation Guide, which is available on the Support Center.

Electronic Check Services: TeleCheck

If you are using TeleCheck as your processor, you may now perform stand-alone credits. A stand-alone credit is a credit that you perform more than 60 days after the debit. With a stand-alone credit you must provide all of the customer's billing and account information as well as a special transaction identifier that you received in the debit reply. For more information, see the Electronic Check Services Implementation Guide, which is available on the Support Center.

PIN-less Debit Services

If you are using FDMS South as your processor, you can now process PIN-less debit orders that originate from a call center (orders that come from an interactive voice response (IVR) system or your Web store were already supported prior to this release). To indicate where the order originates, set the e-commerce indicator to one of these values:

  • internet
  • moto-call center
  • moto-ivr

If you are using the Simple Order API, you specify this value in the pinlessDebitService_commerceIndicator field. If you are using the SCMP API, you specify this value in the e_commerce_indicator field.

For more information, see the PIN-less Debit Services Implementation Guide, which is available on the Support Center.

Global Payment Service: Bank Transfer Missing Payment Inquiry

If you are processing bank transfers through CyberSource's Global Payment Service, you can now initiate a payment inquiry through the Enterprise Business Center to locate a missing payment. You may need to do this if customer calls to say that they have made the bank transfer payment, but they have not received the goods, and CyberSource's report and your bank account statement do not show that you have received the payment. This might happen if CyberSource cannot match the customer's payment information to the information you submitted in the original bank transfer request (typically because the customer transcribed information incorrectly). You make the payment inquiry in the Enterprise Business Center, and CyberSource will research the missing payment and try to match your request with the customer's payment.

For more information, see the Global Payment Services Planning Guide, which is available on the Support Center.

PayPal: New Services

With this release, CyberSource has made two major changes to the PayPal Services. We have:

  • Replaced the existing PayPal Payment Service with a new Button Create Service that allows you to create multiple types of PayPal payment button
  • Added two new services to support PayPal's preapproved payments

The old PayPal Payment Service was able to create only one kind of payment button. The new Button Create Service can create a regular Buy Now button, a Shopping Cart button, or a Billing Agreement button.

You use a Billing Agreement button as part of processing preapproved payments. Preapproved payments are periodic payments that you process without needing to interact with the customer each time you process a payment. For example, if you have a regular monthly service that the customer is buying from you, you can charge an amount each month to the customer's PayPal account without having to get approval from the customer each time. Instead, you set up a billing agreement and use the Billing Agreement button to take the customer to PayPal's Web site to view and approve the agreement. Once the customer approves the agreement, you use CyberSource's Preapproved Payment Service to process each payment according to the terms in the agreement. You can also later update or cancel the agreement by using CyberSource's Preapproved Payment Update Service.

For more information, see the PayPal Services Implementation Guide, which is available on the Support Center.

Simple Order API (formerly the Web Services API)

Version 1.14 of the Simple Order API has been released. For more information, see the Simple Order API Release Notes, which are available on the Support Center.