cancel
Showing results for 
Search instead for 
Did you mean: 

Recurring payments initiated by us

Hi - I'm trying to process reoccurring payments with the following requirements:

 

  • Payment processing would be initiated by us
  • Customer would enter card data on first transaction only. We would bill the card monthly, with potentially different amounts but would not have the card data present.
  • Want to require the CVV on first transaction. If it succeeds, when we bill the card monthly, CVV would not be required for transactions later.
  • We do not want to stored sensitive information like credit card data
  • User would have option later to specify a different card or update their profile (this can be done by SOAP, XML or any commonly available method)
  • This would include echeck transactions

 

Effectively, we're trying to create a similar experience as Amazon, where you enter the card data once. When you buy in the future, you only select your profile/(card and shipping address) you want to use and the payment goes through, without entering in card or CVV again. The only difference is, we're initiating the payments in the future as our services is handled on a subscription basis.

 

My initial thought was CIM. However, due to the 3rd requirement, CIM may not work for this. What's the best route to achieve the result we're after?

 

Bill

 

 

 

martin1b
Contributor
1 ACCEPTED SOLUTION

Accepted Solutions

The "createCustomerProfileTransactionRequest" CIM API method provides for charging the customer's credit card without requiring the card code.

 

In other words, the CIM API should meet all of your requirements.

View solution in original post

jbubbison
Contributor
1 REPLY 1

The "createCustomerProfileTransactionRequest" CIM API method provides for charging the customer's credit card without requiring the card code.

 

In other words, the CIM API should meet all of your requirements.

jbubbison
Contributor