openapi: 3.2.0 info: contact: name: API Support email: support@getpliant.com url: https://www.getpliant.com title: Pliant Customer Payments API description: Pliant Customer API version: 2.1.0 license: name: MIT url: https://opensource.org/license/MIT servers: - url: https://partner-api.getpliant.com/api description: Pliant Production Server - url: https://sandbox.partner-api.getpliant.com/api description: Pliant Sandbox Server - url: https://pci-api.getpliant.com description: PCI Vault Production Server - url: https://pci-sandbox.partner-api.getpliant.com description: PCI Vault Sandbox Server security: - bearerAuth: [] tags: - name: Payments description: This tag is for operations related to payments paths: /payments: get: summary: List of Payments description: Returns a list of payments with metadata. Payments happen according to the payment frequency of the organization. They include and consider all relevant transactions and other payments during the specified period. You can use the `limit`, `page`, `sortBy` and `sortDirection` parameters to filter and sort the results. tags: - Payments operationId: get-payments parameters: - name: organizationId in: query description: The ID of the organization to get the payments for. required: true schema: type: string format: uuid - name: cardAccountId in: query description: The ID of the [card account](/docs/card-account) to get the payments for. Payments keep the card account id they were booked on. If a card account was superseded, filtering by the superseded id returns the payments booked before the switch and filtering by its successor (`supersededBy`) returns the ones booked after. Query both ids to get a complete list across the switch. schema: type: string format: uuid - name: type in: query description: The type of the payments to filter by. schema: type: string enum: - BILL - TOPUP - DIRECT_DEBIT_REVERSAL - PAYOUT - PAY_IN - name: status in: query description: The status of the payments to filter by. schema: type: string enum: - PLANNED - UPCOMING - DEFERRED - READY_FOR_PMT - PENDING - PAID - FAILED - DISCARDED - BOOKED - REVERSED - name: fromDate in: query description: The date from which to return payments, zero-offset UTC time. The date boundary is inclusive. Meaning we compare with `>=`. schema: type: - string - 'null' format: date-time example: '2021-01-30T08:30:00Z' - name: toDate in: query description: The date until which to return payments, zero-offset UTC time. The date boundary is inclusive. Meaning we compare with `<=`. schema: type: - string - 'null' format: date-time example: '2021-01-30T08:30:00Z' - name: byDateField in: query description: Desired date field to be filtered by if `fromDate` or `toDate` present. schema: type: - string - 'null' enum: - cutoffDate - collectionDate - paymentDate - updatedAt - createdAt default: createdAt - name: limit in: query description: The maximum number of items to return per page. The default value if not provided is 100, the maximum allowed value is 1000. schema: type: integer - name: page in: query description: The page number to return, starting with 0, this counts up to the total number of pages. The total number of pages is determined by the total number of records divided by the limit. schema: type: integer - name: sortBy in: query description: The field to sort by. schema: type: string enum: - organizationId - status - type - cutoffDate - collectionDate - paymentDate - createdAt - name: sortDirection in: query description: The direction to sort by. schema: type: string enum: - ASC - DESC responses: '200': description: Ok content: application/json: schema: type: object properties: data: type: array items: type: object properties: paymentId: type: string format: uuid description: The unique identifier of the payment. organizationId: type: string format: uuid description: The unique identifier of the organization. cardAccountId: type: string format: uuid description: The unique identifier of the [card account](/docs/card-account). publicPaymentId: type: - string - 'null' description: The public payment reference used for reconciliation. This value can be `null` at payout creation and is populated after payment file generation. Use payout callbacks to receive the populated value. type: type: string description: '* `BILL` - Bill that is being deducted from the account after transactions have been processed * `TOPUP` - Top-up that is being transferred onto the account before transactions are initiated * `DIRECT_DEBIT_REVERSAL` - Organization is charged with a fee because direct debit was not successful multiple times * `BILL_PAYMENT_REVERSAL` - Organization is charged with a fee because bill payment was not successful multiple times * `PAYOUT` - Money transferred from Pliant to an external bank account (only for pre-funded organizations) out of Pliant * `PAY_IN` - Inbound transfer credited from a third-party sender, i.e. an account holder different from the receiving customer * `OTHER` ' enum: - BILL - TOPUP - DIRECT_DEBIT_REVERSAL - BILL_PAYMENT_REVERSAL - PAYOUT - PAY_IN - OTHER method: type: string description: '* `DIRECT_DEBIT` - prefix indicates that money was send to Pliant platform via direct debit * `WIRE_TRANSFER` - prefix indicates that money has been sent to Pliant platform via wire transfer (SEPA credit transfer) ' enum: - DIRECT_DEBIT_CORE - DIRECT_DEBIT_B2B - WIRE_TRANSFER amount: type: object description: The amount of the payment. properties: value: type: number description: The value of the monetary amount, converted to minor units of the currency. For instance 1.00 EUR is 100 cents, thus the value here is `100`. See our [guides](/docs/monetary-values) for more details about how to handle monetary amounts. currency: type: string description: The currency of the monetary amount in ISO 4217 format, for example `EUR` for Euro or `USD` for US Dollar. status: type: string description: The status of the payment. enum: - PLANNED - UPCOMING - DEFERRED - READY_FOR_PMT - PENDING - PAID - FAILED - DISCARDED - BOOKED - REVERSED hasNextPage: type: boolean description: Indicates whether there is a next page available. '400': $ref: '#/paths/~1cards/get/responses/400' '401': $ref: '#/paths/~1cards/get/responses/401' '403': $ref: '#/paths/~1cards/get/responses/403' '429': $ref: '#/paths/~1cards/get/responses/429' '500': $ref: '#/paths/~1cards/get/responses/500' /payments/subscription: post: summary: 'Callback: Add/Update' description: Subscribe to callbacks for this entity or change an existing callback. tags: - Payments operationId: create-payment-subscription requestBody: required: true content: application/json: schema: type: object properties: callbackUrl: type: string format: uri example: https://myserver.com/send/callback/here description: The URL to send the callback to. Must be a valid and reachable URL. We do some basic validation to ensure the URL is syntactically correct and reachable for Pliant. Only HTTPS URLs are supported. eventTypes: type: array description: The event types to subscribe to. items: type: string enum: - PAYMENT_STATUS_CHANGED - PAYMENT_READY - PAYOUT_COMPLETED - PAYOUT_FAILED - PAYOUT_DISCARDED required: - callbackUrl - eventTypes responses: '201': description: Created '401': description: Unauthorized '403': description: Forbidden '500': description: Internal Server Error callbacks: paymentUpdated: '{$request.body#/callbackUrl}': post: parameters: - in: header name: X-Organization-Id schema: type: string format: uuid description: 'Referencing the organization this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.' - in: header name: X-Partner-Organization-Id schema: type: string description: 'Filled, if the value `partnerOrganizationId` is [set](/reference/update-organization) by the partner on the organization itself. Referencing the organization identifier of the partner. Example value: `abc123`.' - in: header name: X-Payment-Program-Id schema: type: string format: uuid description: 'Referencing the payment program this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.' - in: header name: X-Callback-Id schema: type: string format: uuid description: 'A unique identifier for this callback. Can be used to deduplicate callbacks to achieve idempotent behavior. See [guides](/docs/callbacks) for more details. Example value: `12a03093-eaad-4ae5-9d8d-42e7f6f8b7c6`.' - in: header name: X-Callback-Created-At schema: type: string format: date-time description: 'The date and time when the callback was created. Can be used to reorder callbacks. See [guides](/docs/callbacks) for more details. Example value: `2024-03-15T15:55:58.623375258Z`.' requestBody: content: application/json: schema: allOf: - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardUpdated/{$request.body#~1callbackUrl}/post/requestBody/content/application~1json/schema/allOf/0' - type: object properties: paymentId: type: string format: uuid publicPaymentId: type: - string - 'null' description: The public payment reference used for reconciliation. This value can be `null` at payout creation and is populated after payment file generation. organizationId: type: string format: uuid cardAccountId: type: string format: uuid description: The card account to which this payment belongs to. status: type: string enum: - PLANNED - UPCOMING - DEFERRED - READY_FOR_PMT - PENDING - PAID - FAILED - DISCARDED - BOOKED - REVERSED responses: '200': description: We expect the partner to return a HTTP 200 status code if the callback was successfully received. On 4xx and 5xx status codes, we will [retry](/docs/callbacks#retries) the callback. paymentReady: '{$request.body#/callbackUrl}': post: parameters: - in: header name: X-Organization-Id schema: type: string format: uuid description: 'Referencing the organization this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.' - in: header name: X-Partner-Organization-Id schema: type: string description: 'Filled, if the value `partnerOrganizationId` is [set](/reference/update-organization) by the partner on the organization itself. Referencing the organization identifier of the partner. Example value: `abc123`.' - in: header name: X-Payment-Program-Id schema: type: string format: uuid description: 'Referencing the payment program this callback was sent for. See [guides](/docs/callbacks) for more details. Example value: `54e6e7e7-0c23-4a54-bccb-2d3ff2fd02df`.' - in: header name: X-Callback-Id schema: type: string format: uuid description: 'A unique identifier for this callback. Can be used to deduplicate callbacks to achieve idempotent behavior. See [guides](/docs/callbacks) for more details. Example value: `12a03093-eaad-4ae5-9d8d-42e7f6f8b7c6`.' - in: header name: X-Callback-Created-At schema: type: string format: date-time description: 'The date and time when the callback was created. Can be used to reorder callbacks. See [guides](/docs/callbacks) for more details. Example value: `2024-03-15T15:55:58.623375258Z`.' requestBody: content: application/json: schema: allOf: - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardUpdated/{$request.body#~1callbackUrl}/post/requestBody/content/application~1json/schema/allOf/0' - type: object properties: paymentId: type: string format: uuid description: The unique identifier of the payment. organizationid: type: string format: uuid description: The unique identifier of the organization. cardAccountId: type: string format: uuid description: The unique identifier of the card account. type: type: string description: '`BILL` - Bill that is being deducted from the account after transactions have been processed `TOPUP` - Top-up that is being transferred onto the account before transactions are initiated `DIRECT_DEBIT_REVERSAL` - Organization is charged with a fee because direct debit was not successful multiple times `BILL_PAYMENT_REVERSAL` - Organization is charged with a fee because bill payment was not successful multiple times `PAYOUT` - Money transferred from Pliant to an external bank account (only for pre-funded organizations) out of Pliant `PAY_IN` - Inbound transfer credited from a third-party sender, i.e. an account holder different from the receiving customer `OTHER` ' enum: - BILL - TOPUP - DIRECT_DEBIT_REVERSAL - BILL_PAYMENT_REVERSAL - PAYOUT - PAY_IN - OTHER method: type: string description: '`DIRECT_DEBIT_CORE`: Indicates that money was send to Pliant platform via core direct debit. `DIRECT_DEBIT_B2B`: Indicates that money was send to Pliant platform via B2B direct debit. `WIRE_TRANSFER`: Indicates that money has been sent to Pliant platform via wire transfer (SEPA credit transfer). ' enum: - DIRECT_DEBIT_CORE - DIRECT_DEBIT_B2B - WIRE_TRANSFER status: type: string description: The status of the payment. The initial payment status is `UPCOMING` for bills. It is different for other types of payments, see [our guides](/docs/payment-entity) for details. After midnight of the `cutoffDate` it changes to `READY_FOR_PMT`. This can be different under certain circumstances regarding the organizations payment terms, see `paymentDefermentInDays`. The day after the `cutoffDay`, around 15:00 German time, the payment is checked and submitted. The status then changes to `PENDING`. After midnight of the `plannedPaymentDate`, the payment status changes to `PAID`. enum: - PLANNED - UPCOMING - DEFERRED - READY_FOR_PMT - PENDING - PAID - FAILED - DISCARDED - BOOKED - REVERSED amount: type: object description: The amount of the payment. properties: value: type: number description: The value of the monetary amount, converted to minor units of the currency. For instance 1.00 EUR is 100 cents, thus the value here is `100`. See our [guides](/docs/monetary-values) for more details about how to handle monetary amounts. currency: type: string description: The currency of the monetary amount in ISO 4217 format, for example `EUR` for Euro or `USD` for US Dollar. relatedTransactions: type: array description: The related transactions of this payment. This array lists all transactions that contribute to the total amount of this payment. The array remains unchanged, with new transactions added daily to the payment at 09:00 German time. items: type: string format: uuid responses: '200': description: We expect the partner to return a HTTP 200 status code if the callback was successfully received. On 4xx and 5xx status codes, we will [retry](/docs/callbacks#retries) the callback. payoutStatusChanged: '{$request.body#/callbackUrl}': post: description: Sent when a payout reaches a terminal status. Covers `PAYOUT_COMPLETED`, `PAYOUT_FAILED`, and `PAYOUT_DISCARDED` events. Uses the same payload as `PAYMENT_STATUS_CHANGED`. parameters: - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardReassigned/{$request.body#~1callbackUrl}/post/parameters/0' - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardReassigned/{$request.body#~1callbackUrl}/post/parameters/1' - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardReassigned/{$request.body#~1callbackUrl}/post/parameters/2' - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardReassigned/{$request.body#~1callbackUrl}/post/parameters/3' - $ref: '#/paths/~1cards~1subscription/post/callbacks/cardReassigned/{$request.body#~1callbackUrl}/post/parameters/4' requestBody: $ref: '#/paths/~1payments~1subscription/post/callbacks/paymentUpdated/{$request.body#~1callbackUrl}/post/requestBody' responses: '200': description: We expect the partner to return a HTTP 200 status code if the callback was successfully received. On 4xx and 5xx status codes, we will [retry](/docs/callbacks#retries) the callback. delete: summary: 'Callback: Remove' description: Remove a callback subscription for this entity. tags: - Payments operationId: remove-payment-subscription requestBody: required: true content: application/json: schema: type: object properties: eventTypes: type: array description: The event types to unsubscribe from. items: type: string enum: - PAYMENT_STATUS_CHANGED - PAYMENT_READY - PAYOUT_COMPLETED - PAYOUT_FAILED - PAYOUT_DISCARDED required: - eventTypes responses: '200': description: Ok /payments/{paymentId}: get: summary: Payment Details description: Returns a single payment by its ID. tags: - Payments operationId: get-payments-detail parameters: - name: paymentId in: path required: true description: The unique identifier of the payment. schema: type: string format: uuid responses: '200': description: Ok content: application/json: schema: type: object properties: paymentId: type: string format: uuid description: The unique identifier of the payment. publicPaymentId: type: string format: uuid maxLength: 8 description: The public identifier of the payment. organizationId: type: string format: uuid description: The unique identifier of the organization. type: type: string description: '`BILL` - Bill that is being deducted from the account after transactions have been processed `TOPUP` - Top-up that is being transferred onto the account before transactions are initiated `DIRECT_DEBIT_REVERSAL` - Organization is charged with a fee because direct debit was not successful multiple times `BILL_PAYMENT_REVERSAL` - Organization is charged with a fee because bill payment was not successful multiple times `PAYOUT` - Money transferred from Pliant to an external bank account (only for pre-funded organizations) out of Pliant `INTERNAL_TRANSFER` - Internal transfer payments are related to transferring funds between multiple card accounts of an organization, for example when the benefit card-account is loaded with money from the main card-account. `INTERNAL_TRANSFER_REVERSAL` - Internal transfer reversal payments are related to transferring funds between multiple card accounts of an organization. `PAY_IN` - Inbound transfer credited from a third-party sender, i.e. an account holder different from the receiving customer `OTHER` ' enum: - BILL - TOPUP - DIRECT_DEBIT_REVERSAL - BILL_PAYMENT_REVERSAL - PAYOUT - INTERNAL_TRANSFER - INTERNAL_TRANSFER_REVERSAL - PAY_IN - OTHER method: type: string description: '`DIRECT_DEBIT_CORE`: Indicates that money was send to Pliant platform via core direct debit. `DIRECT_DEBIT_B2B`: Indicates that money was send to Pliant platform via B2B direct debit. `WIRE_TRANSFER`: Indicates that money has been sent to Pliant platform via wire transfer (SEPA credit transfer). ' enum: - DIRECT_DEBIT_CORE - DIRECT_DEBIT_B2B - WIRE_TRANSFER status: type: string description: The status of the payment. The initial payment status is `UPCOMING` for bills. It is different for other types of payments, see [our guides](/docs/payment-entity) for details. After midnight of the `cutoffDate` it changes to `READY_FOR_PMT`. This can be different under certain circumstances regarding the organizations payment terms, see `paymentDefermentInDays`. The day after the `cutoffDay`, around 15:00 German time, the payment is checked and submitted. The status then changes to `PENDING`. After midnight of the `plannedPaymentDate`, the payment status changes to `PAID`. enum: - PLANNED - UPCOMING - DEFERRED - READY_FOR_PMT - PENDING - PAID - FAILED - DISCARDED - BOOKED - REVERSED amount: type: object description: The amount of the payment. properties: value: type: number description: The value of the monetary amount, converted to minor units of the currency. For instance 1.00 EUR is 100 cents, thus the value here is `100`. See our [guides](/docs/monetary-values) for more details about how to handle monetary amounts. currency: type: string description: The currency of the monetary amount in ISO 4217 format, for example `EUR` for Euro or `USD` for US Dollar. paymentDefermentInDays: type: - integer - 'null' description: The number of days the payment is deferred. cutoffDate: type: - string - 'null' format: date description: 'The cutoff date of the payment, e.g `2023-03-23`. This date describes the last day when transactions can be added to the payment. Or to put it differently: the cutoffDate is equal to or later than the last booked transaction linked to this payment. For payments of type `BILL` this field is normally filled. There is one special case where it might be empty for `BILL` payments: if a previous payment failed, we create a new payment of the same type and mark the failed payment as such. This newly created ''retry'' payment will not have a `cutoffDate`, since it is just a retry of the already existing payment. Other payment types such as `TOPUP`, `BILL_PAYMENT_REVERSAL`, `DIRECT_DEBIT_REVERSAL` and `PAYOUT` will also not have a `cutoffDate`.' plannedPaymentDate: type: - string - 'null' format: date description: The planned payment date of the payment, e.g `2023-03-23`. actualPaymentDate: type: - string - 'null' format: date description: The actual payment date of the payment, e.g `2023-03-23`. partnerSubmissionStatus: type: string description: The partner can use this field to indicate the processing of the payment on its side. enum: - NOT_SYNCED - SYNCED - TEMP_LOCKED - LOCKED partnerSubmissionStatusSyncedAt: type: - string - 'null' format: date-time description: The date when the partnerSubmissionStatus was set to SYNCED. partnerSubmissionStatusTempLockedAt: type: - string - 'null' format: date-time description: The date when the partnerSubmissionStatus was set to TEMP_LOCKED. partnerSubmissionStatusLockedAt: type: - string - 'null' format: date-time description: The date when the partnerSubmissionStatus was set to LOCKED. createdAt: type: string format: date-time description: The date when the payment was created. updatedAt: type: - string - 'null' format: date-time description: The date when the payment was last updated. relatedTransactions: type: array description: The related transactions of this payment. This array will grow in size when a transaction is made within the payment frequency window of the organization. It will grow until (including) the `cutoffDate` of the payment. Transactions are added daily to payments at 09:00 German time. items: type: string format: uuid cardAccountId: type: string format: uuid description: The unique identifier of the [card account](/docs/card-account). billId: type: - string - 'null' format: uuid description: The unique identifier of the bill associated with this payment. '400': $ref: '#/paths/~1cards/get/responses/400' '401': $ref: '#/paths/~1cards/get/responses/401' '403': $ref: '#/paths/~1cards/get/responses/403' '404': $ref: '#/paths/~1cards/post/responses/404' '429': $ref: '#/paths/~1cards/get/responses/429' '500': $ref: '#/paths/~1cards/get/responses/500' components: securitySchemes: bearerAuth: type: http scheme: bearer description: This API uses oAuth2 with client credentials flow to [obtain the Bearer Token](/docs/authenticated-api-usage). bearerFormat: JWT x-provenance: method: searched source: https://customer-api.getpliant.com/reference harvested: '2026-10-14' tool: harvest-readme-openapi.py note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored. assembled_from: - https://customer-api.getpliant.com/reference/activate-physical-card.md - https://customer-api.getpliant.com/reference/assign-project-team.md - https://customer-api.getpliant.com/reference/assign-to-team.md - https://customer-api.getpliant.com/reference/bulk-upsert-subscriptions.md - https://customer-api.getpliant.com/reference/card-pan-and-cvv-pci-vault.md - https://customer-api.getpliant.com/reference/card-pan-tokenized-from-pci-proxy.md - https://customer-api.getpliant.com/reference/claim-card-as-copilot.md - https://customer-api.getpliant.com/reference/create-account-entry-subscription.md - https://customer-api.getpliant.com/reference/create-accounting-project-subscription.md - https://customer-api.getpliant.com/reference/create-accounting-team-subscription.md - https://customer-api.getpliant.com/reference/create-accounting-transaction-subscription.md - https://customer-api.getpliant.com/reference/create-card-account-subscription.md - https://customer-api.getpliant.com/reference/create-card-account-transfer.md - https://customer-api.getpliant.com/reference/create-card-account.md - https://customer-api.getpliant.com/reference/create-card-copilot-subscription.md - https://customer-api.getpliant.com/reference/create-card-subscription.md - https://customer-api.getpliant.com/reference/create-cardholder-subscription.md - https://customer-api.getpliant.com/reference/create-custom-field-option.md - https://customer-api.getpliant.com/reference/create-custom-field.md - https://customer-api.getpliant.com/reference/create-payment-subscription.md - https://customer-api.getpliant.com/reference/create-project.md - https://customer-api.getpliant.com/reference/create-receipt-automatching-subscription.md - https://customer-api.getpliant.com/reference/create-receipt-subscription.md - https://customer-api.getpliant.com/reference/create-statement-subscription.md - https://customer-api.getpliant.com/reference/create-team.md - https://customer-api.getpliant.com/reference/create-transaction-subscription.md - https://customer-api.getpliant.com/reference/deactivate-card-account.md - https://customer-api.getpliant.com/reference/deactivate-cardholder.md - https://customer-api.getpliant.com/reference/deactivate-team.md - https://customer-api.getpliant.com/reference/delete-custom-field-option.md - https://customer-api.getpliant.com/reference/delete-custom-field.md - https://customer-api.getpliant.com/reference/delete-project.md - https://customer-api.getpliant.com/reference/delete-receipt.md - https://customer-api.getpliant.com/reference/delete-subscription.md - https://customer-api.getpliant.com/reference/delete-team.md - https://customer-api.getpliant.com/reference/delete-transaction-comment.md - https://customer-api.getpliant.com/reference/generate-test-transactions-in-sandbox.md - https://customer-api.getpliant.com/reference/get-account-entries.md - https://customer-api.getpliant.com/reference/get-accounting-transactions-batch.md - https://customer-api.getpliant.com/reference/get-available-cards.md - https://customer-api.getpliant.com/reference/get-callback-details.md - https://customer-api.getpliant.com/reference/get-callback-log.md - https://customer-api.getpliant.com/reference/get-callback-subscriptions.md - https://customer-api.getpliant.com/reference/get-callback.md - https://customer-api.getpliant.com/reference/get-card-account-details.md - https://customer-api.getpliant.com/reference/get-card-accounts-available-currencies.md - https://customer-api.getpliant.com/reference/get-card-accounts.md - https://customer-api.getpliant.com/reference/get-card-controls-by-card.md - https://customer-api.getpliant.com/reference/get-card-pin.md - https://customer-api.getpliant.com/reference/get-cardholder-details.md - https://customer-api.getpliant.com/reference/get-cards.md - https://customer-api.getpliant.com/reference/get-custom-field-options.md - https://customer-api.getpliant.com/reference/get-custom-fields.md - https://customer-api.getpliant.com/reference/get-multiple-card-details.md - https://customer-api.getpliant.com/reference/get-organization-details.md - https://customer-api.getpliant.com/reference/get-otp-for-pci-widget.md - https://customer-api.getpliant.com/reference/get-payments-detail.md - https://customer-api.getpliant.com/reference/get-payments.md - https://customer-api.getpliant.com/reference/get-projects.md - https://customer-api.getpliant.com/reference/get-receipt-automatcher-status.md - https://customer-api.getpliant.com/reference/get-receipt-detail.md - https://customer-api.getpliant.com/reference/get-receipts.md - https://customer-api.getpliant.com/reference/get-single-card-details.md - https://customer-api.getpliant.com/reference/get-statement-csv.md - https://customer-api.getpliant.com/reference/get-statement-detail.md - https://customer-api.getpliant.com/reference/get-statementpdf.md - https://customer-api.getpliant.com/reference/get-statements.md - https://customer-api.getpliant.com/reference/get-teams.md - https://customer-api.getpliant.com/reference/get-transactions-detail-batch.md - https://customer-api.getpliant.com/reference/get-transactions-detail.md - https://customer-api.getpliant.com/reference/get-transactions.md - https://customer-api.getpliant.com/reference/invite-cardholders.md - https://customer-api.getpliant.com/reference/issue-card-instant-with-pci.md - https://customer-api.getpliant.com/reference/issue-card-instant.md - https://customer-api.getpliant.com/reference/issue-card.md - https://customer-api.getpliant.com/reference/list-cardholders.md - https://customer-api.getpliant.com/reference/list-organizations.md - https://customer-api.getpliant.com/reference/load-cards-batch.md - https://customer-api.getpliant.com/reference/lock-card.md - https://customer-api.getpliant.com/reference/metadata-receipt-to-automatcher.md - https://customer-api.getpliant.com/reference/receipt-as-merged-pdf.md - https://customer-api.getpliant.com/reference/receipt-as-pdf.md - https://customer-api.getpliant.com/reference/receipt-original.md - https://customer-api.getpliant.com/reference/receipt-thumbnail.md - https://customer-api.getpliant.com/reference/register-cardholders.md - https://customer-api.getpliant.com/reference/remove-account-entry-subscription.md - https://customer-api.getpliant.com/reference/remove-accounting-project-subscription.md - https://customer-api.getpliant.com/reference/remove-accounting-team-subscription.md - https://customer-api.getpliant.com/reference/remove-accounting-transaction-subscription.md - https://customer-api.getpliant.com/reference/remove-card-account-subscription.md - https://customer-api.getpliant.com/reference/remove-card-copilot-subscription.md - https://customer-api.getpliant.com/reference/remove-cardholder-subscription.md - https://customer-api.getpliant.com/reference/remove-cards-subscription.md - https://customer-api.getpliant.com/reference/remove-payment-subscription.md - https://customer-api.getpliant.com/reference/remove-receipt-automatching-subscription.md - https://customer-api.getpliant.com/reference/remove-receipt-subscription.md - https://customer-api.getpliant.com/reference/remove-statement-subscription.md - https://customer-api.getpliant.com/reference/remove-transaction-subscription.md - https://customer-api.getpliant.com/reference/replace-card.md - https://customer-api.getpliant.com/reference/resend-callbacks.md - https://customer-api.getpliant.com/reference/search-callbacks.md - https://customer-api.getpliant.com/reference/simulate-prefund-payment.md - https://customer-api.getpliant.com/reference/simulate-transaction-status-transition.md - https://customer-api.getpliant.com/reference/terminate-card.md - https://customer-api.getpliant.com/reference/unassign-from-team.md - https://customer-api.getpliant.com/reference/unassign-project-team.md - https://customer-api.getpliant.com/reference/unlock-card.md - https://customer-api.getpliant.com/reference/update-card-account.md - https://customer-api.getpliant.com/reference/update-card-controls-by-card.md - https://customer-api.getpliant.com/reference/update-card-copilots.md - https://customer-api.getpliant.com/reference/update-card-label.md - https://customer-api.getpliant.com/reference/update-card-limit.md - https://customer-api.getpliant.com/reference/update-card-validity-period.md - https://customer-api.getpliant.com/reference/update-card.md - https://customer-api.getpliant.com/reference/update-cardholders.md - https://customer-api.getpliant.com/reference/update-custom-field-option.md - https://customer-api.getpliant.com/reference/update-custom-field.md - https://customer-api.getpliant.com/reference/update-custom-fields-on-accounting-transaction.md - https://customer-api.getpliant.com/reference/update-custom-fields-on-card.md - https://customer-api.getpliant.com/reference/update-project.md - https://customer-api.getpliant.com/reference/update-team.md - https://customer-api.getpliant.com/reference/update-transaction-category.md - https://customer-api.getpliant.com/reference/update-transaction-comment.md - https://customer-api.getpliant.com/reference/update-transaction-partner-submission-status-batch.md - https://customer-api.getpliant.com/reference/update-transaction-partner-submission-status.md - https://customer-api.getpliant.com/reference/update-transaction-receipt-upload.md - https://customer-api.getpliant.com/reference/upload-receipt-to-automatcher.md - https://customer-api.getpliant.com/reference/upload-receipt.md merge: pages: 128 deduped: 452 conflicts_kept_first: 0