Obsidian Registration Creates Incomplete NMI Customer Vault Records

[thejasonharvey]

Please go through all the tasks below

• Check this box only after you have successfully completed both the above tasks

Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.

When a transaction uses tokenized payment information to process a charge request the new Obsidian event registration feature does not include the first/last name fields when tokenizing using Collect.js.

Expected Behavior

When a transaction occurs the NMI Customer Vault Record would include the first and last name of the person making the payment.

Actual Behavior

When a transaction uses the tokenized Collect.js method it does not record the first and last name of the person making the transaction upon creation of the new record.

Below is more information related to this provided by our payment processor:

After reviewing the transactions without the name created by the Rock RMS event Obsidian registration in greater detail. The transactions use tokenized payment information to process a charge request (which is good).

You can tell this by looking at the transaction in the NMI gateway and seeing that a "Customer ID" is visible. The "Customer ID" is a reference to the NMI vault record, which contains the sensitive payment information (card/bank-account) along with the customer's first and last name.

When using NMI's Collect.js to tokenize payment data in the browser, it would need to include "first_name" and "last_name" fields in the web form or tokenization request. Technically speaking, NMI does not require the first_name, last_name to be present to charge a card. However, it is strongly recommended that this information be included for better transaction context and records in the gateway.

The current design of the new Obsidian registration does not include the first/last name fields when tokenizing using Collect.js. The Collect.js implementation could be updated to include the "first_name" and "last_name" fields. It could be pre-filled from the existing information using hidden form fields or similar - as an example.

Related Links That May be Helpful to Rock:

• https://secure.process4changegateway.com/merchants/resources/integration/integration_portal.php?tid=db48a1b512a6105f3d5f5107e1febcf2#cjs_integration_inline1

• Rock/Rock.NMI/gatewayCollectJS.js

  Line 43 in 55273a7

  self.validationFieldStatus = {

Steps to Reproduce

Go to an instance of Rock as a user that has no NMI information previously recorded
Register for an event that requires a form of payment using the Obsidian registration block.
Go to the payment processor to view the customer vault record that was created.

Rock Version

14.2

Client Culture Setting

en-US