> ## Documentation Index
> Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Regenerate transaction

> Regenerates a pre-built transaction for an order.

**Offramp orders** (status: Created): The new transaction will be sent over the webhook asynchronously. Returns HTTP 202 Accepted.

**Stellar onramp orders with claimable balances** (status: Completed): If the stored claim transaction has a stale sequence number (e.g., the user transacted on Stellar before claiming), this endpoint rebuilds the unsigned XDR with a fresh sequence number and returns it synchronously. The order's `stellarClaimTransaction` field is also updated. Returns HTTP 200 with the fresh XDR in the response body.




## OpenAPI

````yaml /openapi.yaml post /ramp/order/{order_id}/regenerate_tx
openapi: 3.1.0
info:
  title: FX API
  version: 1.0.0
  description: >
    API for managing FX operations including onboarding, quotes, orders, and
    customer management.

    This API provides endpoints for managing customers, bank accounts, crypto
    wallets, orders, and webhooks.
servers:
  - url: https://api.etherfuse.com
    description: Production API
  - url: https://api.sand.etherfuse.com
    description: Sandbox API (for testing)
security: []
tags:
  - name: Lookup
    description: Public endpoints for looking up stablebond and exchange rate data
  - name: Assets
    description: Get available assets for ramping
  - name: Onboarding
    description: Customer onboarding and KYC
  - name: Bank Accounts
    description: Manage customer bank accounts
  - name: Agreements
    description: Handle customer agreements and consents
  - name: Quotes
    description: Get quotes for conversions
  - name: Orders
    description: Create and manage orders
  - name: Swaps
    description: Create and manage swaps
  - name: Customers
    description: Manage customers
  - name: Crypto Wallets
    description: Manage crypto wallets
  - name: Webhooks
    description: Manage webhook subscriptions
  - name: Organizations
    description: Manage organizations and child organizations
paths:
  /ramp/order/{order_id}/regenerate_tx:
    post:
      tags:
        - Orders
      summary: Regenerate transaction
      description: >
        Regenerates a pre-built transaction for an order.


        **Offramp orders** (status: Created): The new transaction will be sent
        over the webhook asynchronously. Returns HTTP 202 Accepted.


        **Stellar onramp orders with claimable balances** (status: Completed):
        If the stored claim transaction has a stale sequence number (e.g., the
        user transacted on Stellar before claiming), this endpoint rebuilds the
        unsigned XDR with a fresh sequence number and returns it synchronously.
        The order's `stellarClaimTransaction` field is also updated. Returns
        HTTP 200 with the fresh XDR in the response body.
      parameters:
        - name: order_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
          description: ID of the order to regenerate the transaction for
      responses:
        '200':
          description: >
            Stellar claim transaction regenerated successfully. The fresh
            unsigned XDR is returned in the response body and stored on the
            order.
          content:
            application/json:
              schema:
                type: object
                properties:
                  stellarClaimTransaction:
                    type: string
                    description: >-
                      Base64-encoded unsigned XDR for the claim transaction
                      (ChangeTrust + ClaimClaimableBalance)
        '202':
          description: >-
            Offramp transaction regeneration request accepted. The new
            transaction will arrive via webhook.
      security:
        - ApiKeyAuth: []
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        API key for authentication. Pass the key directly (e.g., `Authorization:
        your-api-key`). Do not use a `Bearer` prefix.

````