Similarly to shipment method mappings, whenever FarApp sees an order with a new payment method, that payment method gets added to the left column of the Payment Method Mappings table in your Pay Method Settings. At that point, you’ll get an error letting you know that a payment method mapping is missing so you can go in and map the new storefront payment method to the corresponding NetSuite payment method by selecting the appropriate payment method from the dropdown in the NetSuite Payment Methods column. You will only have to do this the first time an order comes in with a specific payment method. After that all orders with that payment method will use the mapping you set. The payment method mappings themselves will only be set up once you begin importing test orders but you’ll need to complete the following steps to prepare for that.
Mapping Payment Methods
- Navigate to your Pay Method Mappings.
- Payment methods aren’t preloaded into FarApp from your NetSuite because FarApp needs to know the subsidiary that the payment methods should be pulled from. Now that you’ve mapped your subsidiaries, you can load your payment methods from NetSuite by clicking the button labeled “Reload NetSuite Payment Methods”.
- Select Do Not Post from the Default payment method to post to when no match found: dropdown. This will ensure that orders can’t sync to NetSuite until a payment method has been mapped and will notify you to map them (once you configure your notifications).
The leading practice is to capture payment in your marketplace/cart at the time of order (most are either preconfigured to do this and many don’t have an option to do external capture). Out of the box, FarApp will import the tokenized credit card data on orders to NetSuite, which can later be used to refund orders in NetSuite. The following information will be populated on the order:
- P/N Ref.
- Auth. Code
- Credit Card Approved (this field ensures payment isn’t captured in NetSuite)
Please proceed with Step 5: Order Sync Customer Matching.