Payment  Card Processing - CRM 4.0

Hi,
I have done all the config and customisation required for the Payment Card Processing in CRM 4.0.
I was wondering if I have to make some changes on the R/3 4.6 c side?
Right now the authorisation is happening in CRM. Once the document goes to R/3, it returns an error saying that the Credit card payment failed in R/3.
Do I need to switch off the authorisation determination in R/3 (its not required, since its already been done in CRM), if yes, what needs to be done?
Anything else on the R/3 side which I have missed?
thanks
Yash

Hi Ash,
You also have to do a bunch of configuration activities in R/3, apart from CRM. Basic authorization takes place in CRM order, and when this order flows into R/3, the approved authorization has to be validated for follow-up processes like invoicing, payment posting etc. Sometimes the order need to be re-authorized in R/3, if the quantities and or line items changes.
List of all the required R/3 payment card configurations must have been provided by the payment card interface vendors like verisign, paymetric etc.
By the way who is the payment card vendor for your project? Request them a copy of R/3 configurations docuement.
If you don't get the copy, then let me know. I should be able to give you the list of configuration activities.
Reward if helps.
Regards,
Paul Kondaveeti

Similar Messages

  • Payment Card processing- Manual Authorization

    Hi Experts,
    We are on CRM 4.0.
    Wanted to have an input on the Manual Authorization process for Payment card processing.
    Can someone guide as to how this can be achieved?
    thanks
    Yash

    df

  • Payment card processing in SAP DBM

    Hi All,
    I am analyzing the use of payment card processing to be used in DBM orders. I tried to search for the same but with no luck.
    Anybody wokring on such stuff or have any nformation / data related to the same.
    or if anybody can guide us on this.
    Regards,
    SB

    Hi,
    Payment card process is simple one but if you are using third party software to process it then you need to consider strong integration point like
    Cardholder
    Uses a payment card to purchase goods and services.
    Merchant (your company)
    Provides goods and services and accepts cards as payment.
    Clearing house
    Issues authorizations and provides services for processing settlement data supplied by
    the merchants.
    Below is link for details
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf
    Kapil

  • Payment card processing in SAP DBM orders.

    Hi All,
    I am analyzing the use of payment card processing to be used in DBM orders. I tried to search for the same but with no luck.
    Anybody wokring on such stuff or have any nformation / data related to the same.
    or if anybody can guide us on this.
    Regards,
    SB

    Hi,
    Payment card process is simple one but if you are using third party software to process it then you need to consider strong integration point like
    Cardholder
    Uses a payment card to purchase goods and services.
    Merchant (your company)
    Provides goods and services and accepts cards as payment.
    Clearing house
    Issues authorizations and provides services for processing settlement data supplied by
    the merchants.
    Below is link for details
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf
    Kapil

  • Payment Card Processing in SAP FI

    Hi Gurus,
    Please can anubody explain me what config needs for paymet card processing for customers in FI side.
    Please any body can give me the config in detail. Points will be assured.
    Regards,
    Shwetha.

    Hi,
    Payment card process is simple one but if you are using third party software to process it then you need to consider strong integration point like
    Cardholder
    Uses a payment card to purchase goods and services.
    Merchant (your company)
    Provides goods and services and accepts cards as payment.
    Clearing house
    Issues authorizations and provides services for processing settlement data supplied by
    the merchants.
    Below is link for details
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf
    Kapil

  • Payment Card processing

    Hi Everybody,
    We have payment card processing implemented and we havebeen noticing that when an order has been placed on credit hold, the backgroung job for authorization is authorizing the order multiple times. As soon as I release the order, it stops authorizing it if a valid authorization is found. But the worrying fact is that, it is authorizing multiple times and teh customer is charged as many times. This is very worrying. Any help wouold be appreciated.
    Also, SAP does not default the credit card number from the customer master into the sales order. Our intention is to mark a card as default and if it is default, it has to copy into the sales order. Has anybody come across a suitabel user exit for this?
    Thanks & Regards,
    Vidya Sagar
    Edited by: VIDYA SAGAR DADI on Oct 13, 2009 4:41 AM

    df

  • Best Practice guide for purchasing - payment card processing

    Hello All,
    \Is there any Best Practice guide for “Payments by credit card”/ “Payment card Processing”.
    The biz process is:
    The purchasing department users purchase goods/services using their corporate credit cards. They obtain a credit card voucher/receipt for the purchase made. The credit card co. turns in the credit card statements/files once in a month  the Accounts Payable  matches the receipts with the statements/files & makes the payments.
    Will reward points.
    Thanks & Regards,
    Arpita

    Hi Arpita,
    You might want to check this link
    http://web.mit.edu/sapr3/docs/webdocs/purchpay/ppCC.html
    http://www.bitpipe.com/tlist/Payment-Processing.html
    http://whitepapers.sapinsideronline.com/view.cfm?session=&white_paper=4
    Thanks,
    Jenny
    award points if helpful

  • SD payment card processing module

    Hi to every one ,
    what is SD payment card processing module.
    any have any idea plz give some idea. if u have any documentation plz send me.
    Murli.

    Hi Murli,
    I have pasted below the payment card configuration document.If it is not clear please send me your e-mail id i will send the document across to you.
                                   SAP Credit card configuration
    <u>Set Up Credit Control Areas:</u>
    Define Credit Control Area
    Transaction: OB45
    Tables: T014
    Action: Define a credit control area and its associated currency.  The Update Group should be ‘00012’.  This entry is required so the sales order will calculate the value to authorize
    Assign Company Code to Credit Control Area
    Transaction: OB38
    Tables: T001
    Action: Assign a default credit control area for each company code
    Define Permitted Credit Control Area for a Company Code
    Transaction:
    Tables: T001CM
    Action: For each company code enter every credit control area that can be used
    Identify Credit Price
    Transaction: V/08
    Tables: T683S
    Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax.  Make the following entries:
    Sub to:          “A”
    Reqt:          “2”
    AltCTy:          “4”
    Automatic Credit Checking
    Transaction: OVA8
    Tables: T691F
    Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed.  You need to mark the field “no Credit Check” with the valid number for sales documents.
    <u>Set Up Payment Guarantees</u>
    Define Forms of Payment Guarantee
    Transaction: OVFD
    Tables: T691K
    Action: R/3 is delivered with form “02” defined for payment cards.  Other than the descriptor, the only other entry should be “3” in the column labeled “PymtGuaCat”
    Define Payment Guarantee Procedure
    Transaction:
    Tables: T691M/T691O
    Action: Define a procedure and a description.  Forms of Payment Guarantee and make the following entries
    Sequential Number      “1”
    Payment Guarantee Form     “02”
    Routine Number           “0”    Routine Number can be used to validate payment card presence.
    Define Customer Payment Guarantee Flag
    Transaction:
    Tables: T691P
    Action: Define a flag to be stored in table.
    Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can use Payment Cards)”.
    Define Sales Document Payment Guarantee Flag
    Transaction:
    Tables: T691R
    Action: Define the flag that will be associated with sales document types that are relevant for payment cards
    Assign Sales Document Payment Guarantee Flag
    Transaction:
    Tables: TVAK
    Action: Assign the document flag type the sales documents types that are relevant for payment cards.
    Determine Payment Guarantee Procedure
    Transaction: OVFJ
    Tables: T691U
    Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
    <u>Payment Card Configuration</u>
    Define Card Types
    Transaction:
    Tables: TVCIN
    Action: Create the different card types plus the routine that validates the card for length and prefix (etc…)
    Visa , Mastercard, American Express, and Discover
    Create the following entries for each payment card
    AMEX          American Express     ZCCARD_CHECK_AMEX     Month
    DC          Discover Card          ZCCARD_CHECK_DC          Month*****
    MC          Mastercard          ZCCARD_CHECK_MC          Month
    VISA          Visa               ZCCARD_CHECK_VISA          Month
    The Routines can be created based on the original routines delivered by SAP. 
    *****SAP does not deliver a card check for Discover Card. We created our own routine.
    Define Card Categories
    Transaction:
    Tables: TVCTY
    Action: Define the card category to determine if a payment card is a credit card or a procurement card.
    Create the following two entries
    Cat     Description          One Card          Additional Data
    CC     Credit Cards          No-check          No-check
    PC     Procurement Cards     No-check          Check
    Determine Card Categories
    Transaction:
    Tables: TVCTD
    Action: For each card category map the account number range to a card category.  Multiple ranges are possible for each card category or a masking technique can be used.  Get the card number ranges from user community.  Below is just a sample of what I am aware are the different types of cards. 
    Visa Credit          Expires in 7 days.
                        400000       405500
                        405505       405549
                        405555       415927
                        415929       424603
                        424606       427532
                        427534       428799
                        428900       471699
                        471700       499999
         Visa Procurement          Expires in 7 days.
                        405501       405504
                        405550       405554
                        415928       415928
                        424604       424605
                        427533       427533
                        428800       428899
         Mastercard Credit     Expires in 30 days
                        500000       540499
                        540600       554999
                        557000       599999
         Mastercard Procurement     Expires in 30 days
                        540500       540599
                        555000       556999
         American Express Credit     Expires in 30 days
                        340000       349999
                        370000       379999
         Discover Card Credit     Expires in 30 days
                        601100       601199
    Set Sales Documents to accept Payment Card Information
    Transaction:
    Tables: TVAK
    Action: Review the listing of Sales Document types and enter “03” in the column labeled “PT” for each type which can accept a payment card
    Configuration for Authorization Request
    Maintain Authorization Requirements
    Transaction: OV9A
    Tables: TFRM
    Action: Define and activate the abap requirement that determines when an authorization is sent.  Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
    Define Checking Group
    Transaction:
    Tables: CCPGA
    Action: Define a checking group and enter the description.  Then follow the below guidelines for the remaining fields to be filled.
    AuthReq     Routine 901 is set here.
    PreAu          If checked R/3 will request an authorization for a .01 and the authorization will be
    flagged as such. (Insight does not use pre-authorization check).
    Ahorizon     This is the days in the future SAP will use to determine the value to authorize
                                 (Insight does not use auth horizon period).
    Valid          You will get warning message if the payment card is expiring within 30 days of order
                                 entry date.
    Assign Checking Group to Sales Document
    Transaction:      
    Tables: TVAK
    Action: Assign the checking group to the sales order types relevant for payment cards
    Define Authorization Validity Periods
    Transaction:
    Tables: TVCIN
    Action: For each card type enter the authorization validity period in days.
    AMEX     American Express     30
    DC     Discover card          30
    MC     Master card          30
    VISA     Visa               7
    Configuration for clearing houses
    Create new General Ledger Accounts
    Transaction: FS01
    Tables:
    Action: Two General Ledger accounts need to be created for each payment card type.  One for A/R reconciliation purposes and one for credit card clearing.
    Maintain Condition Types
    Transaction: OV85
    Tables: T685
    Action: Define a condition type for account determination and assign it to access sequence “A001”
    Define account determination procedure
    Transaction: OV86
    Tables: T683 / T683S
    Action: Define procedure name and select the procedure for control.  Enter the condition type defined in the previous step.
    Assign account determination procedure
    Transaction:
    Tables:
    Action: Determine which billing type we are using for payment card process.
    Authorization and Settlement Control
    Transaction:
    Tables: TCCAA
    Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
    Enter Merchant ID’s
    Transaction: 
    Tables: TCCM
    Action: Create the merchant id’s that the company uses to process payment cards
    Assign merchant id’s
    Transaction:
    Tables: TCCAA
    Action: Enter the merchant id’s with each clearinghouse account
    Reward if useful.
    Regards,
    Pramod.

  • Credit Card or Payment Card Processing

    Hello Forum members,
    I have tried to look for a thread in regards to "hiding/masking" a credit card number within sales order transactions (VA01,VA02 and VA03) but have not been able to find one exactly related to this.  I think I need some type of encryption processing maybe.  In addtion, the number should NOT display as previously entered within in the payment card number field as it happens with many of the field boxes withn SAP when hitting the back space key.   We are running ECC 6.0 and have been using credit cards for a couple of years, but as we are getting ready to increase the number of payment card transactions we will be accepting, we are revising our process to become 100% PCI compliant.
    Thanks in advance
    Jacob...

    Hai Jacob,
    USE T CODE: SHD0
    Record a sales order creation
    and save it.
    While saving system displays all the fields name with
    W.content
    Output only
    Invisible
    Required
    and select the field and put a TICK mark again the Payment card Number field
    Now
    T CODE: VOV8
    Open the sales order type and assign the Variant name and save it.
    This will hide the field in the sales order VA01, VA02, VA03  screen.
    Regards,
    Mani

  • Payment Card processing - SAP CRM 4.0

    We are in the implementation of CRM 4.0 with R/3 4.6c
    Card Types- Credit and Debits
    I have confusions in the following, I hope the experts would help-
    1. Manual Authorization - I understand from SAP help that CRM does not support manual authorization. The requirement here is to have the functionality in place for the manual authorization. Is this possible? I am sure it could be through custom way but do not have any idea as to how this can be achieved.
    2. Encryption - We need the Encryption to happen at BP as well as Transaction level. Can you please help me as to how this can be done? I am aware that at transaction level, SAP does it automatically, but it is not happening right now.
    thanks
    Yash

    resolved by self

  • Payment Card Processing - SAP Library

    To add a comment, please log in or register on the top of this page and choose Reply. Please write your comment in English.
    You can also go back to the SAP help page.

    Please see FAQ note :
    1034482 - FAQ: Credit card encryption in CRM

  • Billing document not cleared when processing Payment cards in Sales order

    Hi,
    I am having an issue with Payment card processing (credit card). We are using SAP R/3 4.7. When I use manual authorization, the status of billing document still shows "A" incomplete. The status shows authorization successful but not settled in billing document.The accounting document when billed shows not cleared.We are not using any interface for credit processing. The authorization check is done outside of the system manually. We are planning to use manual authorization for all such transactions. I am not sure if any specific config is to be done or am I misssing something.
    Any inputs in this regard would highly be appreciated.
    Thanks!
    Sanjay

    Hello Sanjay,
    Please also check to see if the field VBAP-ABFOR is filled for the line item (This is the Form of payment guarantee). Without this field filled the billing does not know that the item will be covered by payment cards.
    VBAP-ABGES (Guaranteed (factor between 0 and 1)) should also be filled with 1.
    I hope this helps.
    Best regards,
    Ian Kehoe

  • Payment card retrieved from customer master?

    hi gurus,
    i am using payment card processing. i want to know why i can only manually input card type and no in sales order although i have maintained the information in customer master. can anyone kindly tell me how can i set to enable auto retrieving card type and no from cutomer master into sales order? thanks a lot.

    Hi Daniel,
    i guess you havent missed any config and the payment card details wont copy to sales order by default. I am also working payment cards. Reason why it isnt set in config is, we may want to input a different card number at the time of sales order / or want to use two cards to authorize a sales order / or if one of the cards has expired or invalid then i want to input a second card info.
    Still if you want to pull in the info from customer master you may check with userexit_field_modification.
    let me know if you have more queries on payment cards.
    regards
    sadhu kishore

  • Payment Card Vs Procurement Card

    Hi Experts,
    I know that 'Procurement card' can be given as a payment method in External requirement / Purchase order in SRM. The same can be cnfigured under SPRO-->Supplier Relationship Management --> SRM server --> Procurement Card.
    However, I am not clear the 'Payment card' functionality under SPRO-->Cross Application components --> Payment Cards.
    Is both are same? If so why both are referring to two diffent configuration settings.
    If not, what is the functionality of Payment Card and where we can use in SRM transactions.
    Vasu

    Hi,
    Procurement card is a type of Payment card.
    Check this out please :
    Card used for cash-free payment in a variety of business transactions, from buying goods at a local store or over the Internet, to procuring goods and services on behalf of a company.
    The main payment card categories involved in payment card processing in the SAP environment are:
    Credit cards
    Used for purchasing goods and services with regular billing, usually with extended credit.
    Customer cards
    Used by customers to buy goods and services from a specific merchant or group of merchants.
    Debit cards
    Used as a means of cashless payment. The cardholder's bank account is debited instantly.
    Procurement cards
    Issued on behalf of companies to employees for purchasing items up to a given amount.
    Walking cards
    Issued on behalf of companies to employees for purchasing a wide range of goods and services for company travel.
    http://help.sap.com/saphelp_470/helpdata/en/93/745309546011d1a7020000e829fd11/frameset.htm
    The payment card functions in Sales and Distribution (SD) allow for sales involving these categories of cards, with the exception of walking cards, which are supported by Human Resources (HR), and debit cards, which are supported by Retail (SAP Retail) using point of sale (POS).
    Best regards,
    Sridhar

  • Payment card related question.

    Hi,
    I have a question related to payment card processing.
    Is there any authorization check happens with the sales order and clearing house or bank? If happens where we do configuration setting for that?
    Because for sales order configuration we have checking group setting.Through checking group setting we can maintain authorizaton requirement which takes care if there is any prerequisite for doing credit card check.
    But I did not find any link up between the sales order and clearing house or bank.
    In billing we can do authorization check with clearing house or bank through clearing house configuration setting in sap.But what about sales order? How to do the setting for that?
    Regards,
    Raj.

    Dear Raj,
    When you create a sales order with payment cards you will need to get an authorisation from your bank or clearing house. This means that the payment card details (credit card number, CVV number, amount to be authorised, name, expiry date etc) will be sent to the clearing house and a response will be returned. The clearing house will either give the authorisation or provide some details on why it will not give the authorisation (for example, not enough credit on the card, incorrect card number).
    You can check the customising in IMG:
    Sales and Distribution
    -> Billing
       -> Payment Cards
          -> Authorization and Settlement
             -> Maintain Clearing House
                -> Set Authorization / Settlement Control Per Account
    Here you can maintain the function module used to connect with your clearing house. The function module CCARD_AUTH_SIMULATION is provided as an example and for testing.
    The clearing house will be contacted during the saving of the sales order. The response will be given from the clearing house and the authorisation will either be successful or fail.
    I hope this information has helped.
    Best regards,
    Ian Kehoe

Maybe you are looking for