Roll a payment transaction import back 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
DELETE /2026-4/payment-transaction-imports/{paymentTransactionImportId}

Deletes an import as a unit: the import itself, the result of every submitted record, and every payment transaction the import created, which disappear from the transaction history. A record that was skipped is not rolled back - its transaction was created by an earlier import and belongs to it. For a trusted caller deleting is idempotent, so an import that is already gone reports success rather than an error. The :authenticated scope may only roll back the imports of the authenticated user and is refused otherwise, which covers an import of another user and one that does not exist alike.

Path parameters

  • paymentTransactionImportId string(uuid) Required

    The unique identifier of the import to roll back.

Responses

  • 204

    The import was rolled back, or did not exist.

  • 400

    The request parameters are invalid or missing.

  • 401

    Client authentication failed.

  • 403

    The caller may only roll back its own imports and named an import of another user, or one that does not exist.

    Missing one or more required scopes.

  • 500

    An internal server error occurred.

DELETE /2026-4/payment-transaction-imports/{paymentTransactionImportId}
curl \
 --request DELETE 'https://api.pace.cloud/payment/2026-4/payment-transaction-imports/9b1c0f4e-2f3a-4c5d-8e6f-7a8b9c0d1e2f' \
 --header "Authorization: Bearer $ACCESS_TOKEN"