Set up recurring billing to automatically charge customers on a schedule. Save the payment information straight to the gateway, along with a specified time period and frequency.
The Plastic plugin allows you to easily process secure credit card payments and recurring billing from FileMaker.
Profile-based payments, also known as tokenization, save payment and customer information with the merchant provider instead of in your database.
Take an electronic check with Automated Clearing House (ACH) payments. This payment method will process a direct debit sale, void, or refund straight to a bank account.
If you have a preferred provider, run transactions with Plastic and one of our gateways. Review the chart below for a list of our supported gateways.
Process Payments in FileMaker
The Plastic plug-in makes it easy to process secure, SSL-encrypted credit card payments from FileMaker Pro, FileMaker Server, and FileMaker Web Publishing.
Run Charges from FileMaker with Ease
Plastic can run charges and transactions with credit-card swipers, card-not-present accounts, direct check debts, and much more. Plastic introduces profile-based payments, or tokenization, which save payment and customer data to the gateway. Running a charge with 360Works Plastic can be done in just one script step.
Supported Plastic Payment Gateways
|PayPal PayFlow Pro|
All of our plugins are designed to run on Mac and on Windows.
All system requirements are the same as those of FileMaker.
As long as you meet FileMaker's minimum requirements, you can run our plugins in your Mac or
What does the FileMaker community think?
We had a requirement to add credit card processing to a FileMaker database. Plastic was by far the easiest to implement.
— Larry Schultz, Mac Edge Corporation
I just finished my first attempt at using the plastic plugin from 360Works. To be honest I was pretty intimidated by credit card processing which is why I had not sold it before as an option to my customers. I was absolutely amazed at how painlessly the process was. I used the example file to get me off the ground and ended up with a very full featured solution.
— Mike Wallace, RCC Engineer
Love this product. Use it with several clients and has been very reliable. Thank you.
— Lee Strong, Strong Computer Support
360Works plugins are compatible with the FileMaker 16 platform and higher.
All of our plugins are designed to run on Mac and on Windows. All system requirements are the same as those of FileMaker. As long as you meet FileMaker's minimum requirements, you can run our plugins. Please reference the FileMaker operating system requirements for all versions.
Our plugins are supported in FileMaker Cloud 1.17 and 1.18, but FileMaker Cloud 2 does not support any plugins. You can still use the plugins in FileMaker Pro accessing a solution hosted on FileMaker Cloud 2, but server side scripts utilizing plugins will not work.
If you purchase the Enterprise License (see below), then you will be able to use the plugin with the FileMaker Web Publishing Engine. This means that when you use our plugins in your FileMaker scripts, they will work the same way with Instant Web Publishing (IWP) or WebDirect. It also means that your Custom Web Publishing applications (with XSLT, PHP, or any other web technology) can call FileMaker scripts that use our plugins.
Yes, all of our plugins work in FileMaker runtime solutions, just copy the plugin to the runtime's Extensions folder.
Most of our plugins are available in 3 licenses: a demo version which works for 2 hours every time you launch FileMaker, a Workgroup license for 10 or fewer users, and an Enterprise license for unlimited users within a single organization.
If you'd like to add plugin functionality to a mobile solution, there are a number of options available. Plugins cannot be installed directly on a iPhone or iPad, but you can trigger a script on a machine that does have the plug-in installed. Using FileMaker Server, you can have routine scripts that will process all the outstanding function calls. For an example on how to do this, see this article on accomplishing this with Plastic. Alternatively you could integrate RemoteScripter to trigger server side scripts.