# Create a transaction from this listing (deprecated)

Calling  with no parameters will create a
new transaction with the details provided by the listing.

The optional  parameter can be passed to create a
transaction for a multiple of the original listing. In this
case, the  and  for the new transaction will also
need to be passed.

As an example, consider a listing for a chair with a price of
 . If a user wants to buy 10 of these in a single
transaction then the charge for the total can be retrieved using
 (note the
addition of the optional quantity parameter at the end). This
will return a  of  and an associated .
These new values must then be passed to 
with , which will create a new transaction with the
new pricing information. The new transaction will also include a
 field, which doesn't have a functional effect on the
transaction, but is included for informational purposes.

Note that this functionality is not available for single-use
listings, from which only singular transactions may be created.

Offline access is allowed for this endpoint when the user has
granted the  scope to the client
that is performing the request.


Endpoint: POST /p2p/multi_use_listings/{listingId}/create_transaction
Version: 0.1.0
Security: OAuth2

## Path parameters:

  - `listingId` (integer, required)

## Query parameters:

  - `quantity` (integer)

  - `price` (integer)

  - `charge` (integer)

## Response 200 fields (application/json):

  - `amount_refunded` (integer)

  - `buyer_handover_confirmed` (string)
    Example: "2019-12-25T16:00:00Z"

  - `buyer_id` (string)
    Example: "feb33a87-3917-4538-9260-127c8a6b5232"

  - `buyer_is_guest` (boolean)

  - `cancellation` (object)

  - `cancellation.reason` (string, required)

  - `cancelled` (string)

  - `claimed_by_buyer` (string)

  - `claimed_by_seller` (string)

  - `client_id` (string, required)
    Example: "trustap-app"

  - `complained` (string)

  - `complaint` (object)
    Example: {"description":"Item was fake"}

  - `complaint.description` (string, required)
    Example: "Item was fake"

  - `complaint_period_deadline` (string)

  - `complaint_period_ended` (string)

  - `created` (string, required)
    Example: "2019-12-25T09:00:00Z"

  - `currency` (string, required)
    The currency of the transaction. Note that, at present, the
buyer must pay using the transaction's currency and the
seller will be paid in the transaction's currency.
    Example: "eur"

  - `deposit_accepted` (string)
    Example: "2019-12-25T12:00:00Z"

  - `deposit_paid` (string)
    Example: "2019-12-25T11:00:00Z"

  - `deposit_pricing` (object, required)
    Example: {"charge":78,"price":1234}

  - `deposit_pricing.charge` (integer, required)
    Example: 78

  - `deposit_pricing.charge_international_payment` (integer)

  - `deposit_pricing.charge_seller` (integer, required)

  - `deposit_pricing.deposit_fee_multiplier` (object)

  - `deposit_pricing.deposit_fee_multiplier.fee_multiplier` (number, required)

  - `deposit_pricing.price` (integer, required)
    Example: 1234

  - `deposit_refunded` (string)

  - `deposit_review` (object)

  - `deposit_review.approved` (boolean)

  - `deposit_review.finished` (string)

  - `deposit_review.outcome_reason` (string)

  - `deposit_review.started` (string)

  - `deposit_review_flagged` (string)

  - `funds_released` (string)
    Example: "2019-12-25T17:00:00Z"

  - `id` (integer, required)
    Example: 1309

  - `is_deposit_payment_in_progress` (boolean, required)
    If the deposit is paid via a delayed payment method,
such as SEPA debit, this field will be  until the
payment has fully succeeded or failed.

  - `is_remainder_payment_in_progress` (boolean, required)
    If the remainder is paid via a delayed payment method,
such as SEPA debit, this field will be  until the
payment has fully succeeded or failed.

  - `join_code` (string)

  - `joined` (string)
    Example: "2019-12-25T10:00:00Z"

  - `listing_id` (string)
    If the transaction is created from a listing then this is
the ID of that listing; otherwise this property is omitted.

  - `listing_type` (string)
    Enum: "single_use", "multi_use", "prepaid"

  - `order_issue_raised` (string)

  - `priced` (string)
    Example: "2019-12-25T13:00:00Z"

  - `pricing` (object)
    Example: {"charge":78,"price":1234}

  - `quantity` (integer, required)

  - `refunded` (string)

  - `refunds` (array)

  - `refunds.amount` (integer, required)

  - `refunds.stripe_refund_id` (string, required)

  - `rejected` (string)

  - `relased_to_seller` (string)

  - `released_to_seller` (boolean)

  - `remainder_paid` (string)
    Example: "2019-12-25T14:00:00Z"

  - `remainder_review` (object)

  - `remainder_review_flagged` (string)

  - `remainder_skipped` (string)

  - `seller_handover_confirmed` (string)
    Example: "2019-12-25T15:00:00Z"

  - `seller_id` (string)
    Example: "ad5bb99f-85bf-47e1-be0d-15e7541c6ad7"

  - `seller_is_guest` (boolean)

  - `skip_remainder` (boolean, required)
    If  is  then this transaction will
move to the "confirm handover" step after the deposit has
been accepted.

  - `status` (string, required)
    Example: "funds_released"

## Response 400 fields (application/json):

  - `code` (string, required)
    Example: "negative_price"

  - `error` (string, required)
    A contextual description of the error that occurred. When
handling errors the  field should be used to determine
the type of error that occurred, as the text in the 
field may change unexpectedly.
    Example: "`price` cannot be negative"