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

# The Deposit Preauthorization object

### Description

The Deposit Preauthorization object enables you to reserve funds on a card so they can be captured later, using two API calls:

* Authorization of the transaction, handled by the Deposit Preauthorization object
* Capture of the funds, handled by the Deposit Preauthorized PayIn object

The Deposit Preauthorization object is used for two payment methods, indicated by the `PaymentType`:

* `CARD` – Created using [POST Create a Card Deposit Preauthorization](/api-reference/deposit-preauthorizations/create-card-deposit-preauthorization)
* `PAYPAL` – Created using [POST Create a PayPal Deposit Preauthorization](/api-reference/deposit-preauthorizations/create-paypal-deposit-preauthorization)

In both cases, the capture is made with the same endpoint, [POST Create a Deposit Preauthorized PayIn](/api-reference/deposit-preauthorizations/create-deposit-preauthorized-payin):

* `CARD` – Within **29.5** days.
* `PAYPAL` – Within 3 days as recommended by PayPal, but the technical limit is **29** days (not 29.5).

Note that preauthorizations may not be permitted by some issuers and for some card types.

<Check>
  **Best practice - For PayPal, capture funds within 3 days**

  PayPal recommends that you capture preauthorized funds within 3 days. This is because the success of the capture is subject to risk and the availability of funds on the card (or other funding instrument) that the user has linked to their PayPal account.
</Check>

<Note>
  **Note – Multi-capture not possible with the Deposit Preauthorization**

  Multiple partial captures are not possible with the Deposit Preauthorization, for either `CARD` or `PAYPAL`. In both cases however, the single capture can be for an amount less than the preauthorized amount.
</Note>

### Attributes

<Tabs>
  <Tab title="Card">
    <ParamField body="Id" type="string">
      Max. length: 255 characters
    </ParamField>

    <ParamField body="CreationDate" type="Unix timestamp">
      The date and time at which the object was created.
    </ParamField>

    <ParamField body="ExpirationDate" type="Unix timestamp">
      The date and time at which the hold period ends and the preauthorized funds are released.\
      At the expiration date, the deposit preauthorization’s `PaymentStatus` changes to `EXPIRED` if no captures were made.
    </ParamField>

    <ParamField body="AuthorId" type="string">
      The unique identifier of the user at the source of the transaction.
    </ParamField>

    <ParamField body="DebitedFunds" type="object">
      Information about the preauthorized funds.

      <Expandable title="properties">
        <ParamField body="Currency" type="string">
          **Returned values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings).

          The currency of the funds.
        </ParamField>

        <ParamField body="Amount" type="integer">
          An amount of money in the smallest sub-division of the currency (e.g., EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`).
        </ParamField>
      </Expandable>
    </ParamField>

    <ParamField body="Status" type="string">
      **Returned values:** `CREATED`, `SUCCEEDED`, `FAILED`

      The status of the authorization.
    </ParamField>

    <ResponseField name="PaymentStatus" type="string">
      **Returned values:** `WAITING`, `CANCELED`, `CANCEL_REQUESTED`, `EXPIRED`, `VALIDATED`, `FAILED`

      The payment status of the deposit preauthorization object:

      * `WAITING` – The deposit preauthorization can be used: the preauthorized funds can be captured (if `Status` is `SUCCEEDED`) or the preauthorization can be canceled manually.
      * `CANCELED` – Value to pass to manually cancel the deposit preauthorization before use; indicates that the deposit preauthorization was canceled manually.
      * `CANCEL_REQUESTED` – The cancellation of the deposit preauthorization has been requested but not yet processed.
      * `EXPIRED` – The hold period on the preauthorized funds has ended without it being used.
      * `VALIDATED` – Indicates that the preauthorized funds were captured.
      * `FAILED` – The pay-in against the preauthorization has failed, but a retry may be possible.
    </ResponseField>

    <ParamField body="PayinsLinked" type="object">
      Information about the deposit preauthorized pay-ins made against the deposit preauthorization.

      <Expandable>
        <ParamField body="PayinCaptureId" type="string">
          The unique identifier of the preauthorized pay-in (capture) made against the deposit preauthorization to debit the preauthorized funds.
        </ParamField>

        <ParamField body="PayinComplementId" type="string">
          The unique identifier of the <a href="/api-reference/deposit-preauthorizations/create-deposit-preauthorized-payin-complement">deposit preauthorized pay-in complement</a> made against the deposit preauthorization to debit additional funds.
        </ParamField>
      </Expandable>
    </ParamField>

    <ParamField body="ResultCode" type="string">
      The code indicating the result of the operation. This information is mostly used to <a href="/errors/codes">handle errors</a> or for filtering purposes.
    </ParamField>

    <ParamField body="ResultMessage" type="string">
      The explanation of the result code.
    </ParamField>

    <ParamField body="CardId" type="string">
      The unique identifier of the Card object, obtained during the card registration process.
    </ParamField>

    <ParamField body="PreferredCardNetwork" type="string">
      **Returned values:** `VISA`, `MASTERCARD`, `CB`, `MAESTRO`

      The card network to use, as chosen by the cardholder, in case of <a href="/guides/payment-methods/card/co-branded">co-branded cards</a>.
    </ParamField>

    <ParamField body="SecureModeReturnURL" type="string">
      Max. length: 255 characters

      The URL to which users are automatically returned after 3DS2 if it is triggered (i.e., if the `SecureModeNeeded` parameter is set to `true`).
    </ParamField>

    <ParamField body="SecureModeRedirectURL" type="string">
      Max. length: 255 characters

      The URL to which to redirect the user to proceed to 3DS2 validation.

      **Caution:** This variable URL is specific to each payment. You must rely on the returned URL in full (host, path, and queries) and not hardcode any part of it.
    </ParamField>

    <ParamField body="SecureModeNeeded" type="boolean">
      Whether or not the `SecureMode` was used.
    </ParamField>

    <ParamField body="PaymentType" type="string">
      **Returned values:** `CARD`, `DIRECT_DEBIT`, `PREAUTHORIZED`, `BANK_WIRE`

      The type of pay-in.
    </ParamField>

    <ParamField body="ExecutionType" type="string">
      **Returned values:** `WEB`, `DIRECT`, `EXTERNAL_INSTRUCTION`

      The type of execution for the pay-in.
    </ParamField>

    <ParamField body="StatementDescriptor" type="string">
      Max. length: 10 characters; only alphanumeric and spaces

      Custom description to appear on the user’s bank statement along with the platform name. Different banks may show more or less information. See the <a href="/bank-statements">Customizing bank statement references</a> article for details.
    </ParamField>

    <ParamField body="Culture" type="string">
      **Returned values:** One of the supported languages in the <a href="/api-reference/overview/data-formats">ISO 639-1 format</a>: DE, EN, ES, FR, IT, NL, PL, PT.

      The language in which the payment page is to be displayed.
    </ParamField>

    <ParamField body="BrowserInfo" type="object">
      Information about the browser used by the end user (author) to perform the payment.

      <Expandable title="properties">
        <ParamField body="AcceptHeader" type="string">
          The exact content of the HTTP accept headers as sent to the platform from the end user’s browser.
        </ParamField>

        <ParamField body="JavaEnabled" type="boolean">
          Whether or not the end user’s browser has the ability to execute Java.
        </ParamField>

        <ParamField body="Language" type="string">
          Format: Two-letter language code (ISO 639-1 alpha-2) followed by two-letter country code (ISO 3166-1 alpha-2), separated by a hyphen (example: `en-US`; pattern:`^[a-zA-Z]{2}(-[a-zA-Z]{2})?$`)

          The language of the browser.
        </ParamField>

        <ParamField body="ColorDepth" type="integer">
          The value representing the depth of the screen’s color palette for displaying images, in bits per pixel.
        </ParamField>

        <ParamField body="ScreenHeight" type="integer">
          Max. length: 6 characters

          The height of the screen in pixels.
        </ParamField>

        <ParamField body="ScreenWidth" type="integer">
          Max. length: 6 characters

          The width of the screen in pixels.
        </ParamField>

        <ParamField body="TimeZoneOffset" type="integer">
          The difference in minutes between the browser’s timezone and UTC.
        </ParamField>

        <ParamField body="UserAgent" type="string">
          Max. length: 255 characters

          The exact content of the HTTP User-Agent header.
        </ParamField>

        <ParamField body="JavascriptEnabled" type="boolean">
          Whether or not the end user’s browser has the ability to execute JavaScript.
        </ParamField>
      </Expandable>
    </ParamField>

    <ParamField body="IpAddress" type="string">
      The IP address of the end user initiating the transaction, in IPV4 or IPV6 format.
    </ParamField>

    <ParamField body="Billing" type="object">
      **Default value:** FirstName, LastName, and Address information of the Shipping object if any, otherwise the user (author).

      Information about the end user billing address. If left empty, the default values will be automatically taken into account.

      <Expandable title="properties">
        <ParamField body="FirstName" type="string">
          The first name of the user.
        </ParamField>

        <ParamField body="LastName" type="string">
          Max. length: 100 characters

          The last name of the user.
        </ParamField>

        <ParamField body="Address" type="object">
          Information about the billing address.

          <Expandable>
            <ParamField body="AddressLine1" type="string">
              Max. length: 255 characters

              The first line of the address.
            </ParamField>

            <ParamField body="AddressLine2" type="string">
              Max. length: 255 characters

              The second line of the address.
            </ParamField>

            <ParamField body="City" type="string">
              Max. length: 255 characters

              The city of the address.
            </ParamField>

            <ParamField body="Region" type="string">
              Max. length: 255 characters

              Required if `Country` is US, CA, or MX.

              The region of the address.
            </ParamField>

            <ParamField body="PostalCode" type="string">
              Max. length: 255 characters

              The postal code of the address. The postal code can contain the following characters: alphanumeric, dashes, and spaces.
            </ParamField>

            <ParamField body="Country" type="string">
              Format: Two-letter country code ([ISO 3166-1 alpha-2 format](/api-reference/overview/data-formats))

              The country of the address.
            </ParamField>
          </Expandable>
        </ParamField>
      </Expandable>
    </ParamField>

    <ParamField body="Shipping" type="object">
      **Default value:** FirstName, LastName, and Address information of the Billing object, if supplied, otherwise of the user (author).

      Information about the end user’s shipping address.

      <Expandable title="properties">
        <ParamField body="FirstName" type="string">
          The first name of the user.
        </ParamField>

        <ParamField body="LastName" type="string">
          Max. length: 100 characters

          The last name of the user.
        </ParamField>

        <ParamField body="Address" type="object">
          Information about the shipping address.

          <Expandable>
            <ParamField body="AddressLine1" type="string">
              Max. length: 255 characters

              The first line of the address.
            </ParamField>

            <ParamField body="AddressLine2" type="string">
              Max. length: 255 characters

              The second line of the address.
            </ParamField>

            <ParamField body="City" type="string">
              Max. length: 255 characters

              The city of the address.
            </ParamField>

            <ParamField body="Region" type="string">
              Max. length: 255 characters

              Required if `Country` is US, CA, or MX.

              The region of the address.
            </ParamField>

            <ParamField body="PostalCode" type="string">
              Max. length: 255 characters

              The postal code of the address. The postal code can contain the following characters: alphanumeric, dashes, and spaces.
            </ParamField>

            <ParamField body="Country" type="string">
              Format: Two-letter country code ([ISO 3166-1 alpha-2 format](/api-reference/overview/data-formats))

              The country of the address.
            </ParamField>
          </Expandable>
        </ParamField>
      </Expandable>
    </ParamField>

    <ParamField body="Requested3DSVersion" type="string">
      **Returned values:** `V1`, `V2_1`

      The 3DS protocol version to be applied to the transaction.
    </ParamField>

    <ParamField body="Applied3DSVersion" type="string">
      **Returned values:** `V1`, `V2_1`

      The 3DS protocol version applied to the transaction.
    </ParamField>

    <ParamField body="Tag" type="string">
      Max. length: 255 characters

      Custom data that you can add to this object.
    </ParamField>

    <ParamField body="CardInfo" type="string">
      Information about the card used for the transaction. \
      If the information or data is not available, `null` is returned.

      <Expandable title="properties">
        <ParamField body="BIN" type="string">
          The 6-digit bank identification number (BIN) of the card issuer.
        </ParamField>

        <ParamField body="IssuingBank" type="string">
          The name of the card issuer.
        </ParamField>

        <ParamField body="IssuerCountryCode" type="string">
          Format: Two-letter country code ([ISO 3166-1 alpha-2 format](/api-reference/overview/data-formats))

          The country where the card was issued.
        </ParamField>

        <ParamField body="Type" type="string">
          **Returned values:** `DEBIT`, `CREDIT`, `CHARGE CARD`.

          The type of card product.
        </ParamField>

        <ParamField body="Brand" type="string">
          The card brand. Examples include: `AMERICAN EXPRESS`, `DISCOVER`, `JCB`, `MASTERCARD`, `VISA`, etc.

          **Note:** The possible returned values are numerous and liable to evolve over time.
        </ParamField>

        <ParamField body="SubType" type="string">
          The subtype of the card product. Examples include: `CLASSIC`, `GOLD`, `PLATINUM`, `PREPAID`, etc.

          **Note:** The possible returned values are numerous and liable to evolve over time.
        </ParamField>
      </Expandable>
    </ParamField>

    <ResponseField name="AuthenticationResult" type="object | null" defaultOpen>
      Information about the authentication result, based on the request made by Mangopay and the decision of the issuer regarding the type of authentication to be enforced (if applicable).

      <Expandable title="properties">
        <ResponseField name="AuthenticationType" type="string | null">
          Response values: `CHALLENGE`, `FRICTIONLESS`, `DIRECT_AUTHORIZATION`

          The type of authentication:

          * `CHALLENGE` – The issuer requested SCA to be enforced (for example, using 3DS).
          * `FRICTIONLESS` – The transaction was exempted from SCA because an exemption was granted by the issuer.
          * `DIRECT_AUTHORIZATION` – The transaction was sent to the issuer for authorization without any frictionless or challenge (for example, if SCA doesn't apply).

          A `null` value typically indicates that authentication was not requested (for example, because the request failed before being sent) or a decision was not received.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ParamField body="ProfilingAttemptReference" type="string">
      The unique reference generated for the profiling session, used by the <a href="/guides/fraud-prevention">fraud prevention</a> solution to produce recommendations for the transaction using the profiling data.

      **Note:** Parameter not returned by the API. Profiling feature available on request – contact Mangopay <a href="https://hub.mangopay.com/" target="_blank">via the Dashboard</a> for more information.
    </ParamField>
  </Tab>

  <Tab title="PayPal">
    <ResponseField name="PaypalPayerID" type="string">
      The PayPal identifier of the buyer.
    </ResponseField>

    <ResponseField name="BuyerLastname" type="string">
      The last name of the buyer.
    </ResponseField>

    <ResponseField name="BuyerPhone" type="string">
      The mobile phone number of the buyer.
    </ResponseField>

    <ResponseField name="BuyerFirstname" type="string">
      The first name of the buyer.
    </ResponseField>

    <ResponseField name="BuyerCountry" type="string">
      The country of the buyer.
    </ResponseField>

    <ResponseField name="PaypalOrderID" type="string">
      PayPal's unique identifier for the order.
    </ResponseField>

    <ResponseField name="CancelURL" type="string">
      The URL to which the user is returned after canceling the payment. If not provided, the Cancel button returns the user to the RedirectURL.
    </ResponseField>

    <ResponseField name="Trackings" type="array (object)">
      Shipping information of the `LineItems` added to the pay-in object.

      <Expandable title="properties">
        <ResponseField name="TrackingNumber" type="string">
          The shipment’s tracking number provided by the carrier.
        </ResponseField>

        <ResponseField name="Carrier" type="string">
          The carrier for the shipment. Use the country-specific version of the carrier if it exists, otherwise use its global version.
        </ResponseField>

        <ResponseField name="NotifyBuyer" type="string">
          **Default value:** false

          If `true`, sends an email notification to the `PaypalBuyerAccountEmail` containing the `TrackingNumber` and `Carrier`, which allows the end user to track their shipment with the carrier.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="ShippingPreference" type="string">
      **Returned values:** `SET_PROVIDED_ADDRESS`, `GET_FROM_FILE`, `NO_SHIPPING`

      Information about the shipping address behavior on the PayPal payment page:

      * `SET_PROVIDED_ADDRESS` - The `Shipping` parameter becomes required and its values are displayed to the end user, who is not able to modify them.
      * `GET_FROM_FILE` – The `Shipping` parameter is ignored and the end user can choose from registered addresses.
      * `NO_SHIPPING` – No shipping address section is displayed.
    </ResponseField>

    <ResponseField name="Reference" type="string">
      Max. length: 127 characters (truncated after)

      The platform’s order reference for the transaction.
    </ResponseField>

    <ResponseField name="PaypalBuyerAccountEmail" type="string">
      The email address registered on the PayPal account used to make the payment.
    </ResponseField>

    <ResponseField name="Culture" type="string">
      **Returned values:** One of the supported languages in the <a href="/api-reference/overview/data-formats">ISO 639-1 format</a>: AT, BR, CA, CH, CN, DE, DK, ES, FR, GB, ID, IL, IT, JK, JP, NL, NO, PL, PT, RU, SE, TH, TR, TW, US.

      The language in which the PayPal payment page is to be displayed.
    </ResponseField>

    <ResponseField name="LineItems" type="array">
      object

      Information about the items purchased in the transaction. The total of all line items’ `UnitAmount` and `TaxAmount` must equal the `DebitedFunds` amount (negative amounts not allowed).

      <Expandable title="properties">
        <ResponseField name="Name" type="string">
          Max. length: 127 characters (truncated after)

          The name of the item.
        </ResponseField>

        <ResponseField name="Quantity" type="integer">
          The quantity of the item.
        </ResponseField>

        <ResponseField name="UnitAmount" type="integer">
          The cost of the item, excluding tax.
        </ResponseField>

        <ResponseField name="TaxAmount" type="integer">
          The tax amount applied to the item.
        </ResponseField>

        <ResponseField name="Description" type="string">
          Max. length: 127 characters (truncated after)

          The platform’s unique reference for the seller. This value must be consistently used for the given seller. You can use, for example, the Mangopay `UserId` or the seller’s business name or first name and last name.\
          Caution: Failure to use a unique seller identifier may result in PayPal restricting your service.
        </ResponseField>

        <ResponseField name="Category" type="string">
          **Allowed values:** PHYSICAL\_GOODS, DIGITAL\_GOODS, DONATION

          The category of the item:

          * `PHYSICAL_GOODS` – Tangible items that can be physically shipped and received with proof of delivery upon arrival.
          * `DIGITAL_GOODS` – Products or services that are distributed and consumed via digital platforms or devices. 
          * `DONATION` – Voluntary contribution made without any goods or services received in return. Multiple line items can be categorized as `DONATION` within a single transaction, however it is not possible to combine `DONATION` other line item categories within the same transaction.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="Shipping" type="object">
      Information about the end user’s shipping address, managed by `ShippingPreference`.

      <Expandable title="properties">
        <ResponseField name="FirstName" type="string">
          The first name of the user.
        </ResponseField>

        <ResponseField name="LastName" type="string">
          Max. length: 100 characters

          The last name of the user.
        </ResponseField>

        <ResponseField name="Address" type="object">
          Information about the shipping address.

          <Expandable title="properties">
            <ResponseField name="AddressLine1" type="string">
              Max. length: 255 characters

              The first line of the address.
            </ResponseField>

            <ResponseField name="AddressLine2" type="string">
              Max. length: 255 characters

              The second line of the address.
            </ResponseField>

            <ResponseField name="City" type="string">
              Max. length: 255 characters

              The city of the address.
            </ResponseField>

            <ResponseField name="Region" type="string">
              Max. length: 255 characters

              The region of the address. This field is optional except if the `Country` is US, CA, or MX.
            </ResponseField>

            <ResponseField name="PostalCode" type="string">
              Max. length: 255 characters

              The postal code of the address. The postal code can contain the following characters: alphanumeric, dashes, and spaces.
            </ResponseField>

            <ResponseField name="Country" type="string">
              Format: Two-letter country code ([ISO 3166-1 alpha-2 format](/api-reference/overview/data-formats))

              The country of the address.
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="Billing" type="object" null>
      Returned `null` because the billing address is not applicable to PayPal preauth.
    </ResponseField>

    <ResponseField name="StatementDescriptor" type="string">
      Max. length: 10 characters; only alphanumeric and spaces

      Custom description to appear on the user’s bank statement along with the platform name. Different banks may show more or less information. See the <a href="/bank-statements">Customizing bank statement references</a> article for details.
    </ResponseField>

    <ResponseField name="RedirectURL" type="string">
      The URL to which to redirect the user to complete the payment.

      **Caution:** This variable URL is specific to each payment. You must rely on the returned URL in full (host, path, and queries) and not hardcode any part of it.
    </ResponseField>

    <ResponseField name="ReturnURL" type="string">
      Max. length: 255 characters

      The URL to which the user is returned after the payment, whether the transaction is successful or not.
    </ResponseField>

    <ResponseField name="ExecutionType" type="string">
      **Returned values:** `WEB`, `DIRECT`, `EXTERNAL_INSTRUCTION`

      The type of execution for the pay-in.
    </ResponseField>

    <ResponseField name="PaymentType" type="string">
      **Returned values:** `PAYPAL`

      The type of pay-in.
    </ResponseField>

    <ResponseField name="Status" type="string">
      **Returned values:** `CREATED`, `SUCCEEDED`, `FAILED`

      The status of the transaction.
    </ResponseField>

    <ResponseField name="Tag" type="string">
      Max. length: 255 characters

      Custom data that you can add to this object.\
      For transactions (pay-in, transfer, payout), you can use this parameter to identify corresponding information regarding the user, transaction, or payment methods on your platform.
    </ResponseField>

    <ResponseField name="ResultMessage" type="string">
      The explanation of the result code.
    </ResponseField>

    <ResponseField name="ResultCode" type="string">
      The code indicating the result of the operation. This information is mostly used to <a href="/errors/codes">handle errors</a> or for filtering purposes.
    </ResponseField>

    <ResponseField name="PayinsLinked" type="object">
      Information about the deposit preauthorized pay-ins made against the deposit preauthorization.

      <Expandable>
        <ResponseField name="PayinCaptureId" type="string">
          The unique identifier of the preauthorized pay-in (capture) made against the deposit preauthorization to debit the preauthorized funds.
        </ResponseField>

        <ResponseField name="PayinComplementId" type="string" deprecated>
          This deprecated parameter is always returned `null`.
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="PaymentStatus" type="string">
      **Returned values:** `WAITING`, `CANCELED`, `CANCEL_REQUESTED`, `EXPIRED`, `VALIDATED`, `FAILED`

      The payment status of the deposit preauthorization object:

      * `WAITING` – The deposit preauthorization can be used: the preauthorized funds can be captured (if `Status` is `SUCCEEDED`) or the preauthorization can be canceled manually.
      * `CANCELED` – Value to pass to manually cancel the deposit preauthorization before use; indicates that the deposit preauthorization was canceled manually.
      * `CANCEL_REQUESTED` – The cancellation of the deposit preauthorization has been requested but not yet processed.
      * `EXPIRED` – The hold period on the preauthorized funds has ended without it being used.
      * `VALIDATED` – Indicates that the preauthorized funds were captured.
      * `FAILED` – The pay-in against the preauthorization has failed, but a retry may be possible.
    </ResponseField>

    <ResponseField name="Status" type="string">
      **Returned values:** `CREATED`, `SUCCEEDED`, `FAILED`

      The status of the authorization.
    </ResponseField>

    <ResponseField name="AuthorId" type="string">
      The unique identifier of the user at the source of the transaction.
    </ResponseField>

    <ResponseField name="DebitedFunds" type="object">
      Information about the preauthorized funds.

      <Expandable title="properties">
        <ResponseField name="Currency" type="string">
          **Returned values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings).

          The currency of the funds.
        </ResponseField>

        <ResponseField name="Amount" type="integer">
          An amount of money in the smallest sub-division of the currency (e.g., EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`).
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="ExpirationDate" type="Unix timestamp">
      The date and time at which the hold period ends and the preauthorized funds are released.\
      At the expiration date, the deposit preauthorization’s `PaymentStatus` changes to `EXPIRED` if no captures were made.
    </ResponseField>

    <ResponseField name="CreationDate" type="Unix timestamp">
      The date and time at which the object was created.
    </ResponseField>

    <ResponseField name="Id" type="string">
      Max. length: 255 characters

      The unique identifier of the PayPal preauthorization.
    </ResponseField>
  </Tab>
</Tabs>

### Related resources

<Card title="Guide" href="/guides/payment-methods/card/deposit-preauthorization">
  Learn more about 30-day preauthorization
</Card>