Plastic 2

From 360Works Product Documentation Wiki
(Difference between revisions)
Jump to: navigation, search
Line 2: Line 2:
 
|type=style
 
|type=style
 
|image=[[file:Ambox_important.png]]
 
|image=[[file:Ambox_important.png]]
|text= '''New to FileMaker Plug-ins? Not sure how to install?''' <br>If you are new to using plug-ins or calling functions, 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.
+
|text= '''New to FileMaker Plug-ins? Not sure how to install?''' <br>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.
 
}}
 
}}
  

Revision as of 19:09, 22 April 2015


Contents

Plastic 2 Overview

Welcome to Plastic 2! Plastic 2 is a paid upgrade from Plastic 1, 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.

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:

oap_sign_up.gif

Plastic 2 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
InternetSecure Merchant Account Merchant eSolutions Profile ID Profile Key
Merchant Warrior Merchant UUID API Key Moneris Store ID API Token
PayTrace User name Password Paypal Payflow Pro Merchant Login Password
RealEx Merchant ID Account name TransFirst Merchant ID Hosted Key
USA ePAY Source Key PIN VirtualMerchant Merchant ID PIN

Documentation

Click one of the links below to view payment gateway-specific documentation:

Authorize.Net First Data InternetSecure Merchant eSolutions
Merchant Warrior Moneris PayTrace Paypal Payflow Pro
RealEx TransFirst USA ePAY VirtualMerchant

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!

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox