Accept Hosted Feature Parity with SIM: Customer ID, Line Items, and Field Configuration

[Tarangtbsit]

Hello Authorize.Net Team,

We have recently migrated from the legacy SIM (Server Integration Method) integration to Accept Hosted and are trying to achieve feature parity with our previous implementation.

Our goal is not to customize the UI, but rather to expose the same data fields and behaviors that were available in SIM while allowing Authorize.Net to continue hosting the payment page.

We have a few questions regarding the capabilities of Accept Hosted:

1. Customer ID Field
   • In SIM, we were able to collect and submit a Customer ID.
   • In Accept Hosted, we cannot find any option to display a Customer ID field on the hosted payment form.
   • Is this field intentionally not supported in Accept Hosted?
   • If it is supported, how can it be enabled?
2. Feature Parity with SIM
   • Is there a supported way to configure Accept Hosted so that it displays all of the fields that were available in SIM?
   • We are interested in the functional behavior rather than visual customization.
   • Specifically, we would like required fields to be displayed as required, optional fields to remain optional, and the hosted form to respect the merchant account's configuration wherever possible.
3. Merchant Account Configuration
   • Can Accept Hosted automatically retrieve and honor the merchant account settings (configured in the Merchant Interface) using the API credentials (API Login ID and Transaction Key)?
   • For example, if billing address, card code, or other fields are configured as required in the merchant account, can the hosted form automatically enforce those settings, or must every field requirement be explicitly specified in the hostedPaymentSettings request?
4. Line Items
   • We are submitting line item data as part of the transaction request.
   • However, the Accept Hosted payment page never displays the line items.
   • Is this expected behavior?
   • If so, is there any supported mechanism to display the purchased items on the hosted payment page, or are line items intended only for transaction processing and reporting?

Our objective is to migrate from SIM without losing functionality. If there is a recommended approach to achieve behavior equivalent to SIM, or if there is documentation describing which SIM features are intentionally unavailable in Accept Hosted, we would greatly appreciate that guidance.

Thank you for your assistance.

[DelaJaun]

The main thing to clarify is that Accept Hosted doesn’t provide complete SIM feature parity. Customer ID and line-item display may not be supported on the hosted form, while field requirements need to be configured through the Accept Hosted request. The official Accept Hosted documentation should confirm which SIM features carry over.