Credit Card Tokenizer URL

Your organizations may engage the services of third-party vendors to help manage constituent-related information, such as to update existing donor or constituent information or to recruit new donors. Third-party vendors who collect sensitive credit card information can use the Blackbaud CRM Credit Card Tokenizer to easily send this information securely to the Blackbaud Payment Service for tokenization. The vendor can then destroy any sensitive credit card information and return only the secure token information back to your organization to import into Blackbaud CRM.

Your organization can provide a specific URL found under Tokenizer URL in Administration, with vendor- and user-specific login credentials, to each vendor. These credentials use the same user access and authentication controls as Blackbaud CRM. The URL is to a secure .ashx page on the same web server as Blackbaud CRM. The vendor can then log in to the Credit Card Tokenizer page and select a file of constituent and credit card information to upload. The file is then submitted to the Blackbaud Payment Service and vendors will receive the secure token information in a return file to download.

Note: No credit card processing happens during this process, nor is any sensitive information written to the disk. Sensitive credit card information is simply submitted by a third-party vendor the organization has contracted with to the Blackbaud Payment Service for tokenization. The return file to the vendor contains cardholder names, last four digits of the card numbers, along with the credit card tokens. If additional information is included in the original file, such as other constituent information not related to cardholder information, that information is included in the return file. No sensitive card number data is returned, even if the card could not be tokenized. In that case, relevant exception messaging from the Blackbaud Payment Service is provided along with the cardholder names. Any sensitive information is completely removed from CRM servers after the file is returned.