Closed LoggiaNG closed 4 years ago
I know the documentation says otherwise. But the way Im doing preauthorizations for the past 2 years is the following.
To capture a payment you send a request to '/api/transactions/{id}' with form data 'Installments' => 0, 'Amount' => {amount}
To release a payment you send a request to '/api/transactions/{id}?amount={amount}'
Hope this help.
@matthewrgourd Is the way we do preauthorization going to change to what is now described in the docs ?
Hi @odysseas12 let me get back to you after I receive an answer from our dev team...
What does PaymentMethodId=1 do? We can't find it in the documentation.
@VrasidasP I dont know exactly PaymentMethodId=1 is but if not included the transaction is not an authorization but a card charge.
Hi there, feedback from our development team is that If you want to create a PreAuth transaction you must pass property IsPreAuth=true
and PaymentMethod=1
(PreauthCapture) on create transaction endpoint: https://developer.vivawallet.com/online-checkouts/native-checkout-v2/#step-5-make-the-actual-charge Hope this helps!
Hello, we have implemented the following procedure, for our food delivery application.
The problem is that on step 2, we thought that we would get feedback if the card data is incorrect (or if the card has sufficient funds), before sending the delivery order to the store. But we see that this is not the case. Are we missing something here?
Ideally we would like to inform the user of any mistakes in the card input form or the card itself on step 2. As it is now, the user sees his card being "accepted", his order being processed, but then rejected because of card error. We wish to make every step clear to the client, and the store.
Thank you.