Retrieve a single payment for the location.
- Mock serverhttps://api-docs.lobbie.com/_mock/openapi/partner/v2/account/{accountId}/location/{locationId}/payment/{paymentId}
- Productionhttps://api-prod.lobbie.com/lobbie/api/partner/v2/account/{accountId}/location/{locationId}/payment/{paymentId}
curl -i -X GET \
'https://api-docs.lobbie.com/_mock/openapi/partner/v2/account/{accountId}/location/{locationId}/payment/42' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'x-api-key: YOUR_API_KEY_HERE'Payment found
Invoice ID this payment is associated with, if any. May be null for V1 recurring/subscription payments not tied to a single invoice — in that case it is backfilled from the recurring payment's originating invoice when one exists, and subscriptionId provides the correlation key otherwise.
Location ID for invoice lookups. Resolved from the associated invoice when present, otherwise from the recurring payment (subscription) this payment belongs to. May be null only for legacy V1 payments with neither association.
Patient ID. May be null for legacy payments where a patient association is not resolvable.
Recurring payment (subscription) ID this payment belongs to, if any. For V2 this is the invoice's subscription ID; for V1 this is the recurring payment ID. Populated when the payment is part of a recurring schedule.
{ "amount": { "amount": 50, "currency": "USD" }, "id": 1234, "invoiceId": 1234, "locationId": 55, "patientId": 1234, "paymentAttemptId": 1234, "postedOn": "2025-01-15T14:00:00Z", "purchaseOrderId": 1234, "subscriptionId": 555, "surchargeAmount": { "amount": 50, "currency": "USD" }, "surchargeRate": 0.025 }