Assembly Payments for WooCommerce

Screenshots

Accept Credit Card and Bank Account payment on your WooCommerce store with Assembly Payments Accept payment made by credit cards, debit cards and through direct bank debit right at your store. Assembly Payment is a fin-tech payment company based in Australia. Since its establishment in 2013, it has enjoyed tremendous growth and has received $14 million USD in funding. With Assembly Payment solution for WooCommerce, you can securely receive payment from customers in Australia, New Zealand, and the US. Customers can easily checkout and complete their purchase without leaving your store, improving their shopping experience. Why use Assembly Payment for WooCommerce? Supports payment made by credit and debit cards issued by VISA, MasterCard and American Express (for US platforms only). Detect and prevent payment fraud with CVV/CVC verification. Let customers pay directly from your store with direct API. Support payment by payment cards and direct bank debit. Saved card detail for quick payment. By integrating Assembly Payment with Magento 2, you will be able to process payments with ease and convenience. Features & Benefits Seamless checkout experience By using Assembly API, merchants will be able to let customers check out right within the store. Customers will fill in the payment form on their browser. This information is then transferred back to merchant's server for processing before it is sent back to Assembly's server. PCI DSS Compliance guide With the direct API integration method, the scope of PCI DSS Compliance for customer is SAQ-D. Different payment methods Through the Direct Debit Authority API, merchants might allow customers to make payment by using bank account as a payment method. When customers agree to the direct debit agreement, the value of the order will be debited from customer's bank account. Convenience for checkout with Card storage When customers make payments, Assembly will use customer payment info to generate a token. This token will be used to get saved card details for customers. During the next purchases, customers will be able to choose from a list of their saved cards to purchase products and services and don't have to enter their card detail again. Secure payment with CVV/CVC test Customers need to insert their card verification number (CVV) to check the validity of their card and reject any failure. This protects merchant from fake cards and fraudsters. Credit card/Debit Card Payment Assembly allows customers to make payment with their credit and debit cards. Supported brands include Visa, MasterCard, and American Express. Support for different countries Assembly payment is currently supported in Australia, New Zealand and United States. Bank accounts opened in these countries will be able to use Assembly payment gateway. Supported for multiple currencies Assembly payment can process payments in AUD, NZD or USD. To use Assembly Payment gateway for WooCommerce, you need to register for an Assembly account here . Pricing for Assembly Payment starts at 2.9% plus 30c for credit card payments (1% for ACH Debit). For more pricing information, see here . A few notes about the sections above: “Contributors” is a comma separated list of wordpress.org usernames “Tags” is a comma separated list of tags that apply to the plugin “Requires at least” is the lowest version that the plugin will work on “Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on higher versions… this is just the highest one you’ve verified. Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for stable. Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag. If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where you put the stable version, in order to eliminate any doubt.