PayFacto API - v2.0 - GET /verifications/{verificationId}

Retrieves a previously created card verification by its unique identifier.

Prerequisites

🔑

Authentication — HTTP Basic Auth

All v2.0 endpoints use HTTP Basic Authentication. Set Authorization: Basic base64(username:password). Contact PayFacto for credentials.

🌐

Environment Base URLs

UAT: https://uat.ca.api.payfacto.cloud/payments/v1 | Production: https://ca.api.payfacto.cloud/payments/v1

📋

Content-Type

All request bodies require Content-Type: application/json.

🔄

Idempotency

Include Idempotency-Key header (max 64 chars) on POST requests. 200 = duplicate; 201 = newly created.

💵

Amounts

All monetary amounts are positive integers in cents. $12.99 = 1299.

Request

GET https://uat.ca.api.payfacto.cloud/payments/v1/verifications/{verificationId}

Path parameter

Parameter	Type	Description
verificationId	string (UUID) · required	Unique verification identifier.

Request — Code Example

cURL

curl -X GET "https://uat.ca.api.payfacto.cloud/payments/v1/verifications/a1822999-099d-4fb1-a354-77be553a5b22" \
  -H "Authorization: Basic YOUR_BASE64_CREDENTIALS"

Response

Response fields (verification object)

Field	Type	Description
id	string (UUID)	Unique verification identifier.
billingDetail	object	Billing address used for AVS.
card	object	Card details: `brand`, `lastFour`, `expiry`.
cardValidation	object	Validation results: `addressLine1Result`, `postalCodeResult`, `avsResultCode`, `cvvResult`.
metadata	object	Key-value pairs.
result	object	Auth result including `authCode`.
status	string	SUCCEEDED or FAILED.
terminal	object	Terminal details if applicable.
transactionTime	string (ISO 8601)	UTC timestamp.
error	object	Error object on failure.

Response — Code Examples

JSON — 200 Success

{
  "id": "a1822999-099d-4fb1-a354-77be553a5b22",
  "card": { "brand": "VISA", "lastFour": "1111", "expiry": { "month": "05", "year": "2039" } },
  "cardValidation": {
    "addressLine1Result": "PASS",
    "postalCodeResult": "PASS",
    "avsResultCode": "M",
    "cvvResult": "PASS"
  },
  "result": { "authCode": "012345" },
  "status": "SUCCEEDED",
  "transactionTime": "2024-05-15T14:30:01Z"
}

JSON — 404 Not Found

{
  "error": { "code": "NOT_FOUND", "type": "INVALID_REQUEST_ERROR", "details": ["Verification not found"], "message": "Not Found" }
}

Error / HTTP Status Codes

HTTP Status	Meaning	Recommended Action
200	OK — Previously created (same idempotency key)	Check `status` field in response body
201	Created — New resource created	Store the `id` for future operations
400	Bad Request — Invalid payload	Check `error.details` and `error.invalidFields`
402	Payment Required — Issuer declined	Check `result.declineCode` — do not retry automatically
404	Not Found	Verify the ID in the request path
422	Unprocessable — Invalid state	Check `error.message`
500	Internal Server Error	Retry with backoff; contact PayFacto Support if persistent