Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
authnet
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Extensions
  • authnet
  • Issues
  • #14

Closed
Open
Opened Oct 06, 2020 by JonGold@JonGoldReporter

All transactions in Auth.net are recorded as coming from the CiviCRM server

With most processors (including legacy Auth.net), if the Civi server is at IP address 1.2.3.4, and I make a donation from 5.6.7.8, the second IP address is what's displayed as the originating IP address.

However, with the new processor, all transactions are logged from the Civi server's IP address in Auth.net, which amongst other issues causes their velocity filter settings to not work as expected.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: extensions/authnet#14