Plastic3
(Created page with "{{mbox |type=style |image=file:Ambox_important.png |text= '''New to FileMaker Plug-ins? Not sure how to install?''' <br>If you are new to using/installing/managing plug-in...") |
(→Error Handling) |
||
| (14 intermediate revisions by 3 users not shown) | |||
| Line 7: | Line 7: | ||
| − | ==Plastic | + | ==Plastic 3 Overview== |
| − | Welcome to [http://360works.com/credit-card-plugin/ Plastic | + | Welcome to [http://360works.com/credit-card-plugin/ Plastic 3]! Plastic 3 is a paid upgrade from Plastic 2, and includes many new features for total flexibility over how and when charges are made within FileMaker. |
Plastic enables FileMaker Pro to act as a payment portal, which sends and receives SSL-encrypted credit card transaction information to and from a payment gateway. The payment gateway ensures the transaction information passes securely from the customer to the gateway, from the gateway to the eventual payment processor and vice versa. | Plastic enables FileMaker Pro to act as a payment portal, which sends and receives SSL-encrypted credit card transaction information to and from a payment gateway. The payment gateway ensures the transaction information passes securely from the customer to the gateway, from the gateway to the eventual payment processor and vice versa. | ||
Plastic can run a charge, authorize, capture, void, or refund transactions for a number of gateways. '''Based on the gateway selected, functions may require different parameters or not take certain parameters at all'''. Please note that this documentation details how to use the functions based on the gateway selected, so it is very important you select the correct gateway or provider. | Plastic can run a charge, authorize, capture, void, or refund transactions for a number of gateways. '''Based on the gateway selected, functions may require different parameters or not take certain parameters at all'''. Please note that this documentation details how to use the functions based on the gateway selected, so it is very important you select the correct gateway or provider. | ||
| + | |||
| + | ==New in Plastic 3== | ||
| + | |||
| + | *No longer requires user to install Java | ||
| + | *Can use plugin functions as script steps with a user-friendly GUI for specifying parameters | ||
| + | *Better error reporting in scripts | ||
| + | *Compatible with FileMaker Cloud | ||
| + | *Better compatibility with FileMaker Server for Perform Script on Server and scheduled scripts | ||
| + | *Each plugin runs in a separate process, increasing reliability and stability | ||
| + | *Plugins can be reliably unloaded, making it possible to auto-update without restarting FileMaker | ||
| + | *Where appropriate, plugin parameters can be selected from pull-down lists and checkboxes | ||
| + | *Support for streaming large container data, allowing unlimited amounts of data to be transferred between FileMaker and the plugin without running out of memory. | ||
| + | *Compatible with the older plugin API, so you can continue to use your existing scripts and calculations with the new plugins. | ||
==Installation== | ==Installation== | ||
| − | [[ | + | For a guide on how to install Plastic please see our [[Plug-In Installation|plugin installation]] page |
==Don't have a merchant account?== | ==Don't have a merchant account?== | ||
| Line 24: | Line 37: | ||
<center>[https://ems.authorize.net/oap/home.aspx?SalesRepID=98&ResellerID=11334 http://www.authorize.net/images/reseller/oap_sign_up.gif]</center> | <center>[https://ems.authorize.net/oap/home.aspx?SalesRepID=98&ResellerID=11334 http://www.authorize.net/images/reseller/oap_sign_up.gif]</center> | ||
| − | ==Plastic | + | ==Plastic 3 Authorization Basics== |
Before you begin using Plastic, you'll need to know your gateway specific log-in credentials. In the function signature template, we refer to these as merchant account names and transaction keys. The chart below illustrates which credential to use in place of merchantAccountName and txKey. Please note that there may be additional security features per gateway. For example, VirtualMerchant also requires a user, Merchant Warrior requires a API Passphrase, and RealEx requires a shared secret. | Before you begin using Plastic, you'll need to know your gateway specific log-in credentials. In the function signature template, we refer to these as merchant account names and transaction keys. The chart below illustrates which credential to use in place of merchantAccountName and txKey. Please note that there may be additional security features per gateway. For example, VirtualMerchant also requires a user, Merchant Warrior requires a API Passphrase, and RealEx requires a shared secret. | ||
| Line 33: | Line 46: | ||
|- | |- | ||
| ''Authorize.Net'' || Merchant API Login ID || Merchant Transaction Key | | ''Authorize.Net'' || Merchant API Login ID || Merchant Transaction Key | ||
| − | | ''First Data'' || User ID || Password | + | | ''First Data'' || User ID || Password |
|- | |- | ||
| − | |||
| ''Merchant eSolutions'' || Profile ID || Profile Key | | ''Merchant eSolutions'' || Profile ID || Profile Key | ||
| + | | ''Merchant Warrior'' || Merchant UUID || API Key | ||
|- | |- | ||
| − | |||
| ''Moneris'' || Store ID || API Token | | ''Moneris'' || Store ID || API Token | ||
| − | |||
| ''PayTrace'' || User name || Password | | ''PayTrace'' || User name || Password | ||
| − | |||
|- | |- | ||
| − | |||
| ''TransFirst'' || Merchant ID || Hosted Key | | ''TransFirst'' || Merchant ID || Hosted Key | ||
| − | |||
| ''USA ePAY'' || Source Key || PIN | | ''USA ePAY'' || Source Key || PIN | ||
| + | |- | ||
| ''VirtualMerchant'' || Merchant ID || PIN | | ''VirtualMerchant'' || Merchant ID || PIN | ||
|} | |} | ||
| − | |||
==Error Handling== | ==Error Handling== | ||
| − | To suppress Plastic | + | To suppress Plastic 3 error dialogs, please use the <code>CCSetErrorCapture ( True )</code> code in your solution startup script. |
| + | |||
| + | For catching the last error use the calculation CCLastError, such as | ||
| + | Let(result = CCLastPaymentAuthCode ; If(result = "ERROR" ; CCLastError ; result)) | ||
For instructions on advanced error handling and custom error dialogs, see [[Plugins_101#Error_Handling.2FReporting|here]]. | For instructions on advanced error handling and custom error dialogs, see [[Plugins_101#Error_Handling.2FReporting|here]]. | ||
| Line 69: | Line 80: | ||
| style="border: 1px solid darkgray;" width="175"|[[FirstData|First Data]] | | style="border: 1px solid darkgray;" width="175"|[[FirstData|First Data]] | ||
| − | |||
| − | |||
| style="border: 1px solid darkgray;" width="175"|[[Merchant eSolutions]] | | style="border: 1px solid darkgray;" width="175"|[[Merchant eSolutions]] | ||
| Line 80: | Line 89: | ||
| style="border: 1px solid darkgray;" width="175"|[[Moneris]] | | style="border: 1px solid darkgray;" width="175"|[[Moneris]] | ||
| − | | style="border: 1px solid darkgray;" width="175"|[[PayTrace | + | | style="border: 1px solid darkgray;" width="175"|[[PayTrace|PayTrace]] |
| − | + | ||
| − | | | + | |
|- | |- | ||
| − | |||
| − | |||
| style="border: 1px solid darkgray;" width="175"|[[TransFirst]] | | style="border: 1px solid darkgray;" width="175"|[[TransFirst]] | ||
| Line 93: | Line 98: | ||
| style="border: 1px solid darkgray;" width="175"|[[VirtualMerchant]] | | style="border: 1px solid darkgray;" width="175"|[[VirtualMerchant]] | ||
| + | |||
| + | |- | ||
| + | |||
|} | |} | ||
| + | |||
| + | |||
</big> | </big> | ||
Latest revision as of 17:18, 12 February 2024
 | New to FileMaker Plug-ins? Not sure how to install? If you are new to using/installing/managing plug-ins, please read the Plugins 101 guide first before consulting this documentation. It explains how to call functions, set function parameters, install plug-ins, and handle errors. |
Contents |
[edit] Plastic 3 Overview
Welcome to Plastic 3! Plastic 3 is a paid upgrade from Plastic 2, and includes many new features for total flexibility over how and when charges are made within FileMaker.
Plastic enables FileMaker Pro to act as a payment portal, which sends and receives SSL-encrypted credit card transaction information to and from a payment gateway. The payment gateway ensures the transaction information passes securely from the customer to the gateway, from the gateway to the eventual payment processor and vice versa.
Plastic can run a charge, authorize, capture, void, or refund transactions for a number of gateways. Based on the gateway selected, functions may require different parameters or not take certain parameters at all. Please note that this documentation details how to use the functions based on the gateway selected, so it is very important you select the correct gateway or provider.
[edit] New in Plastic 3
- No longer requires user to install Java
- Can use plugin functions as script steps with a user-friendly GUI for specifying parameters
- Better error reporting in scripts
- Compatible with FileMaker Cloud
- Better compatibility with FileMaker Server for Perform Script on Server and scheduled scripts
- Each plugin runs in a separate process, increasing reliability and stability
- Plugins can be reliably unloaded, making it possible to auto-update without restarting FileMaker
- Where appropriate, plugin parameters can be selected from pull-down lists and checkboxes
- Support for streaming large container data, allowing unlimited amounts of data to be transferred between FileMaker and the plugin without running out of memory.
- Compatible with the older plugin API, so you can continue to use your existing scripts and calculations with the new plugins.
[edit] Installation
For a guide on how to install Plastic please see our plugin installation page
[edit] Don't have a merchant account?
If you do not already have a gateway or merchant account, you can sign up for an Authorize.Net account at the following:
[edit] Plastic 3 Authorization Basics
Before you begin using Plastic, you'll need to know your gateway specific log-in credentials. In the function signature template, we refer to these as merchant account names and transaction keys. The chart below illustrates which credential to use in place of merchantAccountName and txKey. Please note that there may be additional security features per gateway. For example, VirtualMerchant also requires a user, Merchant Warrior requires a API Passphrase, and RealEx requires a shared secret.
| Gateway | merchantAccountName | txKey | Gateway | merchantAccountName | txKey |
|---|---|---|---|---|---|
| Authorize.Net | Merchant API Login ID | Merchant Transaction Key | First Data | User ID | Password |
| Merchant eSolutions | Profile ID | Profile Key | Merchant Warrior | Merchant UUID | API Key |
| Moneris | Store ID | API Token | PayTrace | User name | Password |
| TransFirst | Merchant ID | Hosted Key | USA ePAY | Source Key | PIN |
| VirtualMerchant | Merchant ID | PIN |
[edit] Error Handling
To suppress Plastic 3 error dialogs, please use the CCSetErrorCapture ( True ) code in your solution startup script.
For catching the last error use the calculation CCLastError, such as Let(result = CCLastPaymentAuthCode ; If(result = "ERROR" ; CCLastError ; result))
For instructions on advanced error handling and custom error dialogs, see here.
[edit] Documentation
Click one of the links below to view payment gateway-specific documentation:
| Authorize.Net | First Data | Merchant eSolutions |
| Merchant Warrior | Moneris | PayTrace |
| TransFirst | USA ePAY | VirtualMerchant |
[edit] Contact Us
If you still need help, there are several resources available! FMForums hosts a support forum for 360Works products. Please look through the posts and see if your question has been posted before making a new topic.
Support is also available via email at plugins@360works.com. You can also call us at 770-234-9293. We offer many services in addition to our plug-ins, so let us know if you'd like a little help integrating the plug-in into your solution. Or if you'd be interested in a customized plug-in or development please let us know!
