Fluidpay is a standard gateway integration.
Sublytics will always try and tokenize the card when processing a Sale or an Auth
Supported Functionality
Data Mapping ( Request )
Below is a table that will show how Sublytics maps its data to the Fluidpay API. Values in bold are hard coded values, the rest are dynamic based on the payment.
| FluidPay | Sublytics |
|---|---|
| General | |
| amount | Transaction Total |
| tax_amount | Transaction Tax |
| shipping_amount | Transaction Shipping |
| currency | Transaction Currency |
| order_id | Transaction ID |
| ip_address | IP Address |
| email_address | Customer Email Address |
| processor_id | value set on merchant for Processor ID |
| vendor_id | value set on merchant for Vendor ID |
| Payment Information | |
| Initial Sales ( Not Recurring ) | |
| billing_method | straight |
| Initial Sales ( Recurring ) | |
| billing_method | initial_recurring |
| Recurring Sales ( Sublytics Transaction Cycle > 1 ) | |
| billing_method | recurring |
| Payment Method (If Token ) | |
| payment_method.customer.id | Customer Card Merchant Token ( customer_id from original response ) |
| payment_method.customer.payment_method_id | Customer Card Merchant Token ( response.card.id from original response ) |
| payment_method.customer.payment_type | card |
| Payment Method ( If No Token ) | |
| payment_method.entry_type | keyed |
| payment_method.cvc | Customer Card CVV ( if present ) |
| payment_method.number | Customer Card Number |
| payment_method.expiration_date | Customer Card Expiration Month / Customer Card Expiration Year |
| 3DS Information ( If available ) | |
| payment_method.cardholder_authentication.eci | Transaction ECI |
| payment_method.cardholder_authentication.cavv | Transaction CAVV |
| payment_method.cardholder_authentication.xid | Transaction XID |
| payment_method.cardholder_authentication.version | Transaction 3ds Version |
| payment_method.cardholder_authentication.ds_transaction_id | Transaction 3ds Transaction ID ( version 2+) |
| Billing / Shipping Information | |
| billing_address.first_name | Billing First Name |
| billing_address.last_name | Billing Last Name |
| billing_address.company | Billing Organization |
| billing_address.email | Billing email |
| billing_address.phone | Billing Telephone |
| billing_address.address_line_1 | Billing Address Line 1 |
| billing_address.address_line_2 | Billing Address Line 2 |
| billing_address.city | Billing City |
| billing_address.state | Billing State |
| billing_address.postal_code | Billing Postal Code |
| billing_address.country | Billing Country |
| shipping_address.first_name | Shipping First Name |
| shipping_address.last_name | Shipping Last Name |
| shipping_address.company | Shipping Organization |
| shipping_address.email | Shipping email |
| shipping_address.phone | Shipping Telephone |
| shipping_address.address_line_1 | Shipping Address Line 1 |
| shipping_address.address_line_2 | Shipping Address Line 2 |
| shipping_address.city | Shipping City |
| shipping_address.state | Shipping State |
| shipping_address.postal_code | Shipping Postal Code |
| shipping_address.country | Shipping Country |
Data Mapping ( Response )
Below is a table that will show how Sublytics maps its data in the API response from Fluidpay
| FluidPay | Sublytics |
|---|---|
| id | Gateway Response ID ( used for refunds / voids ) |
| order_id | Gateway Response Gateway ID ( not currently used) |
| response_code | Gateway Response Code |
| response_body.card.auth_code | Gateway Auth Code |
| response_body.card.cvv_response_code | Gateway Response CVV Code |
| response_body.card.avs_response_code | Gateway Response AVS Code |
| msg | Processor Response Text |
| customer_id|customer_payment_ID | Customer Card Merchant Token |