CreditCard Tasks

Properties   Configuration Settings  

The CreditCard Task is used to authorize a credit card charge.

Remarks

The CreditCard Task allows you to use multiple Internet Payment Gateways through one property set and one task. This allows for easy migration from one gateway to another, as well as quick integration into applications or web services.

CreditCard Send Task

The CreditCard Send Task allows your SSIS Package to securely perform credit card transactions without the need to redirect to a third-party site. All transactions are accomplished through a secure HTTPS Post to any supported gateway. To gain access to gateway services you must first contact a gateway vendor and set up an account. Necessary account and password detail will be supplied by the gateway.

In order to configure the task, you will need to select the Gateway. The task will automatically determine the URL for posting transactions, however you may override the default URL by directly setting the GatewayURL property. You must also supply, at the very least, your MerchantLogin. If your account requires a password, you should set that via the MerchantPassword property. Some gateways may also require that SSL be used, which can be set up by selecting an SSLCert for client authentication and a SSLAcceptServerCert for server authentication.

In order to perform a transaction, you must set the necessary properties. First and foremost, you must set the relevant card information, such as Number, ExpMonth, ExpYear, and CVVData. The task will attempt to automatically discover the type of card based on the Number, but you may directly set it via the CardType property.

Once you have set the card information, you must also set the customer information. This includes, but is not limited to, FirstName, LastName, and Address. Finally, you must set the details of the actual transaction, such as TransactionAmount and any desired description via TransactionDesc.

After the task has performed the transactions, the status will be returned via the various response properties, which can be read from the message context at runtime. These include TransactionApproved, ResponseApprovalCode, ResponseAVS, ResponseCode, ResponseCVV2 and ResponseInvoiceNumber. The complete response is stored in ResponseData, with a human-readable message in ResponseText. If the gateway returns an internal identifier for the transaction, it will be stored in ResponseTransactionId.