Server Release Notes for June 14, 2000

If merchants include the field auth_request_id when calling both ics_auth and ics_bill in the same request, they will receive the reply flag DINVALIDDATA and the following error message:

"Requesting ICS applications ics_auth and ics_bill while sending a previous auth_request_id is not permitted."

If merchants include the offer-level field tax_amount in a request but provide no amount, ICS formerly returned an ESYSTEM error. ICS now returns the reply flag DINVALIDDATA and the error message "Value for tax_amount is missing from offer."

For merchants using ics_score and the optional offer-level field score_category_longterm, the day, week, and month settings are now based on calendar days, weeks, and months rather than on lengths of time. For example, if a merchant uses the day setting, IFS checks whether the product has already been purchased on that calendar day rather than in the preceding 24 hours.

In addition, merchants can now specify an integer for the score_category_longterm field to see whether a customer has purchased the product within the specified number of days. For example, a merchant can specify score_category_longterm: 14 to check whether the customer purchased the product within the preceding 14 days. The valid number of days can be any integer from 1 to 90.

For merchants using ics_download, ics_elc, or ics_export, if a transaction is declined because the customer's name matches or resembles a name on a denied-parties list, merchants can now view the denied party's name in the ics_rmsg return message. The denied party's name can also be viewed on the Merchant Support screens.

For all Credit Card Services Customers

If an invalid year appears as the customer's credit card expiration year (for example, 1899), merchants formerly received an ESYSTEM error. Now merchants receive the reply flag DINVALIDDATA.

ICS2 now includes a new service called Stored Value, which merchants can use to offer gift certificates and promotional gifts to customers and employees.

Merchants who are creating their public and private certificates for the first time and merchants who are updating their certificates will now automatically receive the latest version of the server certificate whenever they run the ecert application.

For merchants using CyberCash

If merchants erroneously attempt to use a previously authorized credit card number for a follow-on bill, ICS now returns a DNOAUTH reply. Formerly, ICS returned an ESYSTEM error.

For merchants using Paymentech

The Paymentech error code which formerly returned the error message "Invalid transaction type," now returns the following error message: "Assorted bank reasons."

For merchants using Vital and Paymentech

Formerly, ICS was not able to handle Type II procurement card transactions for merchants using Vital and Paymentech. The services ics_bill and ics_credit (follow-on only) now have that capability.

For merchants using Vital or NetTrade

When the issuing bank is down but the payment processor is still available, Internet Commerce Suite (ICS) applications formerly returned an ESYSTEM error. Now ICS applications return an ETIMEOUT error.

For merchants using NatWest or FDR

Formerly, when an error occurred at a payment processor, the ESYSTEM error did not specify the name of the processor. Now ESYSTEM errors specify the payment processor.

An ESYSTEM error returns the following error message to NatWest merchants:
"The payment processor returned an unexpected result: Interrupted system call: NatWest."

An ESYSTEM error returns the following error message to FDR merchants:
"The payment processor returned an unexpected result: Interrupted system call: FDR."

For all Credit Card Services Customers: Dynamic Soft Descriptor feature

NOTE: Paymentech-New Hampshire Customers only

The CyberSource SCMP API has been expanded to include support for Dynamic Soft Descriptors. This feature allows you to submit a unique merchant descriptor and toll free support number with each transaction. The descriptor and toll free number will persist throughout the transaction and be posted on the cardholder's statement for clarification and resolution purposes.

CyberSource has enhanced the credit capabilities associated with electronic checks. As of 6/14, CyberSource customers are able to issue credits for payments made by electronic check with any payment processor supporting CyberSource electronic check/ACH services.

For all Credit Card Services Customers: Verbal Authorization feature

IMPORTANT: In the June release, this feature is only available to Vital, NatWest, FDR Customers. As a result of Customer feedback, CyberSource will be releasing this feature for other Processors in a phased approach during the summer. This release note is to provide a heads-up for those Customers who would like to begin implementation of this feature in advance of it's release.

CyberSource has added support for verbal authorizations (also called referrals). Upon securing a verbal authorization, businesses can now send the authorization code through the CyberSource gateway via a standard CyberSource SCMP request or enter it manually via transaction screens found on the CyberSource Merchant Support Center.

New Fields in ics_bill:
auth_code (optional): must contain authorization code verbally received from Bank.
auth_type (optional): must contain text "verbal"

New Reply field:
rFlag = DCALL: this may require modifications to your system to ensure it can handle this new rFlag gracefully.

For all Credit Card Services Customers: eCommerce Indicator feature

As of 6/1/00, CyberSource is in compliance with the new Visa regulation requiring all e-commerce transactions to carry an e-commerce 'flag' - one that identifies them as an online transaction.

No modification is needed to your systems, as CyberSource automatically includes the eCommerce indicator with all transactions handled via processors who support this feature.

For all Credit Card Services Customers: Card Verification Value2 feature

The CyberSource SCMP API has been expanded to include support for Card Verification Value2 (also called CVV2, CID, CVC2) for all processors that support this feature. CyberSource has added an optional field to the authorization request which allows businesses to request verification of the card verification value at the time of authorization.

New Fields in ics_auth:
customer_cc_cv_number (optional): card verification value on back of credit card.
ignore_bad_cv (optional): allows you to override 'bad' card-verification-value responses from Bank.

New Reply fields:
auth_cv_result: result returned from Bank
rFlag = DCV: indicates Card Verification check failed by Bank.

For all Payment Services Customers: Transaction Level Reconciliation

CyberSource has enhanced our reporting capabilities to make it easier for Customers to reconcile CyberSource transaction reports with their bank statements. A business can now determine whether a deposit has been made for specific transaction. This feature is available for Customers processing on Paymentech, Vital, and FDMS-Nashville.