Authorize.Net DPM payment gateway for the Responsive Storefront
Add the Authorize.Net payment processor to your Magelia WebStore responsive storefront using the Direct Post Method (DPM)
Main benefits :
- Safe and secure (benefits from Authorize.net PCI-DSS compliance)
- Authorize.net gateway accepts a variety of payment methods
- Automated update of the order status (based on the payment gateway response)
- SandBox / Test mode
What’s included ?
- a package (NuGet package) that, once installed, makes the Authorize.net payment gateway available to the Responsive Storefront
What’s required ?
- You must have subscribed to an Authorize.Net plan. The Authorize.net Plan and the additional costs are NOT included in this package. Please visit www.authorize.net for more info.
This package requires that your storefront be based on the responsive design template available here and that the checkout page has not been modified.
Add Authorize.Net payment gateway based on the DPM (Direct Payment mode):
- The Authorize.Net Payment Gateway handles all the steps of the secure transaction while remaining virtually transparent.
- Customer data is protected with 128-bit SSL encryption.
- Authorize.Net supports a variety of payments methods : Credit cards : Visa / MasterCard / American Express / Discover
- For maximum security, Credit Card Information are NOT stored in the Magelia WebStore Database. This also facilitates the PCI Compliance of your store.
When you install the Authorize.Net package:
1. The new payment mode is available on the checkout page :
2. Payment Information is not stored in Magelia WebStore but directly processed by Authorize.Net
3. The payment Gateway response updates the order status
Once the payment request has been submitted to Authorized.Net, the payment gateway will notify the response to the Responsive Store front (using Silent Post URL)
The order status will be automatically updated:
Response Code Description Payment status Order status in Magelia WebStore Admin console 1 This transaction has been approved. Authorization Request Approved Approved (Further Inquiry Required if response amount is different than order amount) 2 This transaction has been declined. Authorization Request Refused Rejected 3 or 4 There has been an error processing this transaction.
This transaction is being held for review.
Further Inquiry Required
Cancelation of the order: If a customer cancels the order from the Authorize.Net page, then the order status is updated to "Canceled".
4. The payment is associated and available in the order
In the administration console you will see the payment appear on the "Payments" tab as shown below:
You will also view additional information such as the transaction code, the authorization codes and additional data.
5. (optional) : define payment modes
In the above screen, you may have noticed that the payment mode mentioned is Authorize.Net DPM.
Here is how to display the payment method or card type used by the buyer:
Go to the Seller/Store > Seller > Payment mode screen and create payment modes that match the Authorize.Net payment modes that you accept on your website (such as CC / ECHECK / Visa / MasterCard / American Express / Discover / Diners Club / JCB).
If the value sent by Authorize.Net in the response match the Code of the payment Mode, then the payment mode will automatically appear in the Magelia WebStore administration console.
Example: create the "American Express" payment mode
Warning: the Code and not the name must exactly match Authorize.Net payment mode.
When a customer pays with an American Express card, the payment will display American Express as payment mode
Additional Information and known limitations
- The current implementation of the Authorize.Net payment gateway does not support recurring payments, multiple payments of a single orders. Supporting these payment modes may require to develop another Package or extend this package by specific developments.
- Multiple payment modes can be proposed in a Responsive StoreFront based on the Responsive design template. You may also propose additional payment gateways such as PayPal or additional Payment modes such as checks. Please view the others Payment gateways proposed by Magelia.
Installing packages for Magelia WebStore responsive Storefront is a two-step process.
- Configure Visual Studio to access your Magelia Private Repository
- View the packages you purchased or got for free
Please note that the configuration of your Magelia Private Repository has to be done only once. After you have configured it, all the packages that you add will be automatically available in your private repository.
1. Configure Visual Studio to access your Magelia Private Repository
If you have already configured your Magelia Private repository, skip this step and go directly to part 2.
We first need to get the URL of your private Magelia repository because we will need this URL to make the packages available in Visual Studio.
Now that we have retrieved this information, let us configure Visual Studio to access your packages.
In Visual Studio, go to the menu: Tools > NuGet Package Manager > Package Manager Settings :
In the menu on the right click on "Package Sources"
Then hit the « + » button on the upper right side to add a new package
Edit the name and enter "Magelia private repository"
Edit the source and Paste the URL of your Magelia repository (the one that was in your Magelia.org account)
2. View the packages you purchased or got for free
Once your private repository has been configured, simply click on “Update”. This will make the packages available in Visual Studio :
To view the available packages and install a package, right-click on your project or on the solution and select "Manage NuGet Packages" :
In the pop-up window select "Magelia private repository" on the left panel to view the packages that you obtained from the Magelia Gallery.
Click Install next to the package name to "Install a package"
You are all set!
What we have described here is the standard procedure to install a Magelia package.
In order to configure or adapt your package to your project requirements, please refer to the package page on Magelia.org.
The Authorize.Net package is based on the Direct Post Method and allows developers to fully customize the experience of the entire payment flow, while simplifying PCI compliance.
- Magelia WebStore (3.0+)
- A responsive storefront based on the Magelia Responsive design template (3.0+) available here
- The code of the checkout page must not have been deeply changed
- An Authorize.Net merchant and/or sandbox account is required for configuration and tests. Make sure your account is a "Card Not Present" (CNP) account. Click here to create an Authorize.Net account
1. Configure the Authorize.Net Settings
Make sure that your Authorize.Net account has been configured as explaced below:
Make sure to set an MD5-Hash. Set an MD5-Hash in the Authorize.Net merchant admin under Settings > Security Settings > General Security Settings > MD5-Hash. This can be any string you want.
Silent Post URL
This package uses Direct Post Method integration with Silent Post response for updating order statuses once the payment authorization has been submitted.
To enable this feature, you need to specify a Silent Post URL under Settings > Transaction Format Settings > Transaction Response Settings.
This URL format sould be like this : http://YourMageliaWebStorePublicUrl.com/en/Authorize/Notification
2. Add information in the web.config
Once the package has been installed from your Magelia private repository, simply add the following parameter keys to the <payments> section in the Web.config file of your Responsive Storefront:
- hash : Define here the hash value that you previously set in your Authorize.Net account. The MD5 Hash authenticates requests between your server and Authorize.Net (Menu Settings > Security Settings > General Security Settings)
- login : Merchant API Login ID provided by Authorize.Net (Settings > Security Settings > General Security Settings)
- key : Merchant Transaction Key provided by Authorize.Net (Settings > Security Settings > General Security Settings)
- test-gateway : Indicates if the payment gateway shoud be the test one or not.
- return-domain : Specify the domain that will be used to generate customers returning URL from Authorize.Net. It should be your public domain name.
Example of information added to the web.config file
<parameter key="test-gateway" value="true" />
<parameter key="hash" value="magelia" />
<parameter key="login" value="97uUxtVk68tn" />
<parameter key="key" value="32fHv43A9dYU2r7J" />
<parameter key="return-domain" value="http://YourMageliaWebStorePublicUrl.com" />
3. Test and check
Once you have properly deployed the package, configured the Authorize.Net settings and modified the web.config file, you should be able to see the Authorize.Net payment mode in the checkout page.
We suggest you to thoroughly test the website before you turn the payment to live mode.
Version 3.0 released May 2014
- Initial release