Credit Card Processing For Microsoft Dynamics AX 2012

Microsoft Dynamics AX 2012
Credit Card Processing

White Paper
This paper provides an overview of the credit card processing
functionality of Microsoft Dynamics AX 2012. It describes how to
set up credit card processing and provides an overview of the
development approach to use with credit card processing.
Date: November 2011
www.microsoft.com/dynamics/ax
Biplob Ghose, Program Manager
Send suggestions and comments about this document to

adocs@microsoft.com. Please include the title with your
feedback.
Table of Contents
Introduction ................................................................................................ 3
Credit Card Processing Feature Concepts .................................................... 3
Setting up Credit Card Processing ............................................................... 4
Security ............................................................................................................................... 4
Payment Services ................................................................................................................. 5
Payment Services for Microsoft Dynamics ERP ....................................................................... 5
Address verification............................................................................................................ 6
Card verification value ........................................................................................................ 6
Demo data ........................................................................................................................ 6
Set up Cards ..................................................................................................................... 7
Terms of Payment ................................................................................................................. 8
Customers ..........................................................................................................................11
Customer settings for address verification and card verification values .......................................14
Credit Card Parameters ........................................................................................................15
Sales Order setup ................................................................................................................16
Processing an authorization ...................................................................................................18
Processing an authorization with card verification values enabled ...............................................19
Processing an authorization ...................................................................................................20
Sales order ...................................................................................................................... 20
Sales Pickup (Will Call) ...................................................................................................... 21
Warehouse management ................................................................................................... 23
Creating a payment journal ................................................................................................ 23
Partial shipments .................................................................................................................23
Batch processing .................................................................................................................23
Merging sales orders ............................................................................................................23
Refunds ..............................................................................................................................24
Voiding an authorization .......................................................................................................24
Credit card issues ................................................................................................................25
Intercompany processing ......................................................................................................25
Technical Information ............................................................................... 26

Payment Services for Microsoft Dynamics ERP (PSMDE) ............................................................26
Security ..............................................................................................................................26
Error Messages ....................................................................................................................26
Transition from Authorize.Net to Payment Services for Microsoft Dynamics ERP ...........................26
Appendix A................................................................................................ 28
Information provided in Level 2 data support ..........................................................................28
Information provided in Level 3 data support ..........................................................................30
2
CREDIT CARD PROCESSING
Introduction
Customers often pay invoices using one or more credit cards.
This paper describes how to automate the processes of authorizing a credit card amount at the time of
an order and then capturing the charge when the order is shipped and invoiced. It also provides an
overview of the development approach to use with credit card processing
This paper is intended for professionals who are involved in the implementation and support of the
credit card processing functionality at a customer site, as well as for those who need to advise
customers, or make modifications within the area.
Credit Card Processing Feature Concepts

The feature is designed to support payment services providers that can accept approval requests from
Microsoft Dynamics AX and return the results back to Microsoft Dynamics AX. Two types of approval
requests are supported:
1. Authorization, in which the invoice amount is set aside by the payment services provider against
the cardholders credit limit.
2. Capture, in which the invoice amount is actually charged to the card holder.
Figure 1 illustrates the processes that can be used with this feature:
Figure 1: Credit card processing feature concepts

3
Setting up Credit Card Processing

Access to the credit card processing feature is controlled by security privileges. After security has been
configured, you must configure payment services, terms of payment, and customers.
Security
The following privileges are assigned to various duties and roles to ensure that credit cards are
processed by only authorized users in Microsoft Dynamics AX 2012:
Security Privilege
Description of the privilege
Authorize credit card information
Process a credit card in the sales order form
Maintain credit cards using a wizard
Create and modify a credit card
Maintain customer credit card

information
Delete a credit card
Maintain customer payment services
Modify the settings used to access the payment services provider
Set up credit cards
Modify the settings that control the credit card processing parameters
View credit card history information
View credit card transaction history
View credit card issues information
View open credit card issues
View customer credit card information
View customer credit card information
In all cases where the user can view credit card information, only the last four digits of the credit card
are shown.
4
Payment Services
The Payment services form allows you to activate a payment services provider by providing logon
information and additional parameters. Credit cards cannot be processed unless one of the payment
services providers is set to Active.
Figure 2: Payment services form

The Payment Services for Microsoft Dynamics ERP (PSMDE) provider is the default payment provider
used by the credit card processing feature.
Payment Services for Microsoft Dynamics ERP

Use the Payment Services for Microsoft Dynamics ERP tab to enter the information that is required to
connect to the PSMDE service.
You must connect with the PSMDE service to obtain your Payment service account. After you sign up,
the account information will be returned to Microsoft Dynamics AX. Because you are allowed to have
multiple payment services account IDs, you must select the one that you will use for this legal entity.
When you click the Sign up now button, the PSMDE sign up screen is displayed, where you can
register for the service. Click the Manage Account button to view the PSMDE administrative area,
where you can manage your PSMDE account.
PSMDE also has a test mode that allows you to test transactions before you go live. When the Test
mode check box is cleared, live transactions will be processed by PSMDE.
5
Address verification
You can use address verification as a criteria for accepting a credit card. Address information is always
sent to Payment Services for Microsoft Dynamics ERP. However, if you select the Address
verification check box, a transaction can be automatically voided if the address is incorrect.
Payment Services for Microsoft Dynamics ERP replies to the address verification request with a result
that indicates how accurate the address is. The value of the Address verification status required
to accept transaction field determines which action is taken. The result of the verification is
compared with the setting that you select. If the result is equal to or better than the value selected,
then the transaction is accepted. If you select the Void transaction when no results are available
check box, the credit card transaction will be voided when the result shows that address verification
was not available.
Card verification value

You can require the card verification value (CVV) to be entered and verified by Payment Services for
Microsoft Dynamics ERP. When the Prompt for card validation value check box is selected, you will
be prompted for a card verification value when you process an authorization.
Figure 3: Card verification value form

The card verification value will be sent to Payment Services for Microsoft Dynamics ERP. If the card
verification value is not correct, the transaction will be declined.
To specify that a blank card verification value can be sent, select the Allow blank card verification
value check box. A blank card verification value means that no verification will be done when you do
not fill in the card verification value on the form.
Demo data
You must sign up for Payment Services for Microsoft Dynamics ERP to demonstrate the credit card
feature. When Test mode is selected in the Payment services form, you can process transactions
for demo purposes without creating real transactions.
6
Set up cards
Microsoft Dynamics AX2012 supports four credit card types: VISA, Master Card, American Express,
and Discover. Each of these card types has additional settings that control the credit card process. To
change these settings, click the Set up cards button on the Payment services form.
A credit card transaction is automatically posted to a cash journal when a transaction is complete.
However, a typical company may have different merchant accounts at the payment services provider.
To support this scenario, individual payment journals can be specified in the Credit card types form
for each type of credit card. In addition, credit card payments are credited to a merchant account and
are not received as cash immediately, so a credit cards receivable account should be used for the
journal. After the cash is received from the merchant, it can be reconciled against this account and
posted to a cash account.
To ensure that only valid currencies are used in sales order transactions, you must enter a list of
currencies that are supported by the payment services providers that you have selected. The default
currency is USD. You can add additional currencies.
The default data support value is Level 1, which represents basic information that is provided by
Microsoft Dynamics AX to Microsoft Dynamics Online Payment Services, such as transaction date,
transaction amount, and description.
Figure 4 shows the Credit card types form, with level 1 data support selected.
Figure 4: Credit card types form

Microsoft Dynamics AX supports the transmission of Level 2 and Level 3 information through Payment
Services for Microsoft Dynamics ERP.
Changing the data support level to Level 2 or Level 3 increases the amount of information that is sent
to Payment Services for Microsoft Dynamics ERP. You can also override the data support setting for
each card at the currency level to match the capabilities of the processors that you have selected. See
Appendix A for a list of the values that are sent when Level 2 or Level 3 is selected.
7
Terms of Payment
In Microsoft Dynamics AX 2012, the Terms of payment form has been modified to identify the terms
of payment that will initiate credit card transactions.
Figure 5: Terms of payment form
8
A new payment type called Credit card has been added in Microsoft Dynamics AX 2012. Figure 6
shows the Terms of payment form, with Credit card selected for Payment type. You can maintain
backward compatibility with certain earlier versions of Microsoft Dynamics AX by using a blank
payment type. A blank payment type does not use credit card functionality when it is selected for a
term of payment. By default, all terms of payment are assigned to a blank payment type during the
upgrade process.
Figure 6: Terms of payment form and payment type
9
In Microsoft Dynamics AX 2012, a Credit check field has been added to allow you to bypass credit
limits when using a credit card. If a customer has exceeded their credit limit and you require the
customer to pay by cash or credit card, this field allows you to select the Bypass credit check value
to bypass the credit check. The Bypass credit check value will be used only when the payment type
is Credit card. The value Normal indicates that normal credit checks will be made when this term of
payment is used. To maintain backward compatibility with previous versions, the Normal value is
assigned by default during the upgrade process.
Figure 7: Terms of payment credit check settings
10
Customers
Credit card information can be added to a customer account at any time before or during the sales
order process. To maintain security, all credit cards must be entered through a Credit Card Wizard.
To access the wizard, click the Credit card button in the Set up group on the Action Pane in the
Customer form or the Sales order form.
Figure 8: Setting up credit cards from the Customer form
11
When you click Credit card, the Customer credit cards form displays the existing credit cards for
the customer. You can add new credit cards or modify existing credit cards with this form. However,
the form does not allow you to directly modify the form. All changes must be made through the
Credit Card Wizard to increase the level of security provided by the application.
Figure 9: Customer credit cards form
12
The Credit Card Setup Wizard is a series of six pages that request cardholder information and the
credit card number. After you have completed the wizard, the credit card information will appear in
the Customer credit card form, and the credit card will be available for use in a sales order.
Figure 10: Credit Card Setup Wizard
13
Customer settings for address verification and card verification

values
By default, Microsoft Dynamics AX uses the settings that are on the Payment services form to
manage address verification and card validation values. You can override those settings on the
Payment defaults FastTab on the Customers form. When credit cards are processed, Microsoft
Dynamics AX will use the customer settings if they are different than the default settings
Figure 11: Customer settings for address verification and card verification values
14
Credit Card Parameters

A Credit card tab has been added to the Accounts receivable parameters form so you can add
default settings that will be used during credit card processing.
Figure 12: Accounts receivable credit card parameters

The Credit card authorization check box determines whether or not the credit card will be
authorized when you process the order. If this check box is cleared, the credit card will not be
validated until it is invoiced.
The Credit card note is the default text that will be provided to the payment services provider for
use on the customers credit card statement. This text is overridden by the Credit note setting from
the Credit Card Wizard.
The Estimated freight charge settings determine the amount of the additional charge that will be
added to the credit card authorization. In many cases, you may not know the actual freight charges
that will be calculated when an order is invoiced, so the estimate ensures that the credit card is
authorized for a sufficient amount to cover the freight. Estimated freight charges can be calculated as
percentages or as fixed charges:
Percent adds a percentage of the order amount before tax, up to the maximum amount, to the
authorization.
Fixed adds the Value setting to the authorization.
15
The Credit card payment posting group defines the default settings that will be used when the
payment journal is posted after a credit card is accepted. To override the settings, select different
methods of payment on the Price and discount tab in the Sales order form.
The Data support setting identifies which dimension will be transmitted as the cost center when
using Level 2 or Level 3 data support.
Sales Order setup

A credit card can be used on a sales order to pay for the order when the invoice is posted. Credit cards
are selected on the Price and discount FastTab in the Sales order form.
Figure 13: Selecting a credit card on the sales order

To use a credit card, you must assign a payment type that has been associated with the credit card
option during setup. After this payment type is selected, the Credit card number field becomes
active and you can select a credit card in the Credit card number field. Only one card can be
selected for an order and cash discounts will not be applied to the order.
16
If a credit card does not exist for the customer, you can click the Register button in the Manage
group on the Action Pane to select Credit Card Wizard. After you have used the wizard to create a
credit card, the card number is automatically added to the order.
Figure 14: Selecting the Credit Card Wizard on the Sales order form
Note: If you have selected a currency, a method of payment, or a credit card payment posting setting
in the Accounts receivable parameters form that results in a currency that is not represented in
the Credit card types form, you will not be able to process the credit card with the payment services
provider.
17
Processing an authorization
If the Credit card authorization check box is selected in the Accounts receivable parameters
form, the authorization will occur automatically when you post the picking list or packing slip. You also
can use the Credit card option in the Manage group on the Action Pane, and select Authorize to
authorize the credit card before sending the order to the warehouse for picking or packing.
Figure 15: Preauthorizing a sales order

After the authorization is complete, an Infolog displays the results of the authorization.
Figure 16: Infolog showing the results of credit card processing
18
To open the Credit card history form to see the details of the authorization, click the Credit card
option on the Manage group on the Action Pane, and then select Authorization history on the
Sales order form.
Figure 17: Credit card authorization history

Every attempt to authorize or capture a transaction is stored for the order and displayed on this form.
If a transaction is declined or you are having difficulties with the network connection, you will be
provided additional information in the Infolog message shown in Figure 16 and in the Description
column in the form in Figure 17.
Processing an authorization with card verification values enabled

If card verification values are enabled, the Card verification value form will be displayed when you
select Authorize from the Credit card option on the Manage group in the Action pane to authorize a
card. The value is checked for a valid length of three digits for Visa, Master Card, and Discover and
four digits for American Express. If blank card verification values are not allowed, Microsoft Dynamics
AX will only allow the authorization to be performed when a value is entered.
The form uses the card verification value settings for the customer to determine if card verification
values must be entered. If the settings have not been selected for a customer, the setting entered in
the Payment services form is used.
19
Processing an authorization
Credit cards are captured when an invoice is posted. There are three ways to post invoices that will
process the credit card:
Sales order
Sales pickup
Warehouse shipment
Sales order
A credit card is captured automatically when you post the invoice from the Sales order form. The
Infolog message shown in Figure 16 will appear when the credit card has been processed. An
additional entry will be added to the Credit card history form, noting the actual amount charged to
the credit card.
Figure 18: Credit card history
20
Sales pickup (Will Call)

The Sales pickup form has been added to the Inventory > Common forms menu. This form shows
all orders that have a mode of delivery in either the Sales order header or Detail lines that was set
up with a Pickup service type. You can also select the All service types check box to display all
orders.
Figure 19: Sales pickup form

The Sales pickup form provides basic information about the sales order. The counter person can
generate a packing slip and create invoices from this form in the same way that you can by posting a
sales order. Additional buttons are provided so that the counter person can quickly refresh the list to
show only the orders that have not been invoiced.
21
The Credit card tab allows the counter person to select a credit card for a customer when the
customer arrives. The credit card cannot be entered in this formit must already exist on the
customers account. When the invoice process is initiated, the credit card is captured, and if the card is
accepted, the invoice process is completed. If the card is declined, the process is stopped and a dialog
box is displayed with the decline information.
Figure 20: Sales pickup form credit card tab
22
Warehouse shipment
A button has been added to the Shipment form for credit card processing. The Process shipment
button is active when a credit card has been used for an order. Customers using a credit card payment
type often want an invoice included in the shipping package. The Process shipment button initiates
the invoice posting process, prints the invoice, and validates that the invoice can be posted. If a credit
card is involved, the credit card is processed. However, the invoice process will be stopped if the credit
card is not accepted.
Figure 21: Shipment form
Creating a payment journal

After a credit card is processed, a payment journal is created by using the payment journal that is
specified in the Payment services form. The credit card amount is settled against the invoice and the
transaction is posted to the payment journal.
Partial shipments
When a partial shipment is invoiced, the entire authorization is canceled and the credit card is
processed for only the amount of the partial invoice. Another authorization is then requested for the
amount remaining on the sales order. This cycle continues until the entire order has been invoiced.
Batch processing
Invoices that include credit cards can be posted using a batch. The batch log will include the same
information about the success or failure of the credit card that is shown in the Infolog message in
Figure 16.
Merging sales orders

During posting, you can merge sales orders into a single invoice based on the invoice account in those
orders. The standard behavior for this process is that the payment terms in the first order for an
invoice account are applied to all orders. That behavior is used for credit cards, as well.
23
If the first order has a credit card on it, all the merged orders for the invoice account will be
consolidated into a single invoice and the entire amount will be charged. The authorization for the first
order will be used to process the card, and all authorizations for the remaining merged sales orders
will be voided. If the first order for the invoice account does not have a credit card on it but the
remaining merged orders do have a credit card, then the credit cards on those orders will not be used
and all authorizations will be voided.
Refunds
You can process refunds using the credit note functionality in Microsoft Dynamics AX. When you create
a credit note for a sales order that contains a credit card, the credit note is created and the credit card
information is obtained from the original sales order. Microsoft Dynamics AX recognizes that the credit
note is a refund and it processes the credit card transaction as a refund. You cannot process a credit
note as a refund unless the credit note is generated from an existing sales order.
Voiding an authorization
After you have authorized an amount, you may want to void that authorization. For example, a
customer may want to cancel the order. In addition, customers may change their mind and decide to
use another payment method.
You can void an authorization by changing the payment term. When you change the payment term,
the dialog box shown in Figure 22 appears. Click OK to void the authorization. You must always
perform this step before deleting a sales order, as well.
Figure 22: Voiding authorizations
24
Credit card issues

Not all credit cards are approved the first time that they are processed. Orders that have issues with
their corresponding credit cards are displayed in the Credit card issues form (Accounts receivable
> Inquiries). The form contains only orders that have been declined at least once and were not
approved in a later attempt to process them.
Figure 23: Credit card issues form
Intercompany processing
Credit cards can be used in intercompany orders. When intercompany orders are automatically
invoiced, a credit card is captured during the invoice process. If the credit card is declined, the entire
intercompany invoice posting is stopped, just as if there were a posting failure. The order must be
invoiced again after the credit card issue is solved.
25
Technical Information
The credit card processing feature is a framework for credit card processing. In this section, we
provide more details about the development approach and issues for the feature.
Payment services provider records are created when you open the Payment services provider form
for the first time. The settings for which providers are active and the settings for payment journals are
stored in the CreditCardProcessors table.
Each payment services provider has unique requirements for how you must connect to it and process
credit card transactions. Due to these requirements, the settings for each processor are stored in
separate tables.
Payment Services for Microsoft Dynamics ERP (PSMDE)

PSMDE communicates with Microsoft Dynamics AX using the following DLLs that are installed during
setup the setup process:
Microsoft.DynamicsOnline.DOClientProxy.dll
Microsoft.DynamicsOnline.DOClientProxy.PaymentService.dll
Microsoft.DynamicsOnline.DOClientProxy.UserManagement.dll
The URLs that Microsoft Dynamics AX uses to communicate with the PSMDE web service and PSMDE
web pages for signup and account management are stored in the CreditCardMicrosoftSetup table.
Security
Two tables for the credit card processing feature contain sensitive information. These tables use the
table permissions framework (TPF) to limit access, however, we recommend additional security.
The CreditCardProcessorsSecurity table stores access keys for payment processors.

Note: PSMDE no longer requires this table in Microsoft Dynamics AX 2012.
The CreditCardCustNumber table stores the credit card numbers that were entered through the
credit card wizard.
Although the AOS and the SYSADMIN user are the only users that can access the Microsoft Dynamics
AX database when it is installed, we recommend that you use the Microsoft SQL Server transparent
database encryption feature to further restrict access to the two tables. Specifics about how to protect
SQL Server are described in the Microsoft Dynamics AX Security Hardening Guide.
To reduce the possibility of obtaining credit card numbers on the network, all Microsoft Dynamics AX
code that processes the full credit card number is run on the AOS.
Error Messages
Several types of error messages can occur.
Error messages returned by the payment services provider, such as Decline or Invalid login, are
displayed in an Infolog message and included in the Credit card transaction history form.
If there are network issues or more serious failures that are not returned by the payment services
provider, Microsoft Dynamics AX 2012 will attempt to determine the most probable cause and display
that error. Additional error information will be included in the Credit card transaction history form.
Transition from Authorize.Net to Payment Services for Microsoft

Dynamics ERP
Authorize.Net was deprecated in Microsoft Dynamics AX 2012. Before you upgrade from Microsoft
Dynamics AX 2009 to Microsoft Dynamics AX 2012, you should transition from using Authorize.Net to
using Payment Services for Microsoft Dynamics ERP.
26
To allow you to process your existing Authorize.Net transactions while transitioning to Payment
Services for Microsoft Dynamics ERP, first install Hotfix rollup 5 (KB 982812) and then hotfixes
KB979304_SYP and KB979304_HFX for Microsoft Dynamics AX 2009.ERP.
Transition from using Authorize.Net to Payment Services for Microsoft Dynamics

ERP in Microsoft Dynamics AX 2009
1. Set up Payment Services in Microsoft Dynamics AX 2009 by installing Hotfix rollup 5 (KB 982812)
and then hotfixes KB979304_SYP and KB979304_HFX. Search CustomerSource to find the
hotfixes. For more information, see Applying hotfixes (AX 2009).
2. Sign up for Payment Services for Microsoft Dynamics ERP.
3. Enable the payment service account.
4. Select Payment Services for Microsoft Dynamics ERP as your default provider.
All new sales order transactions are processed using Payment Services for Microsoft Dynamics ERP.
The hotfix enables Microsoft Dynamics AX 2009 to recognize existing Authorize.Net transactions and
to process them using the original Authorize.Net account. This enables you to process all older sales
order transactions that have already been authorized with Authorize.Net while having only Payment
Services enabled as a provider.
27
Appendix A
Information provided in Level 2 data support
information
Microsoft Dynamics AX 2012 information
Order Date
Purchase order date
Order Number
Purchase order number
Invoice Date
Invoice date
Invoice Number
Invoice number
Order description
Customer reference
Summary Commodity Code
Not provided
Merchant Contact
Contact
Merchant Tax ID
Company tax registration number
Merchant Type
Not provided
Purchaser ID
Customer number
Purchaser Tax ID
Customer tax registration number
Ship to City
Ship to city
Ship to County
Ship to county
Ship to State/Province Code
Ship to state/province code
Ship to Postal Code
Ship to postal code
Ship to Country Code
Ship to country code
Ship from City
Ship from city
Ship from County
Ship from county
Ship from State/Province Code
Ship from state/province code
Ship from Postal/Zip Code
Ship from ZIP/postal Code
Ship from Country Code
Ship from country code
Discount Amount
Total discount for the order
Handling charge
Handling charge
Duty Amount
Not provided
Freight Amount
Freight amount
Is Taxable
Yes, if taxes were calculated
Total Tax Amount
Total taxes for the invoice
Total Tax Rate
Average tax rate
Merchant Name
Name (company information)
Merchant Street
Company street
Merchant City
Company city
Merchant State
Company state
28
Merchant Country Code
Company country
Merchant County
Company county
Merchant Zip
Company postal code
Misc Charge Amount
Misc charge amount
Misc Charge Type
Misc charge type
Tax Rate
Average tax rate
Tax Amount
Amount calculated for the sales tax
Tax Description
Tax description
Tax Type Identifier
Alternate tax
Requester Name
Customer name
Total Amount
Total invoice
Purchase Card Type
U Unknown (default)
Amex Legacy Desc 1
Not provided
Amex Legacy Desc 2
Not provided
Amex Legacy Desc 3
Not provided
Amex Legacy Desc 4
Not provided
29
Information provided in Level 3 data support

information
Microsoft Dynamics AX 2012 information
Item Sequence #
Blank
Item Commodity Code
Commodity
Product Code
Item number
Product Name
Item description
Product SKU
Item number
Item Descriptor
Item description
Unit of Measure/Code
Unit
Unit Price
Unit price
Line Item Discount
Discount amount
Line Item Discount Rate
Not provided
Item Quantity
Quantity
Misc Charge Amount
Misc. charge amount
Misc Charge Type
Misc. charge type
Line Item Net Total
Net amount
Line Item Tax Amount
Total tax amounts on this line
Line Item Total Amount
Total amounts on this line
Line Item Tax Rate
Not provided
Cost Center
Dimension
Merchant Catalog Number
Item number
Merchant Tax ID
Company tax registration number
Tax Categories Applied
Not provided
Freight Amount
Freight amount
Handling Amount
Handling amount
Carrier Tracking Number
Tracking numbers
Pickup Address
Ship from street
Pickup City
Ship from city
Pickup State
Ship from state/province code
Pickup ZIP
Ship from ZIP/postal Code
Pickup Country
Ship from country code
Pickup County
Ship from county code
UNSPSC Code
Not provided
Pickup Datetime
Pickup date and time
Pickup record number
Not provided
30
Carrier Shipment number
Tracking number
Tax Rate
Tax rate used to calculate the tax
Tax Amount
Amount calculated for the sales tax
Tax Type Description
Description of the sales tax code
Tax Type Identifier
Alternate tax
31
Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your
people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar
Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a
way that helps you drive business success.
U.S. and Canada Toll Free 1-888-477-7989
Worldwide +1-701-281-6500
www.microsoft.com/dynamics
This document is provided as-is. Information and views expressed in this document, including URL and other
Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or
connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You
may copy and use this document for your internal, reference purposes. You may modify this document for your
internal, reference purposes.
2011 Microsoft Corporation. All rights reserved.
Microsoft, Microsoft Dynamics, and the Microsoft Dynamics logo are trademarks of the Microsoft group of
companies.
All other trademarks are property of their respective owners.
32

Credit Card Processing For Microsoft Dynamics AX 2012

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Credit Card Processing For Microsoft Dynamics AX 2012

Diunggah oleh

Hak Cipta:

Format Tersedia

Microsoft Dynamics AX 2012

Credit Card Processing

Date: November 2011

Send suggestions and comments about this document to

Technical Information ............................................................................... 26

Credit Card Processing Feature Concepts

Figure 1: Credit card processing feature concepts

Setting up Credit Card Processing

Description of the privilege

Authorize credit card information

Process a credit card in the sales order form

Maintain credit cards using a wizard

Create and modify a credit card

Maintain customer credit card

Delete a credit card

Maintain customer payment services

Modify the settings used to access the payment services provider

Set up credit cards

View credit card history information

View credit card transaction history

View credit card issues information

View open credit card issues

View customer credit card information

View customer credit card information

Figure 2: Payment services form

Payment Services for Microsoft Dynamics ERP

Card verification value

Figure 3: Card verification value form

Figure 4: Credit card types form

Figure 5: Terms of payment form

Figure 6: Terms of payment form and payment type

Figure 7: Terms of payment credit check settings

Figure 8: Setting up credit cards from the Customer form

Figure 9: Customer credit cards form

Figure 10: Credit Card Setup Wizard

Customer settings for address verification and card verification

Credit Card Parameters

Figure 12: Accounts receivable credit card parameters

Sales Order setup

Figure 13: Selecting a credit card on the sales order

Figure 15: Preauthorizing a sales order

Figure 16: Infolog showing the results of credit card processing

Figure 17: Credit card authorization history

Processing an authorization with card verification values enabled

Figure 18: Credit card history

Sales pickup (Will Call)

Figure 19: Sales pickup form

Figure 20: Sales pickup form credit card tab

Figure 21: Shipment form

Creating a payment journal

Merging sales orders

Figure 22: Voiding authorizations

Credit card issues

Figure 23: Credit card issues form

Payment Services for Microsoft Dynamics ERP (PSMDE)

The CreditCardProcessorsSecurity table stores access keys for payment processors.

Transition from Authorize.Net to Payment Services for Microsoft

Transition from using Authorize.Net to Payment Services for Microsoft Dynamics

Microsoft Dynamics AX 2012 information

Purchase order date

Purchase order number

Summary Commodity Code

Company tax registration number