Server Release Notes for July 28, 2004

Credit Card Services: Enhancements for Vital Processor

If Vital is your payment processor, you may now process Level III transactions with Visa and MasterCard. For more information, see the Vital Level III Addendum to the Credit Card Services Implementation Guide, which is available on the Support Center.

If Vital is your payment processor, you may now process Level II transactions with American Express cards. For more information about the fields to use with American Express Level II transactions, see the Credit Card Services Implementation Guide, which his available on the Support Center.

If Vital is your payment processor, you may now process a credit card authorization for $0 to determine if the credit card is lost or stolen.

Subscription Payments (previously called Recurring Billing)

CyberSource has enhanced the Recurring Billing service and renamed it the Subscription Payments service. The enhancement includes the addition of two new types of subscriptions:

  • Approval-required: This is a recurring subscription that requires your approval before each payment is processed. An example of this type of subscription is a cell phone plan. Before you bill the customer at the end of the month, you determine the customer's usage during the month, set the amount of the payment, and approve the payment for processing by CyberSource.
  • On-demand: This is not a recurring subscription, but a subscription that lets you generate a payment at any time. CyberSource stores the customer's billing information and sensitive account information. At any time you can process a payment for that subscription by requesting a credit card authorization or electronic check debit and providing the subscription ID.

The enhancement also includes two new services that you can use:

  • A service to update an individual payment. For example, with this service you can change the amount of an individual payment and approve the payment for processing. Or, you can skip or unskip a particular payment. If you are using the Simple Order API, the service is called paySubscriptionEventUpdateService. If you are using the SCMP API, the service is called ics_pay_subscription_event_update.
  • A service to retrieve information about a subscription. You provide the subscription ID, and CyberSource returns details about the subscription, such as the customer's billing address, the masked account number, and so on. If you are using the Simple Order API, the service is called paySubscriptionRetrieveService. If you are using the SCMP API, the service is called ics_pay_subscription_retrieve.

In addition, we have changed how we handle the start date for the subscription. Previously we required you to follow specific rules to determine and then submit the earliest valid start date if you wanted the subscription to start as soon as possible. Now, you can omit the start date, or set the start date to the current day (or a day in the past) and we will determine the earliest valid start date for you.

We have also added the ability for you to provide an end date for the subscription instead of specifying the number of payments when you create the subscription. In this case, we use an algorithm to determine the number of payments based on the start date, the end date, and the payment frequency. Beware that if you specify the end date instead of the specific number of payments, our algorithm might calculate a number of payments that you do not expect. The algorithm we use is described in our documentation.

For a full discussion of these enhancements, see the Subscription Payments Implementation Guide (previously called the Recurring Billing Implementation Guide), which is available on the Support Center.

Global Payment Service

If you use the Global Payment Service, you can now perform direct debit refunds and bank transfer refunds more than 60 days after the direct debit or bank transfer. When using a CyberSource API to perform the refund, you must provide additional API fields with the refund request. For details, see the Global Payment Service Developer's Guide, which is available on the Support Center.

If you use the Global Payment Service and you request a follow-on credit against a payment, and the payment has not yet been processed by the processor, you now receive reason code 233 instead of 150 (for the Simple Order API) or a DINVALIDDATA rflag instead of an ESYSTEM rflag (for the SCMP API).

Simple Order API (formerly the Web Services API)

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