> ## Documentation Index > Fetch the complete documentation index at: https://docs.jupico.com/llms.txt > Use this file to discover all available pages before exploring further. # Roll back a card transaction > A rollback (communications/system reversal) cancels a transaction whose response you never received — for example, after a timeout. As the original requestor, you are responsible for generating a rollback for every transaction that does not receive a response, to prevent duplicate or inconsistent charges. ## OpenAPI ````yaml /openapi.json post /v1/transactions/creditcard/rollback openapi: 3.0.0 info: title: Jupico - OpenAPI 3.0 description: >- The Jupico API lets Service Providers onboard merchants, process card and eCheck (ACH) payments, run hosted payment pages, manage recurring billing, send payouts, and query every resource. All endpoints use HTTPS with Basic authentication and accept and return JSON. Endpoints are grouped by workflow: onboard merchants first, then accept payments, then move funds and report. termsOfService: https://help.jupico.com/references-and-resources/legal contact: email: support@jupico.com license: name: Jupico License url: https://jupico.com version: 1.0.5 servers: - url: https://sandbox-platform.jupico.com security: - basicAuth: [] tags: - name: Status description: Health check for the Jupico API. - name: Onboarding Invites description: >- Create and send invites that onboard merchants through the Jupico-hosted flow, with optional pre-filled identity, fees, and payout bank account data. - name: Provisioning description: >- Onboard merchants from your own UI. Collect onboarding data and submit it through the provisioning chain: applicant → application → submerchant. - name: Session description: >- Create browser authorization sessions for the Jupico web components, so card and bank account data is tokenized client-side and never touches your servers. - name: Tokenization description: >- Convert one-time tokens from the web components into permanent Jupico tokens, or tokenize raw card data if your systems are PCI DSS compliant. - name: Customer description: >- Create and manage customer records that payments, subscriptions, installments, and invoices link to. - name: Card Transactions description: >- Process credit and debit card transactions using tokenized card data: sale, authorization, capture, void, refund, and rollback. - name: eCheck Transactions description: >- Debit customer bank accounts via eCheck (ACH): sale, void, refund, rollback, and bank account tokenization. - name: Checkouts description: >- Hosted checkout sessions where customers complete payment on a Jupico-hosted page. - name: Payment Links description: >- Shareable links that open a Jupico-hosted payment page — no integration code needed at the point of sharing. - name: Invoices description: Create and email invoices that customers pay online. - name: Subscriptions description: >- Recurring billing. Plans define billing schedules and pricing models; subscriptions enroll customers against a stored payment token. - name: Installments description: Split a fixed total into scheduled payments with an optional deposit. - name: Payouts description: >- Send funds from a submerchant's available balance to a tokenized bank account with on-demand payout instructions. - name: Query description: >- Search and report across every resource: transactions, merchants, settlements, balances, disputes, fees, and more. All query endpoints accept the same filter, sort, and pagination envelope — see the Query Capabilities guide. paths: /v1/transactions/creditcard/rollback: post: tags: - Card Transactions summary: Roll back a card transaction description: >- A rollback (communications/system reversal) cancels a transaction whose response you never received — for example, after a timeout. As the original requestor, you are responsible for generating a rollback for every transaction that does not receive a response, to prevent duplicate or inconsistent charges. operationId: ccRollback requestBody: $ref: '#/components/requestBodies/ccRollback' responses: '200': $ref: '#/components/responses/ccRollback' security: - basicAuth: [] components: requestBodies: ccRollback: description: '***To test this endpoint you need to make an SALE request first***' required: true content: application/json: schema: $ref: '#/components/schemas/ccRollback' examples: Rollback: $ref: '#/components/examples/ccRollback' responses: ccRollback: description: Successful rollback content: application/json: schema: type: object properties: success: type: boolean description: >- Whether the request was processed successfully. Declines return HTTP 200 with `success: false`. code: type: string description: Machine-readable result code. See the Error Codes reference. message: type: string description: Human-readable result message. schemas: ccRollback: properties: subMerchantId: type: string description: Unique identifier of the submerchant. amount: type: number description: The amount of the original transaction. paymentToken: type: object properties: type: type: string description: Type of token supplied. token: type: object description: Token payload returned by tokenization. description: >- The payment credential to charge: a one-time token from the web component or a stored Jupico token. description: type: string description: Free-text description. referenceId: type: string description: >- Your own reference for this transaction. Returned in responses and query results for reconciliation. metadata: $ref: '#/components/schemas/metadata' required: - subMerchantId - amount - paymentToken metadata: type: object description: >- metadata is an object that can host as much as 50 key-value pairs, where the keys can be at most 40 char length and can’t include the characters “[“ or “]”, and the values must be strings and cannot exceed 500 chars [Learn more about metadata](https://docs.jupico.com/docs/metadata#/) additionalProperties: type: string maxLength: 500 x-key-max-length: 40 examples: ccRollback: summary: Example request value: subMerchantId: jpt-sim-md-1 amount: >- You need to change *this* with amount from the operation that you are trying to rollback description: reversal item returned paymentToken: type: creditcard token: provider: jupico token: 5dd19881-b437-42b0-9c9b-7773ebb598eb metadata: test: test securitySchemes: basicAuth: type: http scheme: basic ````