Get a single payment transaction import Beta

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://developer.pace.cloud/doc/payment/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "Payment MCP server": {
    "url": "https://developer.pace.cloud/doc/payment/mcp"
  }
}

Close
GET /2026-4/payment-transaction-imports/{paymentTransactionImportId}

Retrieve a single import by its identifier. Request include=items for the result of every submitted record, ordered by position. With the :authenticated scope an import of another user is reported as not found rather than forbidden, so it does not reveal that it exists.

Path parameters

  • paymentTransactionImportId string(uuid) Required

    The unique identifier of the import to retrieve.

Query parameters

  • include array[string]

    Related resources to include in the response.

    Value is items.

Responses

  • 200 application/json

    The import was retrieved successfully.

    Hide response attribute Show response attribute object
    • data object Required

      The import for the given import ID, with the result of every submitted record.

      Hide data attributes Show data attributes object
      • clientId string Required

        The identifier of the client that submitted the import, read from its access token.

      • counts object Required

        How many records ended up with which result.

        Hide counts attributes Show counts attributes object
        • failed integer Required

          The number of records that were rejected.

          Minimum value is 0.

        • imported integer Required

          The number of records that created a transaction.

          Minimum value is 0.

        • skipped integer Required

          The number of records whose external id was already imported and that were left unchanged.

          Minimum value is 0.

        • total integer Required

          The number of records that were submitted.

          Minimum value is 0.

      • createdAt string(date-time) Required

        When the import was created.

      • id string(uuid) Required

        The unique identifier of the import.

      • items array[object]

        The result of every submitted record, ordered by position. Only present when requested via the include query parameter.

        Hide items attributes Show items attributes object
        • externalId string Required

          The identifier the importing system assigned to the record.

        • failureCode string | null Required

          Why the record was rejected; null unless the result is FAILED. PAYMENT_METHOD_NOT_FOUND: the payment method is not one of the import user's, which covers a method the payment integration does not know and one that belongs to somebody else.

        • position integer Required

          The 0-based index of the record in the submitted transactions array.

          Minimum value is 0.

        • result string Required

          What became of the record. IMPORTED: a transaction was created. SKIPPED: the external id was already imported, the existing transaction is left unchanged. FAILED: the record was rejected, see failureCode.

          Values are IMPORTED, SKIPPED, or FAILED.

        • transactionId string(uuid) | null Required

          The transaction the record refers to: the one this import created (IMPORTED), the one that already carried the external id (SKIPPED), or null (FAILED).

      • status string Required

        The summary of the record results. COMPLETED: no record failed (skipped records count as success). PARTIAL: some records failed, the others were imported or skipped. FAILED: every record failed. Imports are processed synchronously, so there is no in-progress value.

        Values are COMPLETED, PARTIAL, or FAILED.

      • updatedAt string(date-time) Required

        When the import was last updated.

      • userId string(uuid) Required

        The unique identifier of the user the imported transactions belong to.

  • 400

    The request parameters are invalid or missing.

  • 401

    Client authentication failed.

  • 403

    Missing one or more required scopes.

  • 404

    The import was not found.

  • 500

    An internal server error occurred.

GET /2026-4/payment-transaction-imports/{paymentTransactionImportId}
curl \
 --request GET 'https://api.pace.cloud/payment/2026-4/payment-transaction-imports/9b1c0f4e-2f3a-4c5d-8e6f-7a8b9c0d1e2f' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200)
{
  "data": {
    "clientId": "backoffice-importer",
    "counts": {
      "failed": 1,
      "imported": 1,
      "skipped": 1,
      "total": 3
    },
    "createdAt": "2026-07-20T10:15:00.000Z",
    "id": "9b1c0f4e-2f3a-4c5d-8e6f-7a8b9c0d1e2f",
    "items": [
      {
        "externalId": "dkv:TXN-2024-0009182",
        "failureCode": "PAYMENT_METHOD_NOT_FOUND",
        "position": 0,
        "result": "IMPORTED",
        "transactionId": "6fc2acbd-3afd-4df3-9967-836a7929b13f"
      }
    ],
    "status": "PARTIAL",
    "updatedAt": "2026-07-20T10:15:00.000Z",
    "userId": "a1c782d9-7a6c-4e5a-b05b-1d11b93c510a"
  }
}