credit card

[Former Member]

Friends,

I have completed configuration for credit card processing. Accomplished following task.

Specify Debit card number in customer master.

While creating Sales order I am entering card number & also giving authorization manually in Header - payment data by giving authorization number.

In billing document after saving i could see payment card plan.

Pl guide me somebody has to how this can be use when actually we used crdit card processing.

i mean what else I should do if i want to test everything in real time.

i.e. when & where we can scrap card, how data is fetch to sap. How it updated the bank account. What are the diff module we must implement in sap.

Thanks

[Former Member]

Hi Shiv,

I am having problem with entering Credit card no: in customer master, it says invalid card no:.

I goto SD- billing- payment card- maintain card category- determine card category and enter a 6 digit no: range for Master card, can i enter any no:? I got the no: range from this forum:

Mastercard Credit Expires in 30 days

500000 540499

540600 554999

557000 599999 but it doesn't work, I am confused about what to enter for number range in determine card category and what to enter in customer master? Please help.

Thanks

[Former Member]

Dear Shiv patil,

I will suggest you to visit http://sap-img.com/sap-sd.htm.

There is a separate section on CIN in the link I have given you. Trust me if you go through all the links you will have a fairly good idea of the CIN.

Do let me know in case of any queries.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

[Former Member]

Dear Rakesh,

Thanks I need information on Credit card processing.

How this process carried out at enduser level.

Thanks

[former_member202002]

Shiv,

Part of the configuration allows you to specify either an external authorization routine or to use the SAP supplied simulation authorization routine for obtaining automatically the authorization which you are now entering manually.

I would recommend that you start by using SAP's simulation function for authorization (CCARD_AUTH_SIMULATION) so that you can test the business logic and workflow of SAP's payment card processing functionality.

Here are links to SAP's Help Portal that should give you some good background:

Start here: [Payment Card Processing (SD-BIL-IV)|http://help.sap.com/erp2005_ehp_03/helpdata/EN/93/745395546011d1a7020000e829fd11/frameset.htm]

These two links should give you some specific details about the authorization simulation function and clearinghouse connectivity:

[Payment Card Interface to Clearing Houses|http://help.sap.com/erp2005_ehp_03/helpdata/EN/93/745395546011d1a7020000e829fd11/frameset.htm]

[Assigning a G/L Account to a Cash Clearing Account|http://help.sap.com/erp2005_ehp_03/helpdata/EN/f4/71bb6f7b1c8d44bb33e23d91ffdfd2/frameset.htm]

If you'd like additional detailed information about setting up a link between SAP and an external credit card processor you can download a whitepaper from Paymetric, the company I work for, [here|http://www.paymetric.com/Resources/Whitepapers/Processing_Payment_Card_Sales_Transactions_in_SAP/].

Eric Bushman

Edited by: Eric Bushman on Feb 14, 2008 10:12 AM

[Former Member]

hi,

let me just share my experience of our credit card implementation on ESOA architecture.

the Credit card details are entered at the sales order level and we do an online authorization connecting the SAP system to 3rd party verification systems via SAP XI a product of netweaver technology. Here we have maintained the required codiing in both ABAP as well Java to talk to the interface. The info from SAP now goes to 3 rd and it validates the amount and authenticity of the card. The response is received and we allow the order to go for delivery. In the billing with help of CC details in the payment card at header level we will be able release the revenues to accouting document against a payment receivable account for accoutng doc type RV. Finally we run the settlements against a settlement account with FCC1.

Modules required were SD,FI, Abap and XI and Java professional. For this you need a very competent abaper

since there would be lot of customizations required at the copy contrl level, user exits and new function modules for authorizatin.

regards

sadhu kishore

[Lakshmipathi]

Dear Shiv

Go through the link and ensure that your settings are in line with the links therein listed

[Overview of Functions |http://help.sap.com/saphelp_46c/helpdata/en/e3/c3ad03909311d194bf00a0c92946ae/content.htm]

Thanks

G. Lakshmipathi

[Former Member]

Dear Lakshmipathi,

Thanks for providing proper guidance. However could you please explain the step involved in processing of credit card.

I am in need of , how enduser performed his activities when it comes to use of credit card.

How many module we need to implement if we want to use credit card.

Thanks

[Former Member]

Set Up for Credit Card Payment Processing

Given below is the set up for credit card payment processing:

Set Up Credit Control Areas:

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.

Set Up Payment Guarantees

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

Payment Card Configuration

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).

A horizon 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 points if useful.

[Former Member]

I am having problem with entering Credit card no: in customer master, it says invalid card no:.

I goto SD- billing- payment card- maintain card category- determine card category and enter a 6 digit no: range for Master card, can i enter any no:? I got the no: range from this forum:

Mastercard Credit Expires in 30 days

500000 540499

540600 554999

557000 599999 but it doesn't work, I am confused about what to enter for number range in determine card category and what to enter in customer master? Please help.

[former_member202002]

I personally don't use the BIN range configuration. I would just set the configuration to a '*' to allow entry of any card number. The card validation routine that is configured for that card type will validate that the number entered is a correct "Visa" card number or "MasterCard" number.