Jump to content
shokinro

[Moduile] - Agile Authorize.NET credit card payment module for PrestaShop 1.7x/1.6x/1.5x

Recommended Posts

What is it?
It is a PrestaShop payment module for Authorize.NET. It accepts major credits payments.
It is a Express Checkout module that allows customer finish checkout with minimum information without going though 5 step registration process. It support one time payment, recurring payments for automatically reordering, it also supports installment payment that splits payment into multiple time pay.

Compatible version
PrestaShop 1.7x (For lower version please contact us support@addons-modules.com)

Features
* Accepts all major credit cards (Master, Visa, American Express, Discover) through Authorize.NET payment gateway.
* It works in all checkout mode of PrestaShop
- Guest checkout mode
- Registered user checkout mode
- One Page checkout mode
- Normal checkout (5 steps)

* Support recurring payment subscription and reordering subscription.
- Automatically update the recurring subscription status and order status
- The module takes of reordering when recurring payment is received.
- Customer will receive order confirmation and payment received email as usual for recurring payment

* Support instalment payment that allow customer pay one order in multiple instalments.
- Customer will receive email alert for approved or failed payment
- Automatically change order status if the subsequent payment approved or failed


* Support one time payment (Normal one time payment), real time payment.
* Admin is able to see the payment history and related of recurring payments/orders at order details page.
* No SSL/HTTPS is required, but the payment is executed with secured server communication.

* Cancellation of recurring payment subscription [new from ver1.1 2011.08.06]

Configurable features
* Configurable to enable or disable recurring payment, instalment payment
* Configurable to hide carrier/shipping methods if there is only one carrier, or no carrier required.
* Configurable to hide country if your store serves only one country
 

Integration with Agile Multiple Seller module
 

- Show order amount and order reference # at order confirmation page
-  Agile Multiple Seller Environment integration
A. Support parallel payment mode, buyer pay multiple sellers together in one time even buyer has products from multiple sellers, the payment will be automatically split into multiple sellers and store account(for seller commission)
B. Support all payment collection mode of agile multiple seller module - "Store collects payment", "Seller collects payments", "Both store and seller collect payments".
C. Recurring payment is not supported for multiple seller environment(because it is too complicated when with different payment collection mode)


About Payment Collection Mode of Agile Multiple Seller
- Store(main store) collects payment mode
At this payment collect mode, customer payment will go to main stores account, so main store will have to pay sellers for their sales(deducting commission) later manually.

- Sellers Collect payment mode(split payment)
At this payment collection mode, customer payments will be split into sellers account directly. But seller will have to pay store for seller commissions later by other way. 

- Both Store and Sellers collects payment (Split payment)
At this payment collection mode, customer payment will split into store and sellers account directly. It is easiest way for store to save management effort.

Note:
It is configurable for maximum recipients in one checkout(shopping cart) , default is 5 recipients. It will be depends on your server performance.

See details about Agile Multuiple Seller module - A best marketplace module for PrestaShop based marketplace solutions

 

Note:
- It is configurable for maximum recipients in one checkout(shopping cart) , default is 5 recipients. It will be depends on your server performance.
- In agile multiple seller environment, the recurring payment feature will be disabled

 

Screenshot
1. Order status screen (Waiting for authorization to Payment Accepted)
1. Recurring-reordering/Instalment payment history at product detailed page
1. Module configuration screen


Demo Site
Please request live demo access at our on-line store product page.

basic info of demo
http://agileservex.com/DemoFAQ-aa.txt

Test Credit Card: 4111111111111111 expiry: 2028 code: 223
Contact us for admin account

Note:
For recurring payment/install payment test, the order status will be changed next day.
(this Authorize.NET process rule)


Where to buy
=========
Http://addons-modules.com/'>Http://addons-modules.com/



Release Note

 

Version 2.7.0.4 - 2017.11.25
Fix - under HTTPS environment, the processing image was URL was not in HTTPS so it causes page warning on Firefox.

Version 2.7.0.3 - 2017.01.30
Fix - even set module to production mode, it still show testing mode and testing credcit numbers.

Version 2.7.0.2 - 2017.01.02
Improvement - Show Amount to pay on payment page when credit card info page 
Change - use $params['order'] instead of $params['objOrder'] on order confirmation page
Adjustment to support Agile Kernel 1.7.1.0 with common Google API keys and Agile Modal window for alert messages

Version 2.7.0.1 - 2016.12.16
Compatible with PrestaShop 1.7x
Feature - When at testing mode, showing testing credit card number for easy testing. 
Fix - Seller payment info error at Store Collects Payment mode
Fix - Payment amount warning because of duplicated paid invoice created at very special scenario: Both store and seller collect payment mode and store owner does not have products in shopping cart.

 

Version 1.3.0.1 - 2015.08.25

- Show order amount and order reference # at order confirmation page

-  Agile Multiple Seller Environment integration
A. Support parallel payment mode, buyer pay multiple sellers together in one time even buyer has products from multiple sellers, the payment will be automatically split into multiple sellers and store account(for seller commission)
B. Support all payment collection mode of agile multiple seller module - "Store collects payment", "Seller collects payments", "Both store and seller collect payments".
C. Recurring payment is not supported for multiple seller environment(because it is too complicated when with different payment collection mode)
 
Version 1.2.5.1 - 2014.06.22
- Supports PrestaShop 1.6x
- Supports responsive design/support mobile devices
- Fix an issue - when billing address is different from shipping address, card payment is declined. 
 
Version 1.2.2 - 2013.04.07
- Adjusted the module to use PrestaShop 1.5x standard for front pages
 
 
Version 1.2.1 - 2013.02.28
- fixed a bug at instalment payment - the amount is incorrect
- fixed a small bug at fancy box related script/css URL at PrestaShop 1.5x 
 
 
Version 1.2.0  - 2012.11.09
- removed express checkout mode.
- compatible with PrestaShop 1.5x
 
 
Version 1.1  - 2011.08.06
* Subscription cancellation function is added.
  - User can cancel recurring payment subscription user Order History page
  - This function is only available for orders with recurring payment subscription and not finish all payment yet.
* at One Page Checkout page, changed to show as normal checkout module UI in stead of Express Checkout UI 
* some other bug fixes and improvements.
 
Version 1.0  - 2011.06.05
* Accepts all major credit cards (Master, Visa, American Express, Discover) through Authorize.NET payment gateway.
* It is a Express Checkout module so customer can finish checkout process in few seconds.
* Does not require customer to log in or sign up an account for checkout. The module will take care of registration.
* It works in all checkout mode of PrestaShop
 - Guest checkout mode 
 - Registered user checkout mode
 - Express checkout(this is only available in old version for PrestaShop 1.5x)
 - One Page checkout mode
 - Normal checkout (5 steps)
* Support recurring payment subscription and reordering subscription. 
 - Automatically update the recurring subscription status and order status
 - The module takes of reordering when recurring payment is received.
 - Customer will receive order confirmation and payment received email as usual for recurring payment
* Support instalment payment that allow customer pay one order in multiple instalments.
 - Customer will receive email alert for approved or failed payment
 - Automatically change order status if the subsequent payment approved or failed 
* Support one time payment (Normal one time payment), real time payment.
* Admin is able to see the payment history and related of recurring payments/orders at order details page.
* No SSL/HTTPS is required, but the payment is executed with secured server communication.
* Customer is able to choose shipping method/carrier at Express Checkout screen
* Configurable to enable or disable recurring payment, instalment payment
* Configurable to hide carrier/shipping methods if there is only one carrier, or no carrier required.
* Configurable to hide country if your store serves only one country

46698_lyUCTjKyhm8M5zm0pgaC_t

46699_tXpigjyb9OTen6XAbENW_t

46700_FryidLawXz2uwCVwXk8m_t

46701_TKGkOPfcdbWoaXWnxPf9_t

46702_Sgqv5LAxRjKhDdNAgECv_t

Edited by shokinro

Share this post


Link to post
Share on other sites

Here is some more information on how order is created and order status is changed

How payment and order works
====================
1. One time payment - Real time authorization and approval. via Authorize.NET AIM(Advanced Integrated Method)

Submit order
"Approved": Order created with status set as Payment Accepted
"Failed" or "Error", Error will be displayed no error will be created

2. Installment payment - Subscribe
Each payment, is 1/X of order amount, where X is number of installments.

* Submit order with installment payment subscription
Success : Order created with status Waiting Authorization by Authorize.NET
Failed or Error: Error will be displayed, no order will be created

* Next day receive silent post form Authorize.NET
Approved: Order status set to Payment Accepted
Error/Failed: Order status set to Payment Error

*Subsequent payment transaction informaiton received from Authorize.NET
Approved: Order status will be changed or upated to "Payment Accepted"
Failed/Error: Order will be set as "Payment Error"


3. Recurring/reordering payment - subscribe via ARA (Authorize.NET recurring billing)
Each time, the same order amount is received

*Submit order with recurring payment subscription
Success : Order created with status Waiting Authorization by Authorize.NET
Failed or Error: Error will be displayed, no order will be created

*Next day receive silent post form Authorize.NET
Approved: Order status set to Payment Accepted
Error/Failed: Order status set to Payment Error

*Subsequent payment transaction informaiton received from Authorize.NET
Approved: A new order will be created - customer will receive new order confirmation email
Failed/Error: No recorring order will be created

Share this post


Link to post
Share on other sites

is your module updated to fit mastercard and visa's new requirements? http://www.authorize.net/support/pafaqs/

MasterCard and Discover are requiring that merchants support the following three transaction types for debit, prepaid and gift cards:

Partial Approval (or Partial Authorization) — Merchants are required to partially approve a transaction if a cardholder does not have enough balance on their debit, prepaid or gift card. In addition, the merchant must allow cardholders to pay the remaining balance owed with another form of payment. This is called a split-tender purchase transaction.

Benefit: Prior to implementing partial approvals, a debit, prepaid or gift card with an insufficient balance would be declined. By supporting partial approvals, the merchant can turn a potential decline or negative cardholder experience into a completed sale by asking for an additional form(s) of payment to cover a purchase.

Authorization Reversal — Merchants are required to reverse an authorized transaction if a cardholder decides they do not want to proceed with the transaction and the transaction has not yet settled. Authorization reversals will free up the available balance on a customer's debit, prepaid or gift card when transactions are not completed.

Benefit: By supporting authorization reversals, the merchant restores the cardholders' available balance, which enables them to potentially make a purchase (within their debit, prepaid or gift card's balance) at your store.

This requirement is important when processing partial authorizations, because merchants will probably run into a scenario where a card is partially authorized for an amount, but the customer decides to cancel the transaction instead of completing the sale. If the authorization reversal wasn't required, the customer's available balance would be reduced until that authorization naturally expired.

Balance Response — Merchants are required to print the prepaid card balance on the customer receipt or display it on a customer-facing terminal/POS device/Web page, or both. Prepaid card balance information is made available by the prepaid issuer only for some, but not all, prepaid cards, and support of this requirement is limited to those particular cards.

Benefit: By supporting balance responses and making the information available to the consumer, the consumer is better informed regarding their available balance on their prepaid cards, and could make additional purchases based on that balance.

Share this post


Link to post
Share on other sites

@tekneto
thanks for your inquiry.
No all of them are implemented, I will look into the detailed information and API changes to manage to implement them. shotly.

For the payment reversal, it is under development and will be implemented soon. but only for the unsettled (like recurring payment) payment.

Share this post


Link to post
Share on other sites

They are giving us till June 30th of this month to be compliant. This could be an issue with your current customers if your module doesn't include this feature. I need to know if yours has this so my client can be compliant with the requirements. Please let me know

What are the new compliance requirements? And how will complying with the requirements benefit me (the merchant)?
UPDATE: E-commerce merchants are now only required to provide support for authorization reversals. Though no longer required, partial authorizations and balance responses are considered best practices, and Authorize.Net still highly recommends that e-commerce merchants provide support for all three requirements. Retail and mobile merchants must still support all three requirements.

Authorization Reversal — Merchants are required to reverse an authorized transaction if a cardholder decides they do not want to proceed with the transaction and the transaction has not yet settled. Authorization reversals will free up the available balance on a customer’s debit, prepaid or gift card when transactions are not completed.

Benefit: By supporting authorization reversals, the merchant restores the cardholders’ available balance, which enables them to potentially make a purchase (within their debit, prepaid or gift card’s balance) at your store.

Share this post


Link to post
Share on other sites

@tekneto,
Thanks for your requirement.
For normal (non-recurring) payment, my module only use "Authorization and Capture", so it is settled once it is approved. For those transactions, they not reversible. So there is no need to implement reversal.

For recurring payment, the cancellation features development just finished and currently under testing. It will be release soon. I will let you know when the test is finished.

Share this post


Link to post
Share on other sites

Thanks again for the information and inquiry.

The new API is for new feature of "Partial Payment", it is Optional, not Mandatory.

In order to use new feature of "Partial Payment", we can send "x_allow_partial_Auth=TRUE", but we can also decide not to op in by sending x_allow_partial_Auth=False. You can also set this at your Authorize.NET account.

In order to keep it simple, at this version, my module does not include the new feature of "Partial Payment". Will consider in future version.

I am currently testing the recurring payment cancellation. It will be finish soon.

Share this post


Link to post
Share on other sites

The Demo site was moved, here is the new URL of demo site.

http://agileservex.com/prestashop141/

 

If you need admin access, please PM me.

 

Because there is an issue to edit old existing thread posts, so I am not able to change original description before the issue of the forum is fixed. sorry for the inconvenience.

Share this post


Link to post
Share on other sites

In Prestashop, the Instant/Guest checkout, does not allow for a different Billing address. If the Delivery Address does not match the customer's credit card statement, Authorize.net will return a failed transaction. This is a major problem and creates a lot of cart abandonment. I'm looking for a module to solve this as Prestashop 1.4.4 did not address this issue.

 

Does this module allow for a different billing address to be sent to Authorize.net?

 

Thank You

Share this post


Link to post
Share on other sites

Does this module allow for a different billing address to be sent to Authorize.net?

Thanks for your inquiry and sorry for late response.

 

Yes, this module does not send billing address to Authorize.net, so there is no this kind of problem.

Share this post


Link to post
Share on other sites

A new version of Agile Authorize.NET 1.1 is just released.

with this version, you will be able cancel recurring payment subscription.

 

agile-authorizenet-express-checkout-10.jpg

 

 

Version 1.1 changes

* Subscription cancellation function is added.

- User can cancell recurring payemt subscription user Order History page

- This function is only available for orders with recurring payment subscription and not finish all payment yet.

* at One Page Checkout page, changed to show as normal checkout module UI in stead of Express Checkout UI

Share this post


Link to post
Share on other sites

A new version of the module is just released. Now it is compatible with PrestaShop 1.5x.

 

Ver 1.2.0 - 2012.11.09

- Module is adjusted to compatible with PrestaShop 1.5x

- Express Checkout mode is removed - it is not suitable for this module

Share this post


Link to post
Share on other sites

Hi Kinro,

 

I wanted to ask if your module is tested and works in the following scenarios:

1) Guest checkout at One Page Checkout > Enters delivery address > Enters credit card info and billing address different from delivery address

 

2) Registered customer with separate delivery and billing address (sending item as gift)

Share this post


Link to post
Share on other sites

@tinyhands

Thanks for your inquiry

Please note, this module does not support Express Checkout.

 

1) Guest checkout at One Page Checkout > Enters delivery address > Enters credit card info and billing address different from delivery address

Yes, it will support One page/Guest Checkout mode.

 

2) Registered customer with separate delivery and billing address (sending item as gift)

 

Both addressed should recorded in your store database by PrestaShop.

The module only process the payment.

Share this post


Link to post
Share on other sites

the modules is updated with following fixes

 

 

Ver 1.2.1 - 2013.02.28

- fixed a bug at insallment payment - the amount is incorrect

- fixed a small bug at fancybox related script/css URL at PrestaShop 1.5x

Edited by shokinro

Share this post


Link to post
Share on other sites

The module is updated and is ready for PrestaShop 1.6x, 

This is a credit card payment module supports one time payment and also supports repeating/recurring payment. please see our store for more details. 

 

 

Version 1.2.5.1 - 2014.06.22
- Supports PrestaShop 1.6x
- Supports responsive design/support mobile devices
- Fix an issue - when billing address is different from shipping address, card payment is declined. 

Share this post


Link to post
Share on other sites

According to the notes, this module is compatible with 1.5x but when I go to the store, it says to request for lower versions than 1.6.  Tried to send a request, and the email bounced back undeliverable that your mailbox is full.  Please advise asap in regard to compatibility.  We are wanting our shop up tonight.

 

Thanks.

Share this post


Link to post
Share on other sites

Thanks for your using our modules.

I just cleared our mailbox. it should be fine now. please try to resend your request.

sorry for the inconvenience.

Share this post


Link to post
Share on other sites

Just make some improvement on order confirmation page after finish payments. It now include following information displayed on the page

- order reference #

- order ID

- total amount paid

 

Also you can add any other information from Order object to this page via Samrty variable, for example order reference.

 

{$objOrder->reference}

Share this post


Link to post
Share on other sites

the module has updated again.

fixed an issue with subscription cancellation - the cancellation does not show up correctly at Order History page.

Share this post


Link to post
Share on other sites

I have a couple of question about recurring payment feature

 

1. Do I have to set up my authorize.net account for recurring payments for this module to work?
2. Is the credit card information for recurring payments stored on my store?

Share this post


Link to post
Share on other sites

thanks for your inquiry

 

1. Do I have to set up my authorize.net account for recurring payments for this module to work?
 

Yes,  you will need to set up your Authorize.NET account to enable recurring payment functions

 


2. Is the credit card information for recurring payments stored on my store?
 

No, we do not record credit card information in store database. 

It is for customer security reason.

 

Share this post


Link to post
Share on other sites

If an item is set to qty. 1 the first time it is ordered on a recurring payment setup, changing the qty. to 0, will recurring payments for that individual still continue going through if the qty. remains at zero (since new orders are created for each payment)?

Edited by mathe

Share this post


Link to post
Share on other sites

The recurring payment will do exactly the same order.  

 

Authorize.NET the process the same payment when the pre-set comes for next payment.

The store(our module) will receive a payment notification from Authorize.NET and the module will create the same order based on previous order(recorded in database).

Share this post


Link to post
Share on other sites

sorry for delay, it seems that I missed your message.

 

yes we have separated version of the module that works for PrestaShop 1.5x.

If you have to use the module under PrestaShop 1.5x, please contact us to exchange the module for Prestaashop 1.5x.

Please send following info to support@addons-modules.com

- your order #

- your store URL

- the version of your Prestashop 

Share this post


Link to post
Share on other sites

Announcement - Agile Multiple Seller integration

This module has been implemented to integrate with Agile Multiple Seller module. 

- It supports all Payment Collection Mode of Agile Multiple Seller

  1. Store Collects Payments
  2. Sellers Collect Payment - Buyer's payment will be automatically split into each seller's account
  3. Both Store and Seller Collect payment - Buyer's payment  will be automatically split into Store(seller commission) and sellers' account(seller sales deducting seller commission).

- Buyer only need enter one time of credit card related information and there will be multiple payment records created when buyer confirm and submit the payment. Once payment for each recipient (seller or store).

- Note: Recurring payment is not available for Agile Multiple Seller environment

Share this post


Link to post
Share on other sites

Module updated and now integrated with Agile Multiple Seller module A. Support parallel payment mode, buyer pay multiple sellers together in one time even buyer has products from multiple sellers, the payment will be automatically split into multiple sellers and store account(for seller commission)

B. Support all payment collection mode of agile multiple seller module - "Store collects payment", "Seller collects payments", "Both store and seller collect payments".
C. Recurring payment is not supported for multiple seller environment(because it is too complicated when with different payment collection mode)

About Paymen Collection Mode of Agile Multiple Seller

- Store(main store) collects payment mode

At this payment collect mode, customer payment will go to main stores account, so main store will have to pay sellers for their sales(deducting commission) later manually.

 

- Sellers Collect payment mode(split payment)

At this payment collection mode, customer payments will be split into sellers account directly. But seller will have to pay store for seller commissions later by other way. 

 

- Both Store and Sellers collects payment (Split payment)

At this payment collection mode, customer payment will split into store and sellers account directly. It is easiest way for store to save management effort.

 

Note:

It is configurable for maximum recipients in one checkout(shopping cart) , default is 5 recipients. It will be depends on your server performance.

 

See details about Agile Multuiple Seller module - A best marketplace module for PrestaShop based marketplace solutions

 

Note:

- It is configurable for maximum recipients in one checkout(shopping cart) , default is 5 recipients. It will be depends on your server performance.

- In agile multiple seller environment, the recurring payment feature will be disabled

Share this post


Link to post
Share on other sites

The module has been updated to be compatible with PrestaShop 1.7x

It also include following 2 fixes

 

Version 2.7.0.1 - 2016.12.16

Compatible with PrestaShop 1.7x
Fix - Seller payment info error at Store Collects Payment mode
Fix - Payment amount warning because of duplicated paid invoice created at very special scenario: Both store and seller collect payment mode and store owner does not have products in shopping cart.

Share this post


Link to post
Share on other sites

Module Update Announcement:

 

Version 2.7.0.3 - 2017.01.30
Fix - even set module to production mode, it still shows testing mode and testing credit numbers.

Share this post


Link to post
Share on other sites

Found a small issue under HTTPS  environment and fixed as following:

 

Fix - under HTTPS environment, the processing image was URL was not in HTTPS so it causes page warning on Firefox.
 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×