VirtualMerchant plugin pass name(s) of product(s)

-- HikaShop version -- : 2.5.0
-- Joomla version -- : 3.4.1

Need to modify VirtualMerchant plugin so that the name(s) of product(s) purchased are passed through to Elavon/Virtual Merchant. How can this be done?

That's strange because before we upgraded to the new version of HikaShop, we used a no longer compatible plugin that sent product names through. So Virtual Merchant allows it; the problem seems to be with the plug-in.

I've confirmed this with the Virtual Merchant folks.

Is there any way to get in touch with whomever developed the plug-in?
Thanks

please see attached - shows how custom fields can be added to what's passed to VirtualMerchant, and our example showing that Product was added.

Hopefully the attachment will go through this time!

Product is available as a custom field (which can be added within VirtualMerchant as shown on the screen print). Other custom fields can be added as well. Those fields that don't say "System Field" are custom fields, added by clicking on the "Add New Field" button within each section.

Not sure if the attachment ever went through to you after I uploaded it.

Here is a copy/paste of the Terminal within Virtual Merchant:
Payment Field Setup
Order Section Required OrderSection System Field
Amount Yes ssl_amount System Field
Reference Type No ssl_customer_code System Field
Product No Product
Invoice Number No ssl_invoice_number System Field
Credit Card Number Yes ssl_account_data System Field
Expiration Date(MMYY) Yes ssl_exp_date System Field
CVV2 Indicator Yes ssl_cvv2cvc2_indicator System Field
CVV2 Yes ssl_cvv2cvc2 System Field
Sales Tax No ssl_salestax System Field
Approval Code Yes ssl_approval_code System Field
Start Date Yes ssl_start_date System Field
Billing Cycle Yes ssl_billing_cycle System Field
Next Payment Date Yes ssl_next_payment_date System Field
Last Payment Date Yes ssl_last_payment_date System Field
Number Of Payments Yes ssl_number_of_payments System Field
Comments No ssl_description System Field
End of Month No ssl_end_of_month System Field
Bill on Half No ssl_bill_on_half System Field
Skip Payment No ssl_skip_payment System Field

Billing Address Required BillingAddress System Field
Company No ssl_company System Field
First Name Yes ssl_first_name System Field
Last Name Yes ssl_last_name System Field
Address1 Yes ssl_avs_address System Field
Address2 No ssl_address2 System Field
City Yes ssl_city System Field
State/Province Yes ssl_state System Field
Postal Code Yes ssl_avs_zip System Field
Email Address Yes ssl_email System Field
Country No ssl_country System Field
Phone No ssl_phone System Field


Within each section (e.g., Payment Fields), there's the option to click on a button called "Add a New Field." In our case, we added the Product field (ages ago). As you can see, it's not labeled as a "System Field" (because it's a "custom" field).

So we just need to add coding to pass this system field!

Here's what the representative from Virtual Merchant/Elavon/Converge told me:
API can pass custom fields as long as they’re added into the custom fields section of the customer’s Terminal – Payment Fields section. ( Payment Fields in the Terminal section of myvirtualmerchant.com/Converge.) Note that custom fields can be added via the “Add New Field” button. The column to the right labeled “System Field” shows whether the fields are integrated as system fields or custom fields. Note that the Product field is blank under System Field column, indicating that it is a custom field.

To send the custom fields to Virtual Merchant, a developer must add code in the API code section with the custom field names and the information (in this case, ssl_product and the information that goes along with it, the same way that the credit card information is passed via ssl_accountdata).