<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Encrypted payment card numbers in Questions about SAP Websites</title>
    <link>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825395#M7442</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See OSS note 662340 on installing SAPCryptolib to enable card enryption. Also, see notes 766703 and 633462. Installation of cryptolib and the keys on a distributed landscape can be tricky.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you activate card enryption, SAP should encrypt/decrypt   automatically throughout the system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Oct 2005 19:46:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-10-14T19:46:05Z</dc:date>
    <item>
      <title>Encrypted payment card numbers</title>
      <link>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaq-p/825392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello. I have a question about implementating database encryption for stored credit card numbers in R3 (Rel. 45B).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a consultant coming in the next week to help with the config. If I am understanding the flow, the encryption and decryption can be done via function calls at different times (I am assuming via user exits) in the processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I encrypt the data, where is the encrypted value (which is much longer than the unencrypted credit card number field) to be stored? Is there a separate field used for storing the value? How long is that field?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any feedback would be appreciated, as I am trying to do a little prep work before the consultant arrives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Aug 2004 15:42:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaq-p/825392</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2004-08-31T15:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypted payment card numbers</title>
      <link>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825393#M7440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The answer is that you do not store the ciphertext in the card number field. You create a reference number which is 25 bytes long that substitutes for the card number, and is stored in the card number field. The reference number, in turn, is also stored in a custom table with the ciphertext. The reference number is a unique key to that table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You then create translation routines to encrypt/decrypt the ciphertext based on the reference number that you stored. These routines would be passed the card number field, which contains the reference number. The input parameter list for these routines are standard. The routines that do the encryption/decryption are configured to be called at the appropriate times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Brendan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Sep 2004 15:59:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825393#M7440</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2004-09-27T15:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypted payment card numbers</title>
      <link>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825394#M7441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What are the SAP functions that you call to encrypt and decrypt the card numbers?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the fields you want to encrypt are standard SAP fields through SAP's standard transactions, did you have to modify SAP code or did you use user exits?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jun 2005 10:47:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825394#M7441</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-06-30T10:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Encrypted payment card numbers</title>
      <link>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825395#M7442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See OSS note 662340 on installing SAPCryptolib to enable card enryption. Also, see notes 766703 and 633462. Installation of cryptolib and the keys on a distributed landscape can be tricky.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you activate card enryption, SAP should encrypt/decrypt   automatically throughout the system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Oct 2005 19:46:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/questions-about-sap-websites/encrypted-payment-card-numbers/qaa-p/825395#M7442</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-14T19:46:05Z</dc:date>
    </item>
  </channel>
</rss>

