Procedure documentationCreating Payment Card Transactions Locate this document in the navigation structure

 

You use this procedure to create and authorize payment card transactions, and copy them to an ERP system.

Prerequisites

You have assigned the payment plan type Payment card to the transaction types you use.

In Customizing, choose   Customer Relationship Management   Basic Functions   Payment Cards   Settings for Transactions   Assign Payment Card Plan Type to Transaction   .

The merchant IDs assigned to the organizational units in SAP CRM match those specified for the corresponding general ledger accounts in your SAP ECC system.

Recommendation Recommendation

For security reasons, we recommend you activate encryption of the payment card number.

In Customizing, choose   Customer Relationship Management   Basic Functions   Payment Cards   Maintain Payment Card Type   .

End of the recommendation.

Procedure

  1. Create a transaction.

  2. On the Payment form tab page, enter required data such as payment card type, card number, and cardholder.

    There are several ways to enter this data:

    • To enter this partner's standard card automatically, choose Default card.

      If this customer's master data includes only one card, it is the standard card. If the customer's master data includes more than one card, the standard card is the one marked as standard.

    • To display a list of available cards, use the Possible entries help for the Card number field.

    • Manually enter the card data.

    When you activate encryption after you have saved the document, the card numbers are displayed automatically in encrypted form . From this moment on, this data is displayed in the activity document in the following format: 51000*********08.

  3. Save the transaction.

Result

When you save a payment card transaction, the system:

  1. Authorizes the transaction with the clearing house, may perform address- and card checks as part of authorization, and enters all results on the Payment form tab page.

  2. Encrypts the card data, if it is not already encrypted, so that it is not readable as plain text in the data bank.

  3. Transfers the transaction document into your OLTP system, provided that the document is free of errors and that authorization has not been denied.