With this release, CyberSource offers two additional credit card processing gateways: LloydsTSB Cardnet and Lynk. For information about the features available with each gateway, see the Credit Card Services Implementation Guide, which is available on the Support Center.
If you use Paymentech as your electronic check processor, you can now send a merchant descriptor with debit and credit requests. The descriptor information appears on the customer's bank account statement. If you are using the Simple Order API, the field to use is invoiceHeader_merchantDescriptor. If you are using the SCMP API, the field to use is merchant_descriptor.
You must use a specific format with the merchant descriptor field:
If the company name is shorter than 15 characters, use spaces to fill in the full 15 characters. If it is longer than 15 characters, supply only the first 15 characters.
Contact Paymentech if you want to use the merchant descriptor. For more information about electronic checks, see the Electronic Check Services Implementation Guide, which is available on the Support Center.
In the July 2004 ICS server release, CyberSource gave you the ability to perform direct debit refunds and bank transfer refunds more than 60 days after the direct debit or bank transfer. In that previous release, you were required to provide the request ID of the bank transfer or direct debit for refunds that you requested within 60 days of the bank transfer or direct debit. For refunds that you requested more than 60 days after, you were required to provide the transaction reference number instead of the request ID. If you provided the request ID for these refunds, your request was rejected.
To make your implementation easier, you can now provide both the request ID and the transaction reference number for refunds no matter when you request the refund (either before or after the 60-day cutoff). For more information, see the Global Payment Service Developer's Guide, which is available on the Support Center.
If you are using the Subscription Payments service and are configured to use the automatic credit card pre-authorization feature, when you create a subscription, you can use the API fields that control how AVS results affect other services.
For example, if you are using the Simple Order API, you can use the businessRules_ignoreAVSResult field with your request to create the subscription. This causes CyberSource to ignore the results of the AVS check that automatically happens with the pre-authorization. If the credit card fails the AVS check, CyberSource still creates the subscription.
You can also use the businessRules_declineAVSFlags field to determine which AVS result codes cause an AVS decline.
If you are using the SCMP API, the corresponding API fields are ignore_avs and decline_avs_flags. For more information, see the Subscription Payments Implementation Guide, which is available on the Support Center.