> ## Documentation Index > Fetch the complete documentation index at: https://voucherify-rc-lv2-guides.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # List member order payments > Lists persisted order transactions (pay-with-points payments) for the given program member, with cursor-based pagination. Supports filtering by transaction `id` and `created_at` date. Dry-run (`SIMULATED`) results from create are never persisted and do not appear in this list. ## OpenAPI ````yaml /openapi/loyalties-v2.json get /v2/loyalties/programs/{programId}/members/{memberId}/orders/payments openapi: 3.1.0 info: title: Voucherify Loyalty v2 API version: 2.0.0 description: >- Complete OpenAPI specification for the Voucherify Loyalty v2 API. All endpoints require the LOYALTY_V2 feature flag. Combined from per-domain specs: programs.yaml, members.yaml, program-operations.yaml, card-definitions.yaml, earning-rules.yaml, tier-structures.yaml, benefits.yaml, rewards.yaml, examine.yaml servers: - url: '{protocol}://{host}' variables: protocol: default: https enum: - https - http host: default: api.voucherify.io security: - X-App-Id: [] X-App-Token: [] - bearerAuth: [] tags: - name: Programs description: >- Loyalty program CRUD, lifecycle management, program-scoped resource assignments (card definitions, earning rules, rewards, tier structures), member management (create, list, get, activate, deactivate, delete), membership retrieval (member + program + cards with tier progress, by customer ID, customer source ID, or member ID), card operations (points adjustment, pending points, expiring points, transactions), reward purchases, and activity history. - name: Card Definitions description: >- CRUD operations, lifecycle management, and activity history for card definitions. Card definitions describe the configuration for loyalty cards, including code generation, points expiration, earning/spending limits, pending points, refunds, and balance settings. - name: Earning Rules description: >- Manage earning rules that define how customers earn points or receive incentives based on triggers (events, segments, custom events). Includes CRUD, lifecycle, and activity history. - name: Tier Structures description: >- CRUD operations, lifecycle management, and activity history for tier structures. Includes nested tier definitions (create, list, update, delete) within tier structures. Tier structures define the tiering model for loyalty programs — how members qualify for and move between tiers. - name: Benefits description: >- Manage benefit definitions (fixed points, proportional points, material, digital). Includes CRUD, lifecycle transitions, and activity history. - name: Rewards description: >- CRUD, lifecycle operations, and activity history for reward definitions. Rewards can be material (product/SKU) or digital (discount coupons, gift vouchers). - name: Examine description: >- Evaluation endpoints that estimate earning opportunities and reward availability for a customer across their loyalty program memberships, without side effects. paths: /v2/loyalties/programs/{programId}/members/{memberId}/orders/payments: parameters: - name: programId in: path required: true description: >- Identifies the loyalty program (`lprg_` followed by hexadecimal characters). schema: type: string pattern: ^lprg_[a-f0-9]+$ - name: memberId in: path required: true description: Identifies the program member (`lmbr_[a-f0-9]+`). schema: type: string pattern: ^lmbr_[a-f0-9]+$ get: tags: - Programs summary: List member order payments description: >- Lists persisted order transactions (pay-with-points payments) for the given program member, with cursor-based pagination. Supports filtering by transaction `id` and `created_at` date. Dry-run (`SIMULATED`) results from create are never persisted and do not appear in this list. operationId: listMemberOrderPayments parameters: - name: limit in: query required: false description: >- Maximum number of items to return. An integer between 1 and 100; numeric strings are also accepted. Defaults to 10. schema: type: - integer - 'null' minimum: 1 maximum: 100 default: 10 - name: order in: query required: false description: >- Sorts results by a field name, optionally prefixed with `-` for descending order. May be provided multiple times (array). The same field cannot be used in both ascending and descending order at once. Default: `-created_at`. schema: oneOf: - type: array items: type: string enum: - '-created_at' - created_at - type: string enum: - '-created_at' - created_at - type: 'null' - name: cursor in: query required: false description: >- Pagination cursor returned in the `cursor.next` field of a previous response (format: `lcrsotx_` followed by hexadecimal characters). schema: type: - string - 'null' pattern: ^lcrsotx_[a-f0-9]+$ - name: filters in: query required: false style: deepObject explode: true description: >- Filters results by field, e.g. `filters[id][conditions][$is]=lotx_...`. Each field accepts a `conditions` object with condition operators. schema: $ref: '#/components/schemas/OrderPaymentListFilters' responses: '200': description: Returns a paginated list of persisted order payment transactions. content: application/json: schema: $ref: '#/components/schemas/OrderPaymentListResponse' examples: Member pay-with-points transactions: value: data: - id: lotx_12b8dbf787c67de367 program_id: lprg_128f58429f4c4bf7b2 member_id: lmbr_128f962dbc8c4ba5dc card_id: lcrd_128f962dbd8c4ba5e1 card_definition_id: lcdef_128f4a88414c4bed69 card_transaction_id: lctx_12b8dbf787c67de366 order_id: ord_12b4cdf5f30c158825 status: APPROVED type: PAY_WITH_POINTS details: reason: Points spent on order payment rejection: null metadata: points_limit: 150 payment: id: ordpay_12b8dbf8d6939c4cd3 amount: 100 points_spent: 100 exchange_ratio: 1 created_at: '2026-07-13T17:22:19.296Z' updated_at: '2026-07-13T17:22:20.630Z' object: order_transaction - id: lotx_12b8d2573e96b6af3b program_id: lprg_128f58429f4c4bf7b2 member_id: lmbr_128f962dbc8c4ba5dc card_id: lcrd_128f962dbd8c4ba5e1 card_definition_id: lcdef_128f4a88414c4bed69 card_transaction_id: lctx_12b8d2573e96b6af3a order_id: ord_12b4cdf5f30c158825 status: APPROVED type: PAY_WITH_POINTS details: reason: Points spent on order payment rejection: null metadata: points_limit: 100 payment: id: ordpay_12b8d25896d39c45e0 amount: 100 points_spent: 100 exchange_ratio: 1 created_at: '2026-07-13T16:40:15.866Z' updated_at: '2026-07-13T16:40:17.237Z' object: order_transaction - id: lotx_12b8d23e9016b6af18 program_id: lprg_128f58429f4c4bf7b2 member_id: lmbr_128f962dbc8c4ba5dc card_id: lcrd_128f962dbd8c4ba5e1 card_definition_id: lcdef_128f4a88414c4bed69 card_transaction_id: lctx_12b8d23e9016b6af17 order_id: ord_12b4cdf5f30c158825 status: REJECTED type: PAY_WITH_POINTS details: reason: Points spent on order payment rejection: reason: PAYMENT_EXCEEDS_ORDER_TOTAL_AMOUNT metadata: amount_limit: 2000 payment: amount: 2000 points_spent: 2000 exchange_ratio: 1 created_at: '2026-07-13T16:39:50.592Z' updated_at: '2026-07-13T16:39:52.240Z' object: order_transaction cursor: next: lcrsotx_12cbca76e282083066 expires_at: '2026-07-28T10:26:59.530Z' object: list '400': description: >- Validation error — query parameters failed validation, or the operation is not allowed in the current resource state. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Program or member not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: Member not found: value: code: 404 key: not_found message: Resource not found details: Cannot find member with id lmbr_128962dbc8c4ba5dc request_id: v-12cbd13b05da398de1 resource_id: lmbr_128962dbc8c4ba5dc resource_type: member Program not found: value: code: 404 key: not_found message: Resource not found details: Cannot find program with id lprg_128f8429f4c4bf7b2 request_id: v-12cbd12127da398dac resource_id: lprg_128f8429f4c4bf7b2 resource_type: program '500': description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: OrderPaymentListFilters: type: object description: Filters for listing order payments. properties: junction: description: Joins field filters with `AND` or `OR`. Defaults to `AND`. oneOf: - type: string enum: - AND - OR - type: 'null' id: description: Filter by order transaction id. oneOf: - $ref: '#/components/schemas/OrderPaymentFilterIdConditions' - type: 'null' created_at: description: Filter by creation date. oneOf: - $ref: '#/components/schemas/OrderPaymentFilterDateConditions' - type: 'null' additionalProperties: false OrderPaymentListResponse: type: object properties: data: type: array description: Order payment transactions. items: $ref: '#/components/schemas/OrderPaymentTransaction' cursor: description: Pagination cursor. `null` when there are no more results. oneOf: - type: object properties: next: type: string description: >- Pass as the `cursor` query parameter to fetch the next page (format `lcrsotx_...`). expires_at: type: string format: date-time description: Timestamp when the cursor expires (ISO 8601). - type: 'null' object: type: string const: list description: Object type marker. Always `list`. ErrorResponse: type: object description: Standard error response returned by all Loyalty v2 endpoints. properties: code: type: integer description: HTTP status code of the error. key: type: string description: Machine-readable error key. message: type: string description: Human-readable error message. details: type: string description: Additional details about the error. request_id: type: string description: Unique identifier of the request that produced the error. resource_id: type: string description: Unique identifier of the resource that produced the error. resource_type: type: string description: Type of the resource that produced the error. OrderPaymentFilterIdConditions: type: object description: >- ID filter conditions for order transaction ids. Values must match pattern `^lotx_[a-f0-9]+$`. `$is`/`$is_not` accept a single value (string or 1-element array); `$in`/`$not_in` accept a string or an array of 1-100 values. properties: conditions: type: object minProperties: 1 additionalProperties: false properties: $is: description: Matches transactions whose id equals the given value. oneOf: - type: string pattern: ^lotx_[a-f0-9]+$ - type: array items: type: string pattern: ^lotx_[a-f0-9]+$ minItems: 1 maxItems: 1 - type: 'null' $is_not: description: Matches transactions whose id does not equal the given value. oneOf: - type: string pattern: ^lotx_[a-f0-9]+$ - type: array items: type: string pattern: ^lotx_[a-f0-9]+$ minItems: 1 maxItems: 1 - type: 'null' $in: description: Matches transactions whose id is one of the given values. oneOf: - type: string pattern: ^lotx_[a-f0-9]+$ - type: array items: type: string pattern: ^lotx_[a-f0-9]+$ minItems: 1 maxItems: 100 - type: 'null' $not_in: description: Matches transactions whose id is not one of the given values. oneOf: - type: string pattern: ^lotx_[a-f0-9]+$ - type: array items: type: string pattern: ^lotx_[a-f0-9]+$ minItems: 1 maxItems: 100 - type: 'null' required: - conditions additionalProperties: false OrderPaymentFilterDateConditions: type: object description: >- Date filter conditions. `$before`/`$after` accept an ISO date-time string. `$is`/`$more_than`/`$less_than` accept a non-negative integer number of days ago. `$has_value`/`$is_unknown` accept any single value and match rows where the field is set / not set. Single values may also be passed as 1-element arrays. properties: conditions: type: object minProperties: 1 additionalProperties: false properties: $before: description: Matches rows with the date before the given date-time. oneOf: - type: string - type: array items: type: string minItems: 1 maxItems: 1 - type: 'null' $after: description: Matches rows with the date after the given date-time. oneOf: - type: string - type: array items: type: string minItems: 1 maxItems: 1 - type: 'null' $is: description: Matches rows with the date exactly the given number of days ago. oneOf: - type: string - type: array items: type: string minItems: 1 maxItems: 1 - type: 'null' $more_than: description: >- Matches rows with the date more than the given number of days ago. oneOf: - type: string - type: array items: type: string minItems: 1 maxItems: 1 - type: 'null' $less_than: description: >- Matches rows with the date less than the given number of days ago. oneOf: - type: string - type: array items: type: string minItems: 1 maxItems: 1 - type: 'null' $has_value: description: Matches rows where the date field is set. oneOf: - type: string - type: array maxItems: 1 - type: 'null' $is_unknown: description: Matches rows where the date field is not set. oneOf: - type: string - type: array maxItems: 1 - type: 'null' required: - conditions additionalProperties: false OrderPaymentTransaction: type: object description: >- An order transaction representing a pay-with-points payment. List endpoints return only persisted transactions; `SIMULATED` appears only on dry-run create responses. properties: id: type: string description: >- Identifies the order transaction (`lotx_...`). Absent on dry-run (`SIMULATED`) create responses, which are never persisted. Always present in list responses. program_id: type: string description: Unique identifier of the loyalty program (format `lprg_...`). member_id: type: string description: Unique identifier of the program member (format `lmbr_...`). card_id: type: string description: >- Unique identifier of the loyalty card the points were spent from (format `lcrd_...`). card_definition_id: type: string description: Unique identifier of the card definition (format `lcdef_...`). card_transaction_id: type: - string - 'null' description: >- Unique identifier of the underlying card transaction (format `lctx_...`). `null` for DRY_RUN (SIMULATED) transactions. order_id: type: string description: Unique identifier of the paid order (format `ord_...`). status: type: string enum: - PENDING - PROCESSING - APPROVED - REJECTED - SIMULATED description: >- Transaction status. `PENDING` — created, awaiting processing; `PROCESSING` — being processed; `APPROVED` — completed successfully; `REJECTED` — rejected (see `details.rejection`); `SIMULATED` — dry-run create result, not persisted (not returned by list). type: type: string enum: - PAY_WITH_POINTS description: Defines the transaction type. Always `PAY_WITH_POINTS`. details: description: Transaction details for the `PAY_WITH_POINTS` type. oneOf: - $ref: '#/components/schemas/OrderPaymentTransactionDetails' - type: 'null' created_at: type: string format: date-time description: Timestamp when the transaction was created (ISO 8601). updated_at: type: - string - 'null' format: date-time description: >- Timestamp when the transaction was last updated (ISO 8601), or `null`. object: type: string const: order_transaction description: Object type marker. Always `order_transaction`. OrderPaymentTransactionDetails: type: object description: Details of a `PAY_WITH_POINTS` order transaction. properties: reason: type: string description: 'Human-readable reason: "Points spent on order payment".' rejection: description: Rejection details, present when the transaction was rejected. oneOf: - $ref: '#/components/schemas/OrderPaymentRejection' - type: 'null' metadata: type: object description: >- Transaction metadata. For pay-with-points transactions this contains the flattened payment limits used for the calculation: `amount_limit` and/or `points_limit` (omitted when the default `CARD_BALANCE` limit was used). Empty object when not set. properties: amount_limit: type: integer description: Maximum amount limit applied to the payment (if any). points_limit: type: integer description: Maximum points limit applied to the payment (if any). additionalProperties: true payment: $ref: '#/components/schemas/OrderPaymentPaymentDetails' OrderPaymentRejection: type: object description: Rejection details for a rejected order payment transaction. properties: reason: type: string description: >- Machine-readable rejection reason. Order-side: `ORDER_NOT_FOUND`, `PAYMENT_EXCEEDS_ORDER_TOTAL_AMOUNT`. Card-side (when the linked card transaction fails first): `NOT_ENOUGH_BALANCE`, `GLOBAL_SPENDING_LIMIT_EXCEEDED`, `TRANSACTION_SPENDING_LIMIT_EXCEEDED`. details: description: >- Structured rejection context. Omitted when the reason carries no extra data (`ORDER_NOT_FOUND`, `PAYMENT_EXCEEDS_ORDER_TOTAL_AMOUNT`, `NOT_ENOUGH_BALANCE`). For `GLOBAL_SPENDING_LIMIT_EXCEEDED`: `type`, `limit`, `spendings`. For `TRANSACTION_SPENDING_LIMIT_EXCEEDED`: `type`, `limit`. oneOf: - type: object additionalProperties: true properties: type: type: string description: Spending cap type that was exceeded. limit: type: number description: Configured spending limit. spendings: type: number description: >- Projected total spendings that exceeded the limit. Present for `GLOBAL_SPENDING_LIMIT_EXCEEDED`. - type: 'null' OrderPaymentPaymentDetails: type: object description: Payment calculation details. properties: id: type: string description: Payment identifier. Omitted when not set. amount: type: number description: Amount of the order paid with points. points_spent: type: number description: Number of points spent on the payment. exchange_ratio: type: number description: >- Points-to-amount exchange ratio evaluated from the card definition's pay-with-points formula. securitySchemes: X-App-Id: type: apiKey name: X-App-Id in: header X-App-Token: type: apiKey name: X-App-Token in: header bearerAuth: type: http scheme: bearer bearerFormat: JWT ````