Marketing 360® Payments for WooCommerce

Accept credit card payments on your WooCommerce store with the Marketing 360® Payments, including Apple Pay, Google Pay, and Microsoft Pay for mobile and desktop.

When customers make a payment on your website, a customer profile will automatically be created in the Payments app in Marketing 360 where you can track their purchases, add details to their profile and more. This gives you a powerful, singular view of your customers that you can use to maximize customer lifetime value and build strong relationships.

This is more than your standard payment gateway, though. Payments is just one of the great apps in Marketing 360. If you’re looking for a one-stop solution for business management and marketing tools like a CRM, email marketing, appointment scheduling and reporting tools to help you keep track of it all, look no further than Marketing 360.

About Marketing 360

Over 20,000 small businesses use Marketing 360 to manage and grow their business. Not only do you get the tools you need to scale, but you get the do-it-for-you marketing programs you need to grow — all in one platform. Click here to sign up today.

Plugin Support

View the Marketing 360 Knowledge Base to read our support articles or submit a ticket with our team.

Before You Get Started

To process transactions on WooCommerce with Marketing 360® Payments, you’ll need start with these things:

1. Secure Your Website with an SSL certificate.
2. Install WooCommerce on your site.
3. Create your Marketing 360 account.
4. Enable the Payments app in Marketing 360.

Installation

Installing the Marketing 360® Payments for Gravity Forms consists of two parts: installing the plugin and connecting it to your Marketing 360 account.

1. Installing The Marketing 360® Payments For WooCommerce Plugin
2. Configuring Marketing 360® Payments for WooCommerce

Once you’ve installed and configured the plugin, the next steps are to finish adding products to your store. When that’s complete, it’s a good idea to make a test purchase from your website to verify everything is working.

Need A Little Help?

If you ever run into issues or you have questions, let us know!
Submit an IT Ticket from the Knowledge Base.

1. 

   Connecting your website to your Marketing 360® account takes just seconds.

2. 

   Your customers get a sleek, simple way to enter their card details during checkout.

3. 

   Each customer that submits a payment will display in the Marketing 360® Payments app.

2.0

• Fixed account connection flow to correctly store Stripe credentials after linking a Marketing 360 account
• Fixed payment gateway not appearing on checkout after account is connected
• Fixed process_admin_options not firing to persist stripeKey and stripeAccountId after Save Changes
• Fixed get_stripe_details, set_account_details, and add_stripe_details_callback to correctly read and write account details
• Fixed webhook signature validation — conditional was inverted, allowing forged requests and rejecting legitimate ones; switched to hash_equals() to prevent timing attacks
• Fixed timestamp validation in webhook handler returning bare return instead of return false
• Fixed testmode property hardcoded to false instead of reading from plugin settings, which caused live charges to always be processed regardless of Test Mode setting
• Fixed debug query parameters (?showdetails, ?registerdomain, ?getresults) removed from gateway constructor — ?getresults exposed customer payment token records to unauthenticated requests
• Fixed level 3 data overwrite in request_with_level3_data() — $level3_data was immediately reset to an empty array, causing level 3 data to always be skipped
• Fixed Apple Pay domain registration — debug echo/print_r/die() block was preventing the function from ever completing and exposing authorization tokens
• Restored idempotency key logic in registerApplePaySubdomain()
• Restored seven settings validation methods that were commented out (M360 account, client ID, client secret, live publishable key, live secret key, test publishable key, test secret key)
• Removed hardcoded live credentials that were present in commented-out code

1.0.4

• Initial public release