We have an enterprise 13 instance running, and are attempting to utilize authorize.net for payment of invoices. Using the provided code without customizing, we are having some challenges submitting charges to authorize.net. We can successfully submit transactions to Authorize.net if we remove some of the fraud detection. We do not wish to go live in this state, but it is sufficient for testing. The customer information and address information is ignored, and the customer information submitted to Authorize.net is the internal user's information instead. This creates a street address and zip code verification error every time. No code has been altered here, and we were able to successfully submit correct transactions using the same authorize.net account with a version 12 instance prior.
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Knjigovodstvo
- Zaloga
- PoS
- Projekt
- MRP
This question has been flagged
We were able to sort this out. It wasn't really an issue with the Authorize.net code, just the way that we were testing it. I think it is worth posting as this isn't obvious. We have both Authorize.net for invoice/online payment and Vantiv for credit card swipe at POS. We do not have the website app installed, but we wanted to use online payment for a couple different reasons.
In order to have a customer pay their invoice using online payment link and test it yourself:
Create invoice
Open invoice; Action/Generate payment link
Copy link and enter it in a new browser
It's important to enter the link in a browser using incognito mode/private, or another browser entirely. If you're logged in, Odoo recognizes the Odoo user as the customer regardless of the way that fields are filled for the customer.
This is the same if you use the "Preview" button and attempt to pay for the customer. You must open the link in a different browser, not logged in, private mode, etc.
Enjoying the discussion? Don't just read, join in!
Create an account today to enjoy exclusive features and engage with our awesome community!
Prijavi| Related Posts | Odgovori | Prikazi | Aktivnost | |
|---|---|---|---|---|
|
0
apr. 22
|
2624 | ||
|
4
jan. 21
|
9302 | ||
|
3
nov. 18
|
4949 | ||
|
0
maj 17
|
3407 | ||
|
5
maj 17
|
8040 |
Please clarify what you mean by "remove some of the fraud detection". What did you remove exactly and where?
Also, when you say "the customer information submitted to Authorize.net is the internal user's information instead", is it because of the change you made? (because it's not supposed to be the standard behavior). It would help if you could copy the content of the architecture of the 'form button template' of your Authorize acquirer, see https://i.imgur.com/SUqGVIH.png