---
title: "Credit a transaction"
method: POST
path: "/v1/transactions/credit"
---

# Credit a transaction

`POST /v1/transactions/credit`

Credit a previously submitted transaction.

Credit note must reference the original debit transaction.

Use /credit endpoint to credit the whole transaction.

## Request body

- TransactionCreditRequest
  - `country_code` string, required — ISO 3166-1 alpha-2 uppercase country code the transaction is taking place in. Validations: - Country code must be uppercase ISO 3166-1 alpha-2. - Required property
  - `country_subdivision_code` string — ISO 3166-2 uppercase code of the principal country subdivision (province, state, region) the transaction is taking place in. Validations: - Values allowed are (letter case matters): AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT - Country subdivision code is only supported for Canada.
  - `issue_date` string — The date when the transaction was issued by an external application. Validations: - Must be an RFC3339 format date
  - `note` string — A text note attached to a transaction. Notes are HTML enabled and will be displayed on the visual document. Validations: - Maximum length: 3000
  - `reference_transaction_id` string, required — The external transaction identifier of the original transaction the credit is referencing. e.g., MY_ORIGINAL_IDENTIFIER_0001 Validations: - Maximum length: 150 - Required property
  - `series` string — A pool of transaction numbers issued by tax authorities to pick the transaction number from. The transaction shall be assigned one of the numbers from this pool when reporting it to the tax authorities. Usually series can be opened and closed at any time and there can be multiple open series at the same time. e.g., 2022_01 Validations: - Maximum length: 20
  - `tax_authority_id_1` string — Main transaction identifier returned by or to be provided to the tax authorities. e.g., JIR in Croatia. Validations: - This field is only supported in specific use cases, refer to country-specific integration guides in the Fonoa dashboard.
  - `tax_authority_id_2` string — Secondary transaction identifier returned by or to be provided to the tax authorities. e.g., ZKI in Croatia. Validations: - This field is only supported in specific use cases, refer to country-specific integration guides in the Fonoa dashboard.
  - `transaction_date` string, required — RFC3339 datetime string representing the point in time when transaction is executed. Validations: - Required property - Must be an RFC3339 format date
  - `transaction_id` string, required — External transaction identifier provided by the customer. e.g., MY_CREDIT_IDENTIFIER_0001 Validations: - Maximum length: 150 - Required property
  - `transaction_number` string — Unique and usually sequential identifier of a transaction displayed on the document and reported to tax authorities. e.g., invoice number for debit scenario or credit note number for credit scenario. e.g., IE00000001 Validations: - Maximum length: 50

## Response `202`

Accepted - transaction was successfully submitted for processing.

- OperationResultResponse
  - `errors` TransactionErrorResponse[] — List of errors in case the request was unsuccessful.
    - `code` string — Error code of the issue. e.g., field_not_valid
    - `doc_link` string — The link for the error documentation. Follow it to gather more details about the error
    - `field` string — Field from the input request that caused the error, in case of validation errors. e.g. transaction_date
    - `message` string — Error message of the issue. e.g., Date must be in RFC3339 format.
    - `type` string — Error type of the issue. e.g., warning, validation, general, tax_authority
  - `message` string — Information about the failure reason in case the request was unsuccessful.
  - `operation_id` string — Auto-generated unique identifier of a transaction operation returned upon async operation request.
  - `transaction_id` string — The unique external transaction identifier provided with the initial request.

## Other responses

- `400` — Bad customer request - some of the provided information is incorrect or mandatory data is missing. Check the message and errors section of the response for more details.
- `401` — Authentication failed - missing or incorrect subscription key
- `429` — Too many requests were sent for a short period of time. Try again a bit later.
- `5XX` — Internal server error. Its not you, its us! We are experiencing a rare and unexpected system disruption. Retry again later. The message field of the response will contain more information for the cause. Feel free to contact us.

---

[API](https://skmtc.net/fonoa/apis/fonoa-api.md) · [All operations](https://skmtc.net/fonoa/apis/fonoa-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fonoa/fonoa-api/versions/cf0ebc843a3f/schema)