Credentials
| Field | Where to find it |
|---|---|
| Account ID | Your Converge merchant account ID. |
| API user ID | A user created for API use on your eCommerce terminal. |
| PIN | That user’s terminal PIN. |
Converge has separate demo and production systems; a sandbox gateway uses the demo system. Test connection runs a transaction search for the last day, which moves no money.
IP allow-list
Converge terminals usually only accept API calls from listed addresses. Ask OrderCard support for the vault’s outgoing addresses and add them to your terminal’s allow-list, or the connection test will fail.
Operations
| OrderCard | Converge |
|---|---|
| Purchase | ccsale |
| Authorize | ccauthonly |
| Capture | cccomplete |
| Void | ccdelete for an authorization, ccvoid for a sale before the batch settles |
| Refund | ccreturn |
| Verify | ccverify |
Merchant-initiated and recurring charges send the credential-on-file indicators and the original approval’s data, which Converge requires for stored cards.
Surcharging
Converge terminals that surcharge add the fee themselves. Turn on surcharging for the gateway in OrderCard and enter the terminal’s rate, so quotes match. When a card is charged, OrderCard first asks Converge whether and how much it will surcharge, then sends the amount before surcharge and records the surcharge Converge reports. If Converge surcharges at a different rate than you entered, OrderCard updates the gateway’s rate to match.
3-D Secure
A 3-D Secure result sent with a charge goes in Converge’s ssl_3dsecure_value, ssl_eci_ind, ssl_3ds_message_version, ssl_program_protocol, ssl_3ds_trans_status and ssl_dir_server_tran_id fields. A 3-D Secure 1 result also sends ssl_xid. Converge reads the outcome from ssl_eci_ind, which OrderCard sets to 5 for status Y and 6 for A.
Elavon accepts these only on terminals with 3-D Secure 2 turned on, set to the internet market segment, in the US or Canada.