--- title: "Get details of a withdrawal charge" method: GET path: "/lifetime-isa/manager/{lisaManagerReferenceNumber}/accounts/{accountId}/withdrawal-charges/{transactionId}" tags: ["Withdrawal Charges"] --- # Get details of a withdrawal charge `GET /lifetime-isa/manager/{lisaManagerReferenceNumber}/accounts/{accountId}/withdrawal-charges/{transactionId}` Use an investor’s transaction ID to get a request for a withdrawal charge that has been submitted to HMRC. ### Test data
Scenario Response

Withdrawal transaction which has been superseded

lisaManagerReferenceNumber:
Use your test user profile

accountId:
1234567890
transactionId:
2345678901

HTTP status: 200 (OK)

{
  "claimPeriodStartDate": "2017-12-06",
  "claimPeriodEndDate": "2018-01-05",
  "automaticRecoveryAmount": 250,
  "withdrawalAmount": 1000,
  "withdrawalChargeAmount": 250,
  "withdrawalChargeAmountYTD": 500,
  "fundsDeductedDuringWithdrawal": true,
  "withdrawalReason": "Regular withdrawal",
  "supersededBy": "2345678903"
}

Withdrawal transaction which has not been superseded

lisaManagerReferenceNumber:
Use your test user profile

accountId:
1234567890
transactionId:
2345678902

HTTP status: 200 (OK)

{
  "claimPeriodStartDate": "2017-12-06",
  "claimPeriodEndDate": "2018-01-05",
  "automaticRecoveryAmount": 250,
  "withdrawalAmount": 1000,
  "withdrawalChargeAmount": 250,
  "withdrawalChargeAmountYTD": 500,
  "fundsDeductedDuringWithdrawal": true,
  "withdrawalReason": "Regular withdrawal"
}

Withdrawal transaction which supersedes another

lisaManagerReferenceNumber:
Use your test user profile

accountId:
1234567890
transactionId:
2345678903

HTTP status: 200 (OK)

{
  "claimPeriodStartDate": "2017-12-06",
  "claimPeriodEndDate": "2018-01-05",
  "automaticRecoveryAmount": 250,
  "withdrawalAmount": 2000,
  "withdrawalChargeAmount": 500,
  "withdrawalChargeAmountYTD": 750,
  "fundsDeductedDuringWithdrawal": true,
  "withdrawalReason": "Superseded withdrawal",
  "supersede": {
    "originalTransactionId": "2345678901",
    "originalWithdrawalChargeAmount": 250,
    "transactionResult": 250,
    "reason": "Additional withdrawal"
  }
}

Invalid LISA Manager Reference Number

lisaManagerReferenceNumber:
123456

accountId:
1234567890
transactionId:
2345678901

HTTP status: 400 (Bad Request)

{
  "code": "BAD_REQUEST",
  "message": "Enter lisaManagerReferenceNumber in the correct format, like Z1234"
}

Invalid Account ID

lisaManagerReferenceNumber:
Use your test user profile

accountId:
1234%3D5678
transactionId:
2345678901

HTTP status: 400 (Bad Request)

{
  "code": "BAD_REQUEST",
  "message": "Enter accountId in the correct format, like ABC12345"
}

Account ID does not exist

lisaManagerReferenceNumber:
Use your test user profile

accountId:
1234567890
transactionId:
1000000404

HTTP status: 404 (Not Found)

{
  "code": "INVESTOR_ACCOUNTID_NOT_FOUND",
  "message": "Enter a real accountId"
}

Transaction ID does not exist

lisaManagerReferenceNumber:
Use your test user profile

accountId:
1234567890
transactionId:
0000000404

HTTP status: 404 (Not Found)

{
  "code": "WITHDRAWAL_CHARGE_TRANSACTION_NOT_FOUND",
  "message": "transactionId does not match HMRC’s records"
}
## Path parameters - `lisaManagerReferenceNumber` string, required - `accountId` string, required - `transactionId` string, required ## Headers - `Accept` 'application/vnd.hmrc.2.0+json', required - `Authorization` string, required ## Response `200` OK - object - `claimPeriodStartDate` string, required — This is the start date of the claim period for the withdrawal charge. It must be the sixth day of the month. You cannot enter a date in the future. - `claimPeriodEndDate` string, required — This is the end date of the claim period for the withdrawal charge. It must be the fifth day of the month. It has to be the month after the claimPeriodStartDate. - `automaticRecoveryAmount` number — This is the amount HMRC can collect from the LISA manager when there is a withdrawal charge. If there are no funds available, this value must be 0. - `withdrawalAmount` number, required — This is the amount that the investor has withdrawn from the LISA account. - `withdrawalChargeAmount` number, required — This is the amount charged for the withdrawal. - `withdrawalChargeAmountYTD` number, required — This is the total value of withdrawal charges reported to HMRC for the current tax year to date. - `fundsDeductedDuringWithdrawal` boolean, required — This confirms if the investor was charged and funds were deducted at the time of the withdrawal. - `withdrawalReason` 'Regular withdrawal' | 'Superseded withdrawal', required — This is used by HMRC to decide how the withdrawal charge is processed. - `supersededBy` string — The ID of the transaction that supersedes the current one. - `supersede` object — Correct an existing withdrawal charge. You can request an additional charge, reduce a charge, or refund a charge. - `originalTransactionId` string, required — The transactionId of the original withdrawal charge affected by the correction or recovery. This is used together with the originalWithdrawalChargeAmount to make sure the right charge is replaced. - `originalWithdrawalChargeAmount` number, required — This is how much was in the withdrawalChargeAmount in the original request. - `transactionResult` number, required — The amount to be added to or recovered from the original withdrawal charge. - `reason` 'Additional withdrawal' | 'Withdrawal reduction' | 'Withdrawal refund', required — Confirm whether an additional charge is due or whether the investor is owed some money. ## Other responses - `400` — Bad Request - `401` — Unauthorized - `404` — Not Found --- [API](https://skmtc.net/hmrc/apis/lisa-api.md) · [All operations](https://skmtc.net/hmrc/apis/lisa-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hmrc/lisa-api/revisions/689ca71752fb/schema)