Anybody using solupay as well as woocommerce / payeezy? Solupay is being frustratingly vague about the field mapping necessary to capture a payeezy auth in NS

Keep in mind that Solupay is both a provider of FirstData services (which you connect to either through Payeezy or NMI), and provides the bundle of customizations in NetSuite to use the NMI or Payeezy gateway to send payments to FirstData. What are you trying to do with you WooCommerce / Payeezy payments in NetSuite? Since they aren’t being paid through NetSuite, Solupay isn’t really involved, other than being the gateway provider. Also, I agree that talking to Solupay and asking for any kind of documentation or technical details is just an exercise in frustration. They seem to have nothing written down, and rely upon tribal knowledge and getting the right person to achieve anything. In our situation, we use Solupay within NetSuite, but also make direct payments to the gateway through an external application. We simply gather enough details to record a Cash Sale from those external payments, and send them to NetSuite through a Restlet we created. We use custom body fields to record the unique values we need for searching and reconciliation. This may not be sufficient for you, but was good enough for our needs.

Thanks for the reply! We auth in woo/payeezy and need to capture in netsuite, when we actually process the order. We use Celigo for importing data into NS. They told us this was possible but gave us no details other than a need to format a string specifically for use in Netsuite comprised of Payeezy details. We did this, but they never told us which field to map to - it's not the native n/s pn. ref, that's all we have sussed out

I see. Our experience is similar. We also moved from Cybersource to Solupay, but found that we were never really able to get external payments into NetSuite in such a way that they would look like a real NetSuite payment. P/N ref is the usual field, but if the payment didn’t initiate in NetSuite, I’m not sure that setting it would do anything.

Did they provide you a concatenation string to build?

Our situation was slightly different, since we are actually doing auth and capture both in our external application, and just recording the payment after the fact in Netsuite, so this probably wouldn’t help our current process. We did consider having them separate and doing something like you are, but ultimately decided the external capture was fine for us. I do wish it could have been integrated into Netsuite, though

I did something similar in my previous company. We authorised payments in BigCommerce, and captured on invoicing in NetSuite. This was with the eWAY gateway. I ran into problems storing the authorisation code on the native P/N Ref field (mainly it randomly disappeared) so I used a custom field, and copied it to the native P/N ref field on creation of invoice.