Credit CARD Authorization and authentication

we are taking following input from user
credit card number
cvvno
card expiry date(Month and Year)
Card Holder Name (As appear on card)
how can we do Master card Authorization and authentication

Credit Card Authorisation means - When you swipe your card at any merchant outlets, it depends upon the merchant aggrement with the Acquirer Bank the transaction will taken plance either online or offline.
Below the merchant floor limit , merchant will authorise the transaction and the same will be send as settlement at the end of the Day by merchant to Acquirer Bank.
Online means, the transaction will be acquired at merchant outlet and the transaction message send to acuirer bank- if the transactions belongs to acquirer bank then, Acquirer will approve the transactions and the response will be send back to the merchant to approve the transactions.
If the transactions not belongs to acquirer bank ( off_us transactions ) then the transactions will be sent to service provider ( VISA / MASTER CARD / DINNERR CLUB etc ).. then Payment Gateway will route the transactions to the Issuer and Issuer will approve / decline the request and send back the response , in the same way the acquirer bank will receive the resoponse and forward the same to the Merchant to approve or decline the transactions.
The question which you had asked is simple - but it is too big, because, I can give you the answer in one line as well as in depth more techincal in 1000 lines too..
In case if you are more intersted to know about the credit card / debit card transactions and the pin authentication part.
Please feel free to contact me on the below given e-mail ID
Mention in the mail - SUN Forum Friend --
[email protected]
Thanks & Regards
Ravi Kumar G

Similar Messages

How Credit Card Authorization/Settlement in SAP is handled?

Hi,
Does SAP ECC has any in build credit card authorization mechanism or we have to use third party tool like payment metric's (payment card interface) application for credit card authorization and settlement?
From what I read on internet and this forum, Biller Direct seems to provide an interface for customers to pay invoices using credit card but did not find anything about how credit card information is processed.
I would greatly apprecitate if anyone can give me pointers on some best practices for credit card authorization from SAP ECC.
Thanks,
Paresh

Hi;
Let me try to explain a real life scenario.
Let us say u r buyong something from Amazon and assume Amazon is using SAP in the b/g. When you submit the Order it flows through an interface and perhaps they create an idoc and and SO is created in SAP.
Now there is a prg RV21A010 in SAP which will send the CC details through your interface to the Payment processor. This is the authorization process. Once the card is accepted, the money is blocked on the CC. No money is taken as yet.
Now, the Sales cycle is completed and the billing is created and at this point we need to settle the CC transaction. For this we have a prog RFCCSSTT in SAP and this wld send the transaction details to the processor and the settlement is done.
Well this is scenario in 4.7, i am sure something of this sort should be there in ECC as well.
Let me know if you are looking for information in this regard.
Regards,
Mani

How do I remove payment information from my account, like the credit card number and information?

*NO THIS DOESN'T HELP ME AT ALL*
V V V V V V
"Symptoms
When there is a mismatch between the iTunes Store's records and your credit card company's records, you will receive an error message stating that your credit card's security code isn't valid or that your zip code does not match your bank's records.
Resolution
In most cases, this issue is caused by a formatting error in the billing address that you have provided. You can correct the issue by verifying that the information you have provided is correct, or by changing the format of your address to match the format that your credit card company has on file.
You can verify and/or modify your billing address by following these instructions:
Open iTunes. If you are signed in to iTunes, skip to step 4.
Note: Verify that you are signed in to the correct iTunes account. If you are unsure which account you're signed into, choose Store > Sign Out and proceed to step 2.
Choose Store > Sign In.
Enter your account name and password, then click the Sign In button.
Choose Store > View My Account.
Click the Edit Payment Information button.
In the Payment Method section, choose None.
Click the Done button at the bottom of the page.
Click the Edit Payment Information button again.
Enter your billing address exactly as it appears on your credit card statement.
Select your credit card type in the Payment Method section.
Enter your credit card information, your card's security code, and the expiration date.
Click the Done button at the bottom of the page.
If the issue persists, contact your credit card company and verify that they and any company they use to process credit card authorizations have the correct information on file."
iPod touch, iOS 5.1.1

I cant find the edit payment information, and everytime i try to delete the information it only says payment option declined then it refreshes and the same information is there

Credit Card authorization error while creating an online sales order in ISA

Hi All,
I did the basic configuration for the webshop for B2C functionality in ISA R/3. When I choose a product from the product catalog, add it to a shopping cart, choose credit card option, enter a valid credit card and expiration date and confirm the order I get the error 'Unsuccessful credit card authorization'. But I can create an order successfully using VA01 transaction in R/3 with the same header and item level data and the credit card data. What can be the reason behind this error and how to fix it? Please let me know.
Thanks in advance.
--R D

Did you fix this issue?

Use of external credit card Authorization code

Hi All,
I am working on a requirement where I am getting an Authorization code for the credit card order from an external payment processor. Now I have to create a Sales Order using process order API by passing the authorization code. The Sales order will be created with the authorization code information.
I want AR to use the same approval code in order to do the final settlement.
Does anybody know if it work like this.
Thanks,

In 11.5.9 this was not possible.
Thinking loud..
You have legacy system which got credit card authorization. YOu have not shipped goods yet, but have blocked funds on their cards.
Now you are moving to Oracle. This will be hooked to your credit card authorization company (say cybersource or payment tech).
You can conver the order with the same authorization code.
But there is nothing in the iPayment tables (IBY in R12) as far as the order line is concerned and neither in the the CC authorizing company.
Hence you cannot use the same authorization code for payment settlement when the order gets invoiced.
This requires not only converion in iPayment and your CC authorizing company, which I think is overwhelming.
So the best think you do is to clear as many order as you can in legacy and manage payments in AR manually.Usually we stopped taking the CC orders 1 month ahead. Your insdustry may not allow that.
You can cancel the orders, let the customers know when converting, reauthorizing in Oracle again.
HTH.
Thanks
Nagamohan

Credit Card Authorization for Confirmed Delivery Date

When a credit card order is placed and the confirmed delivery date is beyond the expiration date on the credit card SAP allows the order to be placed and authorized. If the confirmed ship date is beyond the expiration date of the card then shouldn't SAP block the order? Currently, it is not doing this in our systems.
Is anyone aware of how to change SAP to check if the confirmed delivery date is passed the expiration date of the credit card?
Many Thanks!
Kyle

Hi Deborah Bourgeois,
There is no Credit Hold check box enabled in the Customer window, We are getting same error in order management too.
Scenario 1:
When we set the profiles like below iStore,OM,AR order getting confirmed with Hold and tangibleId is starting with as shown below
TangibleId:
iStore = ASO%.
Order Management = ONT%.
AR Manual orders = AR%
Profiles:
ASO: Credit Card Authorization = No
IBE: Perform Payment authorization = Yes
ASO: Default Order State profile = Booked
Scenario 2:
When we set the profiles like below iStore,OM,AR order getting confirmed without any Hold and all the tangibleId is starting with ONT%
ASO: Credit Card Authorization = Yes
IBE: Perform Payment authorization = No
ASO: Default Order State profile = Booked
Our Expectation:
1. Order should be confirmed with out any Hold.
2. Tangible id should as below
a. iStore = ASO%.
b. Order Management = ONT%.
c. AR Manual orders = AR%
3. All this should work for iStore when the below profile is enabled
IBE: Perform Payment authorization = Yes
Could you please help me on this.
Thanks
Vino.

Is there a template available for a credit card authorization form?

Is there a template available for a credit card authorization form? (Something professional looking along the lines "I authorize a one time payment in the amount of...select Mastercard, Amex...billing addresss...3 digit code...) Thanks

There probably is, but before you go to far with a PDF form for such information you need to consider how it is to be used.
E-mail is a definite no. Even standard web submission is not acceptable. You would want to submit to a secure web site. If that is the case, it might be better to just use standard HTML processes, but at least https is a needed protocol for things such as credit cards and other personal information. I always look for "https" on line and would probably refuse to use a PDF form that asked for my credit card because of a concern about proper handling. Messing this up could lead to a big law suit against you, suggesting why so many firms just use a payment service.

Credit card authorization

I am building a shopping cart E-commerce application.
How can I get a credit card authorization? i.e How can I call a credit card company services to get credit card approval?
How should I get a secure connection between my company network and credit card company?
What amount of code do I have write?
I am very new to building E-commerce applications. So please explain me in detail about the process.
Can you also suggest me articles or tutorials that explain this phenomenon....
Any help would be appreciated.....
Thanks.

Your system designer should already have given you all this information.
If you are the designer you should know where to look, and a Java Servlets forum isn't it.
Locking this thread.

HT3702 Hey guys! I have a problem with my billinng information. I enter my credit card information and appear the last three digitas number wrong. What happend?

I have a problem with my billing information.

If you mean the security code on the back of the card, then is the address on your iTunes account exactly the same (format and spacing etc) as on your credit card bill : http://support.apple.com/kb/TS1646 ? If it is then you could try what it says at the bottom of that page :
If the issue persists, contact your credit card company and verify that they and any company they use to process credit card authorizations have the correct information on file.
And/or try contacting iTunes support : http://www.apple.com/support/itunes/contact/

Re-authorizing an expired credit card authorization

Hi,
I am trying to find out whether re-authorising an expired credit card authorisation taken at the point of an order being placed will duplicate the amount ring fenced on the customers card. The documentation I have seen suggests that the funds are released and a re-auth will not duplicate the amount. We have the scenario where the customers using CC are bad payers therefore at the point the web order is taken we would like to ring fence the money unfortunately the requested delivery date could 3 weeks away and VISA auths generally last for 7 days before expiring.
Any experience or advice on this would be greatly appreciated.

Hello,
You can maintain the authorisation validity periods in the customising to keep the authorisation for longer than 7 days (SAP Customizing Implementation Guide -> Sales and Distribution -> Billing -> Payment Cards -> Authorization and Settlement -> Specify Authorization Validity Periods) but I think you might be referring to how long VISA will keep the authorisation for.
Perhaps your clearing house could provide you with more details on this.
Bear in mind that even if you request an authorisation in the sales order in 3 weeks time you can stop the delivery from being created if no valid credit card authorisation has been received. If no authorisation is received from the clearing house no goods will be delivered to the customer so there should be no problem.
Best regards,
Ian

Multiple Credit Card Authorization

We use credit cards, but also do many partial deliveries against a sales order. It seems that when we have a partial delivery against an open sales order the system overauthorizes the credit card.
Example:
Order
Line Item 10 = $200
Line Item 20 = $100
Total Authorization = $300.
If a delivery note is created against line item 10, but it is not picked or PGI'd and we run the credit authorization program the system creates another authorization for $200 (amount on the delivery), which causes a total authorization of $500 on the order, although the net value of the sales order is only $300. I believe this is due to how Open_Values is populated in function Group V21F.
Has anyone run into similar issues with credit cards and partial deliveries? If so how did you resolve? Doing a Ship Complete is not an option for us based on our business processes.
Thank you for any help you can provide.

Hi Molly,
What did you discover here. Sorry, I know this is an old thread. We are experiencing credit cards remaining with open authorizations because inconsistencies happen between the billing plan and the payment card entries. When the order-related billing fails to post, the credit card authorization remains open and gets triggered each time the order is opened.
We are doing 2 things to manage this - first we are going to try to require the payment card and billing plan information to be synchronized. Next, we are going to use the VOFM routine to wrap the credit card authorization function in a custom function to implement business logic to suppress the call under certain conditions.
I really wish there was an explanation somewhere in regards to what causes a credit card authorization request.

Testing credit card authorization scenario using B1 TC

In the image below you can see that the credit card authorization is enabled only for 'Sales Order' screen. Also the credit card payment term is set as 'ZP10NET30'.
Here the expected behavior of our add-on is that, on adding a Sales Order the add-on should prompt "Would you like to authorize this document?" if the customer's payment term matches with the credit card's payment term(in this case 'ZP10NET30'). If Yes is clicked with the prompt, then the lastly added document should be loaded back to the Sales Order screen and a Card Authorization window should be loaded. If No is clicked then the sales order should be added with out loading the Card Authorization window.
Can B1 Test Composer be used for handling such scenario?
Regards,
Sam

Hi Sam,
in my opinion you should prepare database with specific data that encompasses a scenario you test (e.g. with record that causes the prompt appears). Then before running a scenario you should restore prepared database. In test script you can include e.g. "CompareItem" line comparing text label in appeared message form.
Regards,
Winicjusz

IPayment for Credit Card Authorization error IBY_0005 - Inavalid account

Hi All,
We have an issue with iPayment auth when I try to do check on iStore
using test credit card numbers. We have implemented veri sign paymentech
as back end processing servlet.
question is vpsipayment.properties file has parameter that sets host name
for real time and test time processing. After setting
hostname=test-payflow.verisign.com it's still pointing to real time auth.
All pointers are highly appreciated
Regards
Siva

Hi Deborah Bourgeois,
There is no Credit Hold check box enabled in the Customer window, We are getting same error in order management too.
Scenario 1:
When we set the profiles like below iStore,OM,AR order getting confirmed with Hold and tangibleId is starting with as shown below
TangibleId:
iStore = ASO%.
Order Management = ONT%.
AR Manual orders = AR%
Profiles:
ASO: Credit Card Authorization = No
IBE: Perform Payment authorization = Yes
ASO: Default Order State profile = Booked
Scenario 2:
When we set the profiles like below iStore,OM,AR order getting confirmed without any Hold and all the tangibleId is starting with ONT%
ASO: Credit Card Authorization = Yes
IBE: Perform Payment authorization = No
ASO: Default Order State profile = Booked
Our Expectation:
1. Order should be confirmed with out any Hold.
2. Tangible id should as below
a. iStore = ASO%.
b. Order Management = ONT%.
c. AR Manual orders = AR%
3. All this should work for iStore when the below profile is enabled
IBE: Perform Payment authorization = Yes
Could you please help me on this.
Thanks
Vino.

Credit Card Authorization Process

Hi All,
I have a problem here. We implemented the credit card functionality and we also enabled the batch job RV21A010 which will run every day to pick up the expired authorization and also it picks up the orders coming within the horizon. Now we have some orders where the time gap between the delivery and the billing is huge and by the time the billing happens the authorization has expired. My doubt here is does the job RV21A010 willkeep authorizing the expired authorization till the accounting document is cleared. I tried looking into the program and it doesn't seem to be taking any indicator by which it finds out the open billing documents. Please help me as this is urgent and we are facing serious problems because of this.
Thanks and Regards
Arvind

Hi Arvind,
The program reauthorizes. We have tested this in our system
we had a scenario where we get Debit memo request from CRM 45 days ahead of billing date and hence no authoirzation.
We have run this program and it picks up these document when they come up withthin the Authorization Horizon (maintained in checking group).
Regards
BgS

Credit Card config and encryption

Hi frnds
I would appreciate if anyone can provide the config steps for credit card and also the step for encrytion. If you have a doc on it then please mail it to [email protected]

hi
CREDIT CARDS
Go thr below links:
PAYMENT CARDS:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf
http://help.sap.com/saphelp_erp2005vp/helpdata/en/93/745309546011d1a7020000e829fd11/frameset.htm
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 ID’s
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 cardholder’s bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP

Credit CARD Authorization and authentication

Similar Messages

Maybe you are looking for