Have your own great idea for a new API feature?

or maybe a suggested improvement to an existing one? Share it and become a god of the developer world.

New Idea

I have a scenario where I'm performing an authorization with a payment nonce, then creating a profile from that successful authorization, and later capturing the authorized amount. This is a nice workflow because I only create a payment profile if the authorization succeeds.

 

But unfortunately, this workflow is not possible because the authorization is not associated with the payment profile, and doesn't show up under its history. In a scenario where we're using a profile for recurring transactions, it's a big deal to us to have the initial payment in the history.

 

See this thread for more details as to alternatives that are less ideal.

 

 

It'd be very helpful if, when I create a profile from a transaction, if that transaction became the initial transaction in the payment profile's history, and I was able to capture it as though it had been issued from that profile.

 

0 Votes

Provide a way or any best practice to ensure initial session is same as return confirmation from iFrame session. Just calling getTranasctionDetails and matching transaction ID and timestamp does not ensure same session.

0 Votes

I have implemented accept hosted form into iFrame and embeded that iFrame into my main payment page.

Now my payment page has a cancel and previous button itself. so, after integration of accept hosted form there are two cancel button in my page.

We are looking for such a feature by which we can show/hide cancel button in accept hosted payment page.

0 Votes

I am sending a createTransactionRequest with <createProfile>true</createProfile>.

 

If there is already a profile associated with the credit card the following error is included in the response:

 

<profileResponse>

<messages>
<resultCode>Error</resultCode>
<message>
<code>E00039</code>
<text>A duplicate record with ID 1812052420 already exists.</text>
</message>

</messages>

</profileResponse>

 

Then I have to send a getCustomerProfileRequest to get the customerPaymentProfileId which is required in order to use the profile in the future.

 

Is it possible to include the default customerPaymentProfileId in the error message so I would not have to send another request to your server?

 

In our system we want to use tokenization but we can't always precreate the profiles.

 

Thank You

 

Lynn Millard, Software Engineer

The Hudson Group

360 Merrimack Street

Lawrence, MA 01843

 

0 Votes

Add a getPaymentProfile method to Accept.js

Status: New
by jima 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.