Plastic

From 360Works Product Documentation Wiki
(Difference between revisions)
Jump to: navigation, search
(→‎"User authentication failed" error)
Line 1: Line 1:
−
==Troubleshooting==
+
{{mbox
−
===Payflow Pro (PayPal) Gateway===
+
|type=style
−
====Correct use of "partner" and "user" optional parameters====
+
|image=[[file:Ambox_important.png]]
−
Depending upon the setup of your merchant account in the [http://manager.paypal.com PayPal Manager], the <strong>partner</strong> and <strong>user</strong> optional parameters might be necessary in order to process a credit card transaction using the Plastic plugin.
+
|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.
 +
}}
  
−
<em>User</em>
 
−
* Required only if you have set up an additional user in PayPal Manager and you wish to perform transactions as that user.
 
  
−
<em>Partner</em>
 
−
* Contains either VeriSign, PayPal  or the name (ID) of the reseller/company from which you purchased the Payflow Pro service. Required only if your partner is anything other than PayPal.
 
  
−
===="Invalid vendor account" error====
+
==Plastic 4 Overview==
−
Usually caused when the partner is something other than PayPal and has been omitted or entered incorrectly.
+
  
−
===="User authentication failed" error====
+
Welcome to [http://360works.com/credit-card-plugin/ Plastic 4]! Plastic 4 is a paid upgrade from Plastic 3, and includes many new features for total flexibility over how and when charges are made within FileMaker.
−
Can be caused by a number of factors.
+
  
−
* <strong>Make sure that you are providing the proper login credentials.</strong>
+
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.
−
Example:
+
−
+
−
CCProcessPayment(
+
−
$merchantAccount ;
+
−
$transactionKey ;
+
−
"1.23" ;
+
−
"371449635398431" ;
+
−
"0809" ;
+
−
"authMode=AUTH_ONLY";
+
−
"partner=VeriSign"
+
−
)
+
  
−
:* In the above example, <strong>$merchantAccount</strong> would be the Merchant Login ID used to access PayPal Manager, <strong>$transactionKey</strong> would be the password used to access PayPal Manager and the optional parameter called <strong>partner</strong> is required because its value is not equal to "PayPal."
+
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.
  
−
* <strong>Determine whether the IP address of the machine you are using to process transactions has been added to the list of Allowed IP Addresses in PayPal Manager.</strong>
+
==New in Plastic 4==
−
** If you log into PayPal Manager, click the Service Settings tab and click the Allowed IP Addresses link, you will see a screen that allows you enter IP addresses from which transactions may originate. If all of the fields on this screen are empty, then there are no IP address restrictions for the account.
+
−
** Do not confuse the Allowed IP Addresses link under the Service Settings tab with a similar link under the Account Administration tab. The latter Allowed IP Addresses link will take you to a screen that allows you to restrict which IP addresses may log into PayPal Manager.
+
  
−
* <strong>Determine whether a separate transaction password has been configured in PayPal Manager.</strong>
+
* Now supports Ubuntu Linux 20.04 and 22.04 for Plastic plugin.
−
** If you log into PayPal Manager and click the Account Administration tab, you will see a link called Change Password. If you click the link, you will see a screen that will indicate whether a separate password has been configured for processing Payflow Pro transactions.
+
* Added support for native Apple Silicon (M1) architecture for both server and plugin.
 +
* Improved docs for the Tap & Chip gateway as well as existing supported gateways.
 +
* Various minor bug fixes and improvements.
 +
 
 +
==Tap & Chip==
 +
 
 +
Your solution can now support Apple Pay, Google Pay, contactless credit card payments and many more NFC payment strategies using Plastic 4 and our new integration with the Celero gateway.  You'll get a payment terminal through  [https://www.celerocommerce.com/mobile-and-online-payments Celero], walk through a quick set-up process, [[Celero#Getting_an_account|create an API key in the gateway]], and then you're ready to make contactless payments with your solution.
 +
 
 +
<Center>Plastic communicating with tap & chip supporting terminal.</Center>
 +
 
 +
<Center>[[File:Plastic Celero.png|500px|]]</Center>
 +
 
 +
==Installation==
 +
For a guide on how to install Plastic please see our [[Plug-In Installation|plugin installation]] page
 +
 
 +
==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:
 +
 
 +
<center>[https://ems.authorize.net/oap/home.aspx?SalesRepID=98&ResellerID=11334 Authorize.net]</center>
 +
 
 +
==Plastic 4 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.
 +
 
 +
{| class="wikitable"  style="margin: 1em auto 1em auto;"
 +
|-
 +
! Gateway  || merchantAccountName || txKey  || Gateway || merchantAccountName || txKey
 +
|-
 +
| ''Authorize.Net'' || Merchant API Login ID || Merchant Transaction Key
 +
| ''Celero'' || API 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
 +
|}
 +
 
 +
==Error Handling==
 +
To suppress Plastic 4 error dialogs, please use the <code>CCSetErrorCapture ( True )</code> code in your solution startup script.
 +
 
 +
For instructions on advanced error handling and custom error dialogs, see [[Plugins_101#Error_Handling.2FReporting|here]].
 +
 
 +
==Recurring Payments==
 +
If your looking to use Plastic 4 for recurring, look for any gateway the has a section called Subscription Services.  Our most popular gateway that supports recurring payments is Authorize.net.
 +
 
 +
==Documentation==
 +
<p>Click one of the links below to view payment gateway-specific documentation:</p>
 +
 
 +
<big>
 +
 
 +
{| cellpadding="15" style="margin: 1em auto 1em auto;"
 +
 
 +
|-
 +
 
 +
| style="border: 1px solid darkgray;" width="175"| [[Authorize.Net]]
 +
 
 +
| style="border: 1px solid darkgray;" width="175"|[[Celero]]
 +
 
 +
| 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 Warrior]]
 +
 
 +
| style="border: 1px solid darkgray;" width="175"|[[Moneris]]
 +
 
 +
|-
 +
 
 +
| style="border: 1px solid darkgray;" width="175"|[[PayTrace|PayTrace]]
 +
 
 +
| style="border: 1px solid darkgray;" width="175"|[[TransFirst]]
 +
 
 +
| style="border: 1px solid darkgray;" width="175"|[[VirtualMerchant]]
 +
 
 +
|-
 +
 
 +
| style="border: 1px solid darkgray;" width="175"|[[USA ePAY]]
 +
 
 +
|-
 +
 
 +
 
 +
|}
 +
 
 +
 
 +
 
 +
</big>
 +
 
 +
==Contact Us==
 +
 
 +
{{Template:Getting Help}}

Revision as of 21:12, 13 November 2023

Ambox important.png
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

Plastic 4 Overview

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

New in Plastic 4

  • Now supports Ubuntu Linux 20.04 and 22.04 for Plastic plugin.
  • Added support for native Apple Silicon (M1) architecture for both server and plugin.
  • Improved docs for the Tap & Chip gateway as well as existing supported gateways.
  • Various minor bug fixes and improvements.

Tap & Chip

Your solution can now support Apple Pay, Google Pay, contactless credit card payments and many more NFC payment strategies using Plastic 4 and our new integration with the Celero gateway. You'll get a payment terminal through Celero, walk through a quick set-up process, create an API key in the gateway, and then you're ready to make contactless payments with your solution.

Plastic communicating with tap & chip supporting terminal.
Plastic Celero.png

Installation

For a guide on how to install Plastic please see our plugin installation page

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:

Authorize.net

Plastic 4 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 Celero API 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

Error Handling

To suppress Plastic 4 error dialogs, please use the CCSetErrorCapture ( True ) code in your solution startup script.

For instructions on advanced error handling and custom error dialogs, see here.

Recurring Payments

If your looking to use Plastic 4 for recurring, look for any gateway the has a section called Subscription Services. Our most popular gateway that supports recurring payments is Authorize.net.

Documentation

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

Authorize.Net Celero First Data
Merchant eSolutions Merchant Warrior Moneris
PayTrace TransFirst VirtualMerchant
USA ePAY


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!

Retrieved from "http://docs.360works.com/index.php?title=Plastic&oldid=3577"
Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox