Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.swippee.com/llms.txt

Use this file to discover all available pages before exploring further.

Turn raw Fonepay terminal PANs and merchant-name strings into clean merchant data — name, MCC, spend category, and city — so you can enrich your own transaction feed with the same directory that powers Swippee’s parsing. Requires a Bearer key (FULL scope); bills 1 unit per call (batch up to 1000 lookups).

​
Resolve a batch

curl -X POST https://api.swippee.com/v1/merchants/resolve \
  -H "Authorization: Bearer $SWIPPEE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "terminals": ["2222000000000000"], "names": ["Example Cafe"] }'

{
  "data": {
    "count": 2,
    "matched": 2,
    "results": [
      {
        "input": "2222000000000000",
        "type": "terminal",
        "matched": true,
        "merchant": "Example Cafe",
        "mcc": "5814",
        "category": "dining",
        "city": "Kathmandu",
        "terminal": "2222000000000000"
      }
    ]
  },
  "meta": { "source": "Swippee Fonepay merchant directory" }
}

​
Single terminal lookup

curl https://api.swippee.com/v1/merchants/2222000000000000 \
  -H "Authorization: Bearer $SWIPPEE_API_KEY"
Name input is matched against the directory after normalization — so “Example Sweets PLTD” and “Example Sweets P LTD” resolve to the same merchant. Unmatched inputs come back with matched: false and null fields.