Managing acquirer connections

Once boarded, an acquirer connection is a regular resource keyed by its derived id <merchant-id>-ACQ-<ACQUIRER-CODE> (e.g. 042-ACQ-NAB). The id isn't stored — it's assembled from the merchant id and the acquirer code, so you can build it yourself if you already know both.

List connections for a merchant

curl https://gateway.pmnts.io/v2/partners/merchants/acme-coffee/acquirers \
  -u "$PARTNER_USERNAME:$PARTNER_TOKEN"

Read one connection

curl https://gateway.pmnts.io/v2/partners/merchants/acme-coffee/acquirers/042-ACQ-NAB \
  -u "$PARTNER_USERNAME:$PARTNER_TOKEN"

Update editable fields

curl -X PATCH https://gateway.pmnts.io/v2/partners/merchants/acme-coffee/acquirers/042-ACQ-NAB \
  -u "$PARTNER_USERNAME:$PARTNER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "mid": "9876543210" }'

Typical edits: MID/TID swap, settlement account changes. The full list of editable fields is in the API reference.

Enable / disable

Toggle without re-boarding:

# Stop processing through this connection
curl -X POST https://gateway.pmnts.io/v2/partners/merchants/acme-coffee/acquirers/042-ACQ-NAB/disable \
  -u "$PARTNER_USERNAME:$PARTNER_TOKEN"

# Turn it back on
curl -X POST https://gateway.pmnts.io/v2/partners/merchants/acme-coffee/acquirers/042-ACQ-NAB/enable \
  -u "$PARTNER_USERNAME:$PARTNER_TOKEN"

Disabling stops new transactions immediately. In-flight settlements are unaffected.