Issue Adding Second Customer Payment through Scren Based API

We Add Customer Payments through Acumatica’s Screen Based API (We use Authorize.NET’s Customer Information Manager for processing).  It works fine for a customer’s first payment method.  When we attempt to add a new Payment Method (Same CustomerProfileId but different PaymentProfileId), it doesn’t throw an exception but it does not add.  It returns the existing Payment Method Token.

Here is my current code:

                AR303010Content AR301000 = context.AR303010GetSchema();
                context.AR303010Clear();
                AR303010Content[] AR303010content = context.AR303010Submit(
                    new Command[]
                {
                    new Value { Value = customerId, LinkedCommand = AR301000.PaymentMethodSelection.Customer },
                    new Value { Value = ccType, LinkedCommand = AR301000.PaymentMethodSelection.PaymentMethod },
                    new Value { Value = "AUTHNETAPI", LinkedCommand = AR301000.PaymentMethodSelection.ProcCenterID },
                    new Value { Value = "QUANTUM", LinkedCommand = AR301000.PaymentMethodSelection.CashAccount },
                    //new Value { Value = customerProfileId, LinkedCommand = AR301000.PaymentMethodSelection.CustomerProfileID },
                    new Value { Value = paymentProfileId, LinkedCommand = AR301000.PaymentMethodDetails.Value},
                    new Value { Value = ccToken, LinkedCommand = AR301000.PaymentMethodSelection.CardAccountNo },
                    AR301000.Actions.Save,
                    AR301000.PaymentMethodSelection.CardAccountNo
                });

                var cardAccountNo = AR303010content[0].PaymentMethodSelection.CardAccountNo.Value;

Has anybody else had a similar issue?  This issue only affects the API as we’re able to add multiple CC payments through the UI.