Illicit transaction through Credit Card

Hi there,
I'm asking on behalf of my relatives, there is an illicit transaction took place on my credit card.
Place : India , Bank: ICICI
Details :
Date : 07/22/2014 -
Ref number: 74313304203000790593592
Transaction details: iTunes.com/bill
Amount : xxxx INR
Same details for the rest of the two transactions on 08/05/2014 where ref ids are,
74313304217000012577948 & 74313304217000012577906.
Moreover, two new transactions of xxxx INR and xxx INR, reciting the same transaction details and having reference id as 74313304221000563841564 (Date : 08/09/2014) and 74313304224000014438850 (Date : 08/12/2014) respectively.
Could you please look into it?
Kindly reply with enough details.

This is a user-to-user support forum. Contact your credit card company and iTunes support. https://getsupport.apple.com/Issues.action

Similar Messages

I would like to know which bank is accepted as payment through credit card in istore

I would like to know which banks is accepted as payment through credit card in istore
Im planning to buy macbook air

You don't say where you are. Apple's Help pages for the USA store say:
The Apple Online Store U.S. accepts credit, debit, or check cards associated with a billing address within the 50 United States and the following U.S. territories:
American Samoa
Armed Forces Africa
Armed Forces Americas
Armed Forces Canada
Armed Forces Europe
Armed Forces Middle East
Armed Forces Pacific
Guam
Northern Mariana Islands
Palau
Puerto Rico
U.S. Virgin Islands
In the U.S., we accept:
American Express
Discover
MasterCard
Visa
(end quote). The bank actually issuing a card such as Visa or MasterCard is immaterial.
In the UK Apple accepts
VISA
MasterCard
American Express
Maestro/Switch
Solo
both credit and debit cards.

Payment to Vendor through credit cards?

Can anybody tell me is there any possibility to make payment to vendor through Credit Card.
If so, Plz tell wat are configuration steps in SAP FI.

Hi All,
Kindly suggest on this requirement.
Thanks & Regards
Deepak Garg

I am having mac book. I order for I-boost up software for $9.99 on 5th oct 2012 installed and paid through credit card. Again on 8th oct2012 my credit card debited with $9.99 please look into matter why this amount debited ,if wrongly debited please refun

I am having mac book. I order for I-boost up software for $9.99 on 5th oct 2012 installed and paid through credit card. Again on 8th oct2012 my credit card debited with $9.99 please look into matter why this amount debited ,if wrongly debited please refund.

Apple deosn't respond here, just other users like you.
iTunes Customer Service Contact - http://www.apple.com/support/itunes/contact.html > Get iTunes support via Express Lane > iTunes > iTunes Store

Payments through Credit Cards

Hi,
Just wanted to know that is there any option of Credit Card payments built in the Oracle Learning Management or we've to integrate it with some other Oracle Application (Order Management or iPayments).
Will appreciate the help.
Sharjeel

There is no delivered front end functionality for learners to purchase classes in OLM. There is integration with Order Management however as documented in the OLM User Guide:
<snip>
Using OLM with Order Management
The linkage of OLM with Oracle Order
Management (OM) enables independent training vendors to manage the ordering
and pricing of classes through a standard interface. Your customers can contact your organization’s call center and order a class or enroll a learner just as they would order a chair or a software package. OM then generates invoices and bills the customers through its interface with Oracle Accounts Receivable

In sales through credit cards , the amount is splitting .

Dear Community ,
I have problem with invoices which are being paid by credit cards . The authorized amount is splitting . For example , if invoice value is 500 , the amount is splitting as 400 , 70 , 20.5 , 6 ,2.5 , 1 .. the split is happening illogically and reconciliation of invoices is becoming very difficult .
Also in the corresponding sales order, in header- payment cards tab , this split is coming ...
Why this is happening . This is having a big impact as the customers are not preferring to buy though credit cards and sales are coming down .
request your inputs on this
Thanks and regards
Raghu

I think that this may not be an SAP issue. Is the authorization being taken from SAP directly?
Maybe you can check the middleware.
Rgds

Transaction PRCCF (Credit Card)

Hi,
I would be thankful if someone let me know the function of transaction PRCCF and how it is linked to transaction PRCCE in travel management.
The correct reply will be immediatly rewarded.
Thanks
KP

I could find answer myself

I am playing a online game called"éè£æ¦å£«", and i have paid cash for some items transaction via credit card account, but last day itunes store was blocked my transaction, may i know how to fix it?

may i know how to fix it and success the transaction

This is user to user forum, no Apple employees.
Try here:
iTunes Store Support
http://www.apple.com/emea/support/itunes/contact.html

Credit Card payment does not go on Credit hold..

Hi,
As per our normal procedure whenever a customer makes payment through "Credit Card" it goes on Credit Hold and than someone releases it from VKM1.
Now the problem we are facing is that suppose SO is of $1000 on 22/07/2009 and delivery is for only $600 on this day than as per our normal process the relaeser can only release $600 from VKM1. But this is not happening now, entire amount of $ 1000 is getting released on 22/07/2009 itself.
Kindly suggest how we can restrict this.
Thanks,

Hello Vk@sap,
In the standard process when you enter payment card details the order should not go on credit hold. VBAP-ABGES will be filled with 1 and the credit check should not be done. When we have an order that will be paid for by credit card all we need to know is if the clearing house (bank/credit card company) will give us the money. The customer's credit limit and history is not important to us if the bank guarantees us they will give us the money.
Is the authorisation being sought for $1000 or $600 in the sales order? Is it just the first schedule line that is being authorised in the sales order? In the standard system you cannot split an authorisation. So if you receive an authorisation for $1000 and only deliver $600 when you go to bill this the entire authorisation is used up. You will need to re-authorise the sales order (transaction VCC1) for the other $400.
I hope this helps.
Best regards,
Ian Kehoe

Mask Credit Card Details in sap?

Hi
We receive the payment through credit card, Is there any way to mask the credit card details (including credit card number) in SAP?

Hi,
follw the below steps for card processing
1. Maintain Card Types
SPRO-Sales & Distribution-Billing-Payment Cards-Maintain Card types
2. Setting up Merchant ID
SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House-Maintain Merchant IDs-Enter Merchant ID
3. Assign Merchant ID
SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House-Maintain Merchant IDs-Assign Merchant ID
4. Account determination
5. SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House- Account determination-Assign GL Accounts
Select Sls Org/Card cat.
6. Assign Clearing Account
SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House-Set Authorization/settlement control per account
Assign Clearing account
7. VA01- Enter Card details
8. Payment Card: Settlement-FCC1
Additional Transactions:
FCC2- Repeat settlement
FCC3-Delete Logs
FCC4-Display Logs
FBRC-Reset Cleared Items
FCCR-Standard Reports
VKM1-Credit Hold Report
VCC1-Payment card credit hold report

Error credit card information for service of Travel ESS

Dear Experts.
I have the following issue.
When I Create Travel Request in the ESS the system display the following message :
Please can help me with suggestion for solve this issue?
Regards

Hello Kris,
You can maintain the Customer credit card information in Customer master data - General Data - Payment Transactions. There you can see the Button called Payment Cards - Click on it, then you are faced with a screen Customer Payment cards and then Enter you customer Credit card Information like type (VISA/MASTER), Card Number , Validity dates etc.
The Payment Method field in Customer Master data - Company Code data - Payment Transactions tab, is responsbile for customer mode of payment after sales order creation. If the Payment Method is through Credit Card, during sales order creation the system will check the Payment method and If the Paymethod is credit, it will get the credit card details validated from third party system and get credited the sales order value amount.
The Pre-requisite is to develop the Interface with Third party service provider for Credit Card transactions (eg. XIPAY).
It is suggested to sit with your abaper and get the relevant user exit implemented to allow the credit card as a payment method in sales transactions with your customers.
Hope it helps.
Thanks, Ram.

REMOVING credit card information for existing AppleID

Ive noticed that iTunes is giving the newly users the option to use
a Credit Card or not. Ive been using iTunes for 5 years now, this has NEVER been a problem
till recently. Im using my credit card as my billing information, but now that
this keeps popping up...
This is overly irrating, my iPhone has updates on apps & my Macbook Pro
needs to be update! Ive been researching this problem, a lot of them do say there is a options
to chose, 'None.' I sure as **** dont see it. Hopefully Im not the only on with this problem.
PLEASE I NEED HELP

Hello Kris,
You can maintain the Customer credit card information in Customer master data - General Data - Payment Transactions. There you can see the Button called Payment Cards - Click on it, then you are faced with a screen Customer Payment cards and then Enter you customer Credit card Information like type (VISA/MASTER), Card Number , Validity dates etc.
The Payment Method field in Customer Master data - Company Code data - Payment Transactions tab, is responsbile for customer mode of payment after sales order creation. If the Payment Method is through Credit Card, during sales order creation the system will check the Payment method and If the Paymethod is credit, it will get the credit card details validated from third party system and get credited the sales order value amount.
The Pre-requisite is to develop the Interface with Third party service provider for Credit Card transactions (eg. XIPAY).
It is suggested to sit with your abaper and get the relevant user exit implemented to allow the credit card as a payment method in sales transactions with your customers.
Hope it helps.
Thanks, Ram.

Credit card integration in SD

Hi everyone,
Could anyone send me some links, or explain me something regarding credit card integration in SAP SD.
Thanks in advance.
I apprecieate your help

Dear Aditya,
I have worked extensively on credit card configuration. let me know you email id so that i can send the documents to you.
In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. Fig 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown fig 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to Fig 9.
Credit Card Configuration And Processing In SAP
Assign checking groups
Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. Fig 10.
Shows the transaction to maintain the field catalog.
Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6.
Credit Card Configuration And Processing In SAP
Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are
The condition
tables.
Credit Card Configuration And Processing In SAP
Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types.
Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
Sales Order Cycle With Credit Card
Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described . The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in Fig 1. And the
remaining lines represent the actual authorizations that are carried out.
Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

CREDIT CARD SAP

Dear All,
Can I have some information related to Credit Card in SAP.
Please mail me on my mail id [email protected]
Regards,
George

Dear George,
Please find the relevant details related to credit Crads as follows:
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

Credit Card Configuration in SAP

Dear All,
Can I have the information on Credit Card Configuration.
Regards,
Geroge

Dear George,
Please find the relevant details related to credit Crads as follows:
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

Illicit transaction through Credit Card

Similar Messages

Maybe you are looking for