FarApp imports tokenized credit card data to NetSuite by default. Most storefronts do no support capturing full payment details, but if they were to support this and FarApp were to import this data to NetSuite for you, it would be in breach of PCI compliance. Please see this article for more information: https://support.farapp.com/hc/en-us/articles/115011513148-Credit-Cards-and-PCI-Compliance
Tokenized credit card data is sufficient to capture payment in NetSuite for most payment gateways. The table below lists any exceptions that FarApp is aware of. If you are using a gateway that is not listed here and know what its unique requirements are, please let us know and we will add it to the table for future reference.
|Required Data||Supported by FarApp|
|Amazon Pay||Tokenized data.||Yes.|
|Braintree||Tokenized data. Some customers map the Braintree ID from the storefront to a custom field in NetSuite.||Yes. If the Braintree ID is needed, customers usually create a custom field called custbody_braintree_id. After creating the custom field, customer should open a support ticket and provide a sample order as well as what the Braintree ID is for that order.|
|Altapay||Tokenized data. Some customers map transaction_id to pnRefNum.||Yes. transaction_id is supplied in customdata from Magento. If needed, customer should open a support ticket and provide a sample order as well as what the transaction_id is for that order.|
|CyberSource||Tokenized data. Some customers map transactionid to otherRefNum.||Yes. If needed, the customer can configure a mapping for otherRefNum here.|
cardauthapprovalnumber needs to be mapped to payPalTranId. authcode needs to be mapped to authCode.
Also requires full credit card number and expiration date. Storefronts will not supply this data in order to maintain PCI compliance. Valid test CC numbers and expiration dates can be used.
Some customers need paypalProcess set to true.
Some customers need ccAvsZipMatch, ccAvsStreetMatch and ccSecurityCodeMatch set to '_y'.
Some customers want a unique CC number used for PayPal Express.
The customer can configure mappings for payPalTranId and authCode here.
The customer should open a support request with FarApp to let us know what valid test CC numbers and expiration dates to use. Expiration data must be a valid date in the future. Valid CC numbers can be found here.
paypalProcess can be set to true by FarApp or NetSuite can be configured so that paypalProcess is always true.
FarApp can set
ccAvsZipMatch, ccAvsStreetMatch and ccSecurityCodeMatch to always be '_y' or only set this in certain situations based on data visible in the order API for the storefront.
If a unique CC number is needed for PayPal Express, please choose a valid test CC number from here and supply FarApp with several examples of PayPal express orders in order to complete the mapping.
*Please note that payment gateway configuration support is not within FarApp's scope. Though we will do our best to provide guidance on the configuration your payment gateway, ultimately proper configuration is the responsibility of the customer. The table above is based off what FarApp has discovered by working with past customers, but your individual configuration may be unique even if using the same gateway. If any data is needed beyond tokenized credit card data, it is the responsibility of the customer to work with the payment gateway to determine what additional data is needed and to clearly communicate to FarApp what additional fields will need values mapped to them. The customer should supply sample orders for these mappings and should inform FarApp what values on the sample orders need to be placed in which NetSuite fields. Many of these mappings can be set up without help from FarApp. FarApp will not violate PCI compliance even if asked to.
There are no known restrictions for the payment gateway that is used to capture and authorize payments in the storefront.