Test...

But I had the create option disabled. It's enabled now, and when I create a customer programmatically and then try
https://sdash-test.chargevault.com/create?key=0bad907d09&code=4...

I get a page asking for a plan, which I don't want (the customer was created with one) and no form for provided credit card info. If create is replaced with update in the URL things work, but with the submit button wording problem that started this ticket.

Still waiting for a response on this.

We want to create a customer identity with a form we have control over. Then use your hosted payments for the first time with the new customer. If "create" is changed to "update" in the above chargevault URL it works, but the button says Update Subscription, which is inappropriate in this case (should say Create instead).

The create URL above asks for the plan, which isn't correct since the key points to a customer record that already has a plan. And when you select a plan (again) and click pay now it says invalid form.

Also, http://support.cheddargetter.com/discussions/problems/1568-saq-c-vt... is still pending resolution. I don't care how you get the document to me.

I can't authenticate for that URL, but it's great to know of the update. Please let me know when it's on the live system. Presumably there'll be something to control it in the hosted payments customization settings.

Very good. Thanks.

Well, not so good. When I first create a CG customer record (which has an indicated plan), and then use the create option with the key, as with https://sdash-test.chargevault.com/create?key=dd83e636c6&code=5...
I then get a page asking again for the plan. The customer already provided a plan when they selected a buy option and we created the record for them. And we don't want them to see all of our plans, some of which are for special sales use.

If I select a plan again any way the view expands with a new green box that is empty and a create subscription button that, when clicked, gives a form validation error. Screen shot attached.

Both these problems were noted above. I thought the new feature would avoid all this. The behavior we want is what we get with the update option, but with the submit button label changed.

"The create page cannot be used for a customer who already exists."

That wasn't clear to me, and it accepted the create request with a key so I was confused. We can customize the update button so it can apply to both initial and update uses, which should satisfy our needs. Thanks for the new feature.