Hello.
I am trying to understand the differences between api use-cases for authorization versus paymentAccount (triPOS Direct). The documentation mentions authorization as "...hold funds when the total amount of the purchase is unknown."
/api/v1/authorization
Creates a new card authorization based on the passed in parameters
/api/v1/paymentAccount
Creates a card account token based on the given data
Basically I am looking to make an api call that gets the paymentAccountId for processing by our ticketing vendor. In other words, I would like to pass the paymentAccountId to their api and they finish the payment processing as they have the account with Vantiv.
The ticketing partner thinks I should pass the paymentAccountId from authorization. I am kind of thinking paymentAccount.
Can you please advise regarding the differences? Also, is this a common workflow? Thanks!
Steve
Hi, Steve. The authorization endpoint is used to put a hold on cardholder funds, which still requires a separate completion submission to ultimately charge the cardholder. Note that a token is not returned as part of the authorization response.
The paymentAccount endpoint is a separate, stand-alone request to tokenize a card (though no card verification takes place with this method). If you have any additional questions, feel free to reach out to us directly using tripossupport@vantiv.com and our team will be happy to assist.