The Payment Service available from Online Services for Microsoft Dynamics ERP is an example of the growing availability of online services that users of ERP systems can benefit from connecting to. Adding functionality to the application through connecting to a service is new territory for us in the NAV development team, and we have learned a lot through this development project. We are looking forward to sharing the benefits of being able to expand the service, while we keep our focus on delivering the new NAV product.
The Payment Service is hosted by Microsoft and the number of available Payment Providers is growing. Today there are multiple Payment Providers like First Data, Pay Pal, and Cybersource supporting the US and Canadian markets. The plan is to grow the number of payment providers, so that the rest of the world can be supported as well. We are shipping the integration for all NAV supported countries - even though the payment providers aren't available yet - so the code is ready when the service becomes available.
The integration to the Payment Service that is included in NAV 2009 R2 will allow users of Microsoft Dynamics NAV to accept credit and debit card payments from Sales Orders, Invoices, as well as the Cash Receipt Journal. The solution will allow for both an authorization process and an automatic capture of the required amount during post as well as using it more freely on the Cash Receipt Journal.
Adding the integration to the online services has been done with a number of goals in mind:
The payment service is also certified by following the guidance of the Payment Card Industry (PCI) Security Standards Council.
The areas that are relevant when describing the integration to the Payment Service can be described by the following scenarios:
To describe the scenarios it is useful to think about the personas using the functionality; in this case we work with Susan, the Order Processor, as well as Arnie the Accounts Receivable Administrator.
As a part of Susan's work, she receives and processes the incoming orders from the sales representatives. She will in some cases talk to the customer to validate the orders and ensure that items are available and that the price is correct according to the agreement. In some cases the customer can request that they want to pay using a credit card, instead of having to handle the invoice later. Susan has to ensure that the information required for using a credit card is available; if not, she will get the information from the customer.
If Susan needs to be certain that the customer can pay the agreed amount, she can go ahead and authorize the amount against the provided credit card information. If the result is successful the sales order can be shipped. When the sales order is posted (or parts of it) the actual capture of the amount on the sales order will automatically be processed. When capture is successful the payment will be automatically registered and money will be received shortly.
On the sales order it looks like below - there are two new fields for the credit cards - as well as a requirement to use a specific Payment Method (described below in the Getting Started section).
The scenario above is the simplest process that is supported by the new payment service integration. The following scenarios is also covered in the implementation:
All of the above transactions and connection to the payment service can be seen on the specific customer as well as on the specific documents. On all places a Transaction Log has been implemented that shows the status of the current transactions and if the connections have been successful or not.
Enabling the payment integration does require a couple of steps both inside and outside NAV:
For more information please look at the following resources:
How can I set this up for Payment Services testing? Is there a standard credit card code such as the Visa account # 4111-1111-1111-1111 that I can use to test this feature? Also, since Payment Services will need to be set up to activate this feature can Partners sign up for testing purposes only?
Thank you for your question.
For testing the functionality you do need to sign up with the Dynamics online team – please refer to the help guidelines for doing this.
When the integration is set to run in test mode (Click the Run in Test mode as shown above) your transactions will not be sent to the payment provider, they will stay in the Dynamics Online environment and the responses will be simulated. In this mode, you can test using any of the 4 supported credit card types and then use any sample credit card numbers that are appropriate for those credit card types (e.g., AMEX cards always have 15 digits). The only rule is that the numbers needs to confine to the modal 10 validation of credit cards.
In case when you would like to test it end to end, you will have the option of testing against a sandbox environment for your payment provider if your payment provider offers such an environment and you have enrolled with their service. In that case, you will not click Run in Test mode and you will use the specific test credit cards that the payment provider offers for use in testing. You will also need to adhere to their guidelines for transaction limits (e.g., transactions less than $100 is a typical rule). Note that not all payment providers offer actual sandbox test environments; some providers effectively have you testing against production environments, but with test credit card numbers. For more information about these services, you will need to get in touch with the payment provider you are considering using and see what their offerings and test guidelines are.
Please reply back to this if there are more specific questions as to how to create a testing credit card number etc.
Hello Rikke Lassen,
Is it possible to register for more that one payment provider and bank account within a single NAV company.
If so can you please let us know how to specify which provider/bank account to use for a Sales Order Transaction.