v1
latestOpenAPI 3.0.02026-07-2436163302.7 KBCredit a transaction
Credit a previously submitted transaction.
Credit note must reference the original debit transaction.
Use /credit endpoint to credit the whole transaction.
Request body
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
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.
The date when the transaction was issued by an external application.
Validations:
- Must be an RFC3339 format date
A text note attached to a transaction. Notes are HTML enabled and will be displayed on the visual document.
Validations:
- Maximum length: 3000
The external transaction identifier of the original transaction the credit is referencing. e.g., MY_ORIGINAL_IDENTIFIER_0001
Validations:
- Maximum length: 150
- Required property
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
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.
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.
RFC3339 datetime string representing the point in time when transaction is executed.
Validations:
- Required property
- Must be an RFC3339 format date
External transaction identifier provided by the customer. e.g., MY_CREDIT_IDENTIFIER_0001
Validations:
- Maximum length: 150
- Required property
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
Example request
{
"note": "This is my HTML <e>enabled</e> note."
}Response
Accepted - transaction was successfully submitted for processing.
Information about the failure reason in case the request was unsuccessful.
Auto-generated unique identifier of a transaction operation returned upon async operation request.
The unique external transaction identifier provided with the initial request.