Connect NMI and NMI-based processors (Banquest, SequelPay, PayArc, Interconnect, Blink)
Many card companies run on the NMI platform. Yahiv connects to all of them the same way, with two keys from your processor.
Before you start
- You are the Owner.
- Ask your processor's rep: "Is my merchant account on the NMI platform? Please send me the private security key (API key), the public tokenization key (Collect.js), and the API endpoint if it isn't the normal NMI one."
- 1
Open Payment processors
Settings → "Payment processors" → "Connect a processor" → "Any other processor".
- 2
Choose your processor
Type a name (e.g. Banquest cards). In "Processor" pick NMI, or your company's name (Banquest, SequelPay, PayArc, Interconnect or Blink). The grey line says "NMI-compatible connector".
NMI-based processors are listed under Credit card gateways. - 3
Paste the private security key
Paste it into "Private security key (API key)".
The private security key box. - 4
Paste the public tokenization key
Paste it into "Public tokenization key (Collect.js)". This one makes the secure card boxes work.
The public tokenization key box. - 5
API endpoint (only if your rep gave one)
Leave "API endpoint (leave blank for default)" empty, unless your rep gave you a different address. It must start with https://.
Leave the endpoint empty unless your rep gave you one. - 6
Connect and make default
Press "Connect", refresh, then "Make default" on the new connection and "Disable" on the test connection. Try a $1 gift and refund it.
Tips
- If your processor is not on the NMI platform, the connector won't work — Yahiv can add a direct connection from that processor's technical documents. Ask Yahiv.
- The private security key can charge cards — keep it private. Yahiv stores it encrypted and never shows it again.
- Ask your processor to turn on its card updater service, so recurring gifts survive new expiry dates.
If something isn't working
"Endpoint must be an https URL".
The endpoint you typed doesn't start with https://. Fix it, or leave it empty.
Charges fail with an authentication error.
The security key is wrong or belongs to a test account. Open "Edit credentials" and paste the live key.
Card boxes don't appear on the giving page.
The public tokenization key is missing or wrong. Paste it again under "Edit credentials".