Setup

Connect Elavon to your Brippo Portal in four steps. You'll create a reporting user in MyOpayo, then enter its details in Brippo.

1. 1

   Create a reporting user in MyOpayo

   Sign in to MyOpayo as an administrator and open Settings → Users. Add a user for Brippo (for example brippo) and give it permission to view transactions and use the reporting API. Administrator rights are not needed.

   Use a dedicated user — MyOpayo locks a user after repeated failed sign-ins. A user shared with a person would lock both of you out; one that only Brippo uses stays predictable.
2. 2

   Open Integrations in your Brippo Portal

   In the Brippo Portal go to Settings → Integrations and find the Elavon card. Click Connect.

   Full access needed — Only users with full access see Connect, Reset and Disable. Collaborators use the Elavon section once it is connected, according to their permissions.
3. 3

   Enter the account details

   Choose the Environment (Live for real payments; Test only for an Elavon sandbox vendor), then enter the vendor name exactly as MyOpayo shows it, the reporting user and its password. Click Connect.

   Vendor nameyourvendorLive

   Reporting userbrippo

   Password••••••••••••••••

   What happens next — Brippo checks the details with Elavon straight away and the card shows Connected when they work. The password is stored encrypted and is only ever used to sign Brippo's requests to Elavon.
4. 4

   Manage payments from Payments → Elavon

   The Elavon entry appears under Payments, laid out like the Stripe payments list: tabs for All, Successful, Uncaptured, Refunds and Failed, a search box for an order number, VendorTxCode or transaction id, and filter buttons for dates (Elavon reports one month at a time), amount, card last four, type, result and customer. Click a transaction to see its details and the actions its state allows: Capture and Cancel for deferred payments, Authorise and Cancel for authenticated ones, Refund, Void and Repeat for successful ones.

   Who can do what — Full-access users can do everything. Collaborators need the Elavon section plus Payments refund for refunds, Payments capture for capture, cancel, authorise and void, and Payments manual charge for repeats.

Troubleshooting

• !"Elavon did not accept the vendor name, user or password, or the user is locked." Check the spelling of all three, then look at the user in MyOpayo → Settings → Users: a locked user must be unlocked there.
• !"Elavon could not validate the request signature." The password does not match. Set a new one in MyOpayo, click Reset on the Elavon card and connect again.
• !"…this server's address … is not in the account's Valid IPs" (4020) when capturing, cancelling or voiding. Elavon only accepts those operations from listed addresses. The message names the address; add it in MyOpayo → Settings → Valid IPs with subnet mask 255.255.255.255 and try again. The same address is shown on the Elavon card in Brippo.
• !"This transaction has already been settled. Refund it instead." Voids only work before Elavon's overnight settlement. Use Refund for anything older.