0 Votes

Add a getPaymentProfile method to Accept.js

Status: New
by on ‎04-05-2017 11:59 AM

Hi there,


It seems like almost a no-brainer to have a method, using Accept.js, to get a payment profile, so that a self-hosted payment form could be populated without from the client machine, rather than having to go through our server using the API. It seems like all it would need is the customerProfileID and the customerPaymentProfileID to pull that info, just like the existing getCustomerPaymentProfile() method found in the AuthorizeNetCIM class.

on ‎08-09-2017 02:35 PM

Hi @jima


Could you elaborate, a little on this? I'm interested to hear how you would like this to work and also get an example use case.  Remember, Accept.js still requires going through your server to have your server send the payment request through our API. It just tokenizes the card data in the browser first.


on ‎08-10-2017 07:39 AM

The idea is to be able to have an HTML form, hosted on my server, and be able to (pre)populate it with the user's stored data without having to go through our server. Yes, submitting the form data, for a transaction request or similar, would still go through our server, but the inital form load would not.


Simple use case:
User logs into our customer portal, where they have previously set-up (and saved) payment info, and we have captured their customerProfileID and customerPaymentProfileID.
User (now identified through login) proceeds to a section of the customer portal, where they can view/change/update their payment info, and clicks on an "Edit/Update Payment Info" button in their profile, which invokes a payment webform that, upon load, is pre-populated with the previously saved payment info, by means of an AJAX call, through Accept.js, using the previously stored customerProfileID and customerPaymentProfileID as arguments.

Le me know if you need anything else to help paint the useage picture.

on ‎08-13-2017 03:01 AM

You can already do a getCustomerPaymentProfileRequest with customerProfileId and customerPaymentProfileId, then an updateCustomerPaymentProfileRequest with the payment nonce from Accept.js in the opaqueData dataValue instead of credit card information.


You could also use a getHostedProfilePageRequest, just by posting a customerProfileId, which will return a secure hosted form where customer can modify their stored payment details.

on ‎08-14-2017 08:03 AM

All fine solutions for certain things, but not at all what I have requested.