360Works Plastic User Guide

The CreditCardProcessor provides easy credit card processing capabilities for FileMaker Pro.

Using the plugin

Consult the "CreditCardProcessor Example.fp7" Filemaker file which contains examples of plugin usage. For additional help troubleshooting the Plastic plugin, consult the 360Works Product Support Wiki.

You must have an active merchant account with a company such as Authorize.net or PayPal Payflow Pro to use this plugin.

Note: Authorize.net test accounts will not work, you must have a full account. Once you have an account, obtain a transaction key in the Account/Security Settings/Transaction Key area on the account.authorize.net website.

Selecting a gateway provider

Before you begin processing charges, you need to tell the plugin what type of gateway account you are using. This is done by calling CCSetGateway and passing in your gateway type. If you skip this step, it is assumed you are using an Authorize.net account.

CCSetGateway("Authorize.net") // for Authorize.net accounts (the default)

CCSetGateway("PayPal") // for Payflow Pro accounts

Running Charges

Once your merchant account is set up correctly, running charges can be done in one quick step. Here is an example of its usage:

CCProcessPayment(
merchantAccount;
transactionKey;
chargeAmount;
cardNumber;
expDate
)

The above method will process a payment transaction for a card, and return the gateway transactionID for the transaction, or the word "ERROR", if the transaction fails for some reason. For additional information about the failure, call CCLastError.

It is important that you store this resulting transactionID, you may need it to VOID the transaction later.

The minimum amount of information needed to process a transaction is:

• Authorize.net merchant account name
• Authorize.net transaction key (obtained at https://account.authorize.net/)
• credit card number
• credit card expiration date
• dollar amount

There are numerous additional optional parameters you can provide such as addresses, email, po number, etc. These are not usually required to process an order, but can be useful for address verification purposes or linking a transaction with a customer or invoice. To supply additional parameters, add them as extra parameters onto the end of your function call in the form 'key=value', like this:

CCProcessPayment(
merchantAccount;
transactionKey;
chargeAmount;
cardNumber;
expDate;
"chargeDescription=" & description;
"cardType=" & cardType;
"verificationCode=" & securityCode
)

Here is a list of the most common valid additional parameters:

authMode

used to process authorization-only transactions. See CCProcessPayment for more information.

firstName

first (given) name of the credit card holder

lastName

last (surname) of the credit card holder

companyName

company name on the credit card

chargeDescription

brief description of the charges

verificationCode

the numeric verification code on the credit card. This is also known as the Card Security Code (CSC), sometimes called Card Verification Value (CVV), Card Verification Value Code (CVVC), Card Verification Code (CVC), or Verification Code (V-Code or V Code)

cardType

the type of credit card being processed (visa, mastercard, etc)

invoiceNumber

an arbitrary invoice number for your records

poNumber

an arbitrary purchase order number for your records

customerId

an arbitrary customer id for your records

address

the billing address street address

unitNumber

the billing unit/apt no.

city

the billing address city

state

the billing address state

zip

the billing address zip

country

the billing address country

phone

the cardholder's phone numer

fax

the cardholder's fax numer

shipFirstName

the shipping recipient's first name

shipLastName

the shipping recipient's last name>

shipAddress

the shipping street address

shipCity

the shipping address city

shipState

the shipping address state

shipZip

the shipping address zip

shipCountry

the shipping address country

shipCompanyName

the shipping recipient's company name

email

the cardholder's email address

currency

currency of the transaction amount (USD, for example)

track1

track1 data from a card reader^*.

track2

track2 data from a card reader^*.

url

an alternate url to which to send a gateway transaction (particularly useful for Authorize.Net emulators)

user

if you set up one or more additional users on the account, this value is the ID of the user authorized to process transactions (Payflow Pro only)

partner

The ID provided to you by the authorized PayPal Reseller who registered you for the Payflow Pro service. Usually this value is either PayPal or VeriSign.

tender

Set The tender type (method of payment) ^**.

proxyAddress

The host address of a proxy server. Required to run Payflow Pro transactions via proxy.

proxyPort

The port number of a proxy server. Required to run Payflow Pro transactions via proxy.

proxyLogon

The username for an account used to access a proxy server. Pay

proxyPassword

The password for an account used to access a proxy server.

Void/Refund Parameters: These parameters are only used in the CCVoidPayment and CCRefund functions:

cardNumber

The credit card number being voided (this is optional for CCVoidPayment)

expirationDate

The expiration date of the credit card number being voided, in MM/YY format (this is optional)

---

Card-present transactions

Before attempting to perform a card-present transaction, make sure your gateway merchant account is configured for processing card-present transactions. Before performing a card-present transaction using the CCProcessPayment function, you must first call the CCSetGateway function, passing in the optional parameter "cardPresent=true". If the CCSetGateway function returns a 1, then you can perform a card-present transaction using the syntax below.

Authorize.net
A card-present transaction should pass in Track 1 or Track 2 data using the additional parameters track1 and track2. Track 1 and Track 2 are parts of the raw string generated when a credit card is passed through a magnetic stripe card reader. See http://www.exeba.com/comm40/creditcardformat.htm for a description of the Track 1 and Track 2 data formats. Note: You do not have to pass in a card number and or an expiration date when performing a card-present transaction; the Authorize.Net gateway will read this information directly from the track data. Make sure you pass in empty quotes ("") for those parameters.

CCProcessPayment(
merchantAccount;
transactionKey;
chargeAmount;
"";
"";
"track1=B4111111111111111^CardUser/John^111110100000019301000000877000000"
)

Payflow Pro
A card-present transaction using Payflow Pro should also pass in Track 1 or Track 2 data using additional parameters. However, you must pass in empty strings for the card number and expiration date.

CCProcessPayment(
merchantAccount;
transactionKey;
chargeAmount;
""; //notice the empty string in place of the cardNumber
""; //notice the empty string in place of the expirationDate
"track2=;4912000033330026=15121011000012345678?"
)

Tender param options (Payflow Pro only)

A = Automated clearinghouse
C = Credit card
D = Pinless debit
E = Electronic check
K = Telecheck
P = PayPal

Voiding previous transactions

To void a transaction, you need the transactionID which was returned by the CCProcessPayment function. Pass this (along with other payment info) to the CCVoidPayment function. See the function documentation for an example of voiding a previous transaction.

Crediting / Refunding previous transactions

To credit a transaction, you need the transactionID which was returned by the CCProcessPayment function. Pass this (along with other payment info) to the CCRefund function. This is similar to the void process, but accepts a dollar amount.

CCRefund(
    settings::merchantAccount ;
    settings::transactionKey ;	// your transaction key or password
    "1321353789" ; // the transactionID being credited
    "1234" ; // the last four digits of the credit card number
    0.02 ; // the amount of the refund
    "expirationDate=" & Date(12, 1, 2010) ; // credit card expiration date
    "firstName=John" ; // card holder first name
    "lastName=Doe" ; // card holder last name
)

Set Variable [ $result = MyPluginFunction("x" ; "y" ; "z") ]
If [ $result = "ERROR" ]
    Show Custom Dialog [ "An error occurred: " & CCLastError ]
End If

// chain multiple calls together
// if any of the functions fail, the calculation will 
// short-circuit with a result of false,
// and none of the subsequent function calls will be evaluated.
Set Variable [ $success = 
    FirstPluginFunction("x") and 
    SecondPluginFunction("y") and 
    ThirdPluginFunction("z") 
]
If [not $success]
    Show Custom Dialog [ "An error occurred: " & CCLastError ]
End If

CCSetGateway("Authorize.net" ; "cardPresent=true");

Set Variable[$data = mytable::swipe]
Set Variable[$accountNumber = getValue($data ; 1)]
Set Variable[$cardHolderName = getValue($data ; 2)]
Set Variable[$expirationYYMM = getValue($data ; 3)]
Set Variable[$additionalData = getValue($data ; 4)]

CCVoidPayment (
    Settings::merchantAccount ;
    Settings::transactionKey ;
    123 ; // the previous transaction key
    "cardNumber=4444444444444441" ;
    "expirationDate=04/08" ;
    "firstName=Bob" ;
    "lastName=Smith"
)