Region
EU · US.
What this does today
Each company connects its own Converge merchant account and maps it to the part of the business it settles for:
- Per-brand association. A connection belongs to one brand; its products are covered through that brand.
- Optional per-location scope. Limit a connection to specific locations of the brand, or leave it open to cover every location.
- Multiple merchant accounts. Run several connections side by side — for example one per region — each with its own brand, locations and credentials.
- Encrypted credentials. Your Converge user id and pin are stored AES-256-GCM encrypted and are never returned to the browser; only a masked merchant id is shown back.
What you need
- An Elavon Converge merchant account — its
ssl_merchant_id,ssl_user_idandssl_pin. - At least one brand set up in GetUp (the connection attaches to a brand).
- The Elavon connector enabled for your company by an administrator.
Sandbox & production
Pick Sandboxto validate against Converge's demo host first, or Live for your real merchant account. You can switch a connection between the two at any time. In a GetUp demo workspace the connection is simulated, so you can walk the whole flow without a real Elavon account.
How to connect
- Open /integrations and click Connect on the Elavon Converge card. That opens the Elavon setup page.
- Choose the environment — Sandbox to start, Live when ready.
- Pick the brand this merchant account settles for, and optionally the specific locations it covers.
- Enter your Converge merchant id, user id and pin, and an optional label to tell several accounts apart.
- Test & connect. We validate the credentials against Converge; if they're valid the connection turns on instantly and the credentials are stored encrypted.
Managing connections
From the Elavon setup page you can re-test a connection, reconfigure its brand/locations or credentials, disconnect it (clears the stored credentials but keeps the row) or delete it entirely.
Card transactions & revenue
Once a connection is live, GetUp pulls settled card transactions (sales and refunds) from Converge once a day into a per-company ledger, deduplicated by the provider transaction id so a re-run never double-counts. The GetUp AI assistant can then answer questions like "what's my card revenue this month?" or "card refunds by location" with cited, per-currency cards — it never invents a number. In a demo workspace the transactions are seeded, so the whole flow works without a real Elavon account.
Security
Credentials are validated and stored server-side only, encrypted at rest. The connector is scoped to your company: a connection can only be attached to a brand your company owns, and to locations of that brand. GetUp staff never see your Converge pin.
What's next
Settlement reconciliation and issuing refunds from GetUp back to Converge are on the roadmap. Today the connector associates the merchant account, syncs settled card transactions daily, and makes them answerable in the assistant.