Montran · Schema
CreditTransferInitiation
Credit transfer initiation request aligned with ISO 20022 pain.001 CustomerCreditTransferInitiation
BankingCentral BankingFinancial-ServicesISO 20022Market InfrastructureMessagingPaymentsReal-Time PaymentsSwift
Properties
| Name | Type | Description |
|---|---|---|
| messageId | string | Unique message identification |
| paymentInformationId | string | Payment information identification |
| numberOfTransactions | integer | Number of individual transactions in the message |
| controlSum | number | Total of all individual amounts |
| debtorName | string | Name of the debtor |
| debtorAccount | object | |
| debtorAgent | object | |
| creditorName | string | Name of the creditor |
| creditorAccount | object | |
| creditorAgent | object | |
| amount | number | Instructed amount |
| currency | string | ISO 4217 currency code |
| requestedExecutionDate | string | Requested execution date |
| endToEndId | string | End-to-end identification |
| remittanceInformation | string | Remittance information |
| chargeBearer | string | |
| categoryPurpose | string | Category purpose code for the payment |
| serviceLevel | string | Service level code (e.g., SEPA for SEPA payments) |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/CreditTransferInitiation",
"title": "CreditTransferInitiation",
"type": "object",
"description": "Credit transfer initiation request aligned with ISO 20022 pain.001 CustomerCreditTransferInitiation",
"required": [
"debtorAccount",
"creditorAccount",
"amount",
"currency"
],
"properties": {
"messageId": {
"type": "string",
"description": "Unique message identification"
},
"paymentInformationId": {
"type": "string",
"description": "Payment information identification"
},
"numberOfTransactions": {
"type": "integer",
"description": "Number of individual transactions in the message"
},
"controlSum": {
"type": "number",
"format": "double",
"description": "Total of all individual amounts"
},
"debtorName": {
"type": "string",
"description": "Name of the debtor"
},
"debtorAccount": {
"$ref": "#/components/schemas/AccountIdentification"
},
"debtorAgent": {
"$ref": "#/components/schemas/FinancialInstitution"
},
"creditorName": {
"type": "string",
"description": "Name of the creditor"
},
"creditorAccount": {
"$ref": "#/components/schemas/AccountIdentification"
},
"creditorAgent": {
"$ref": "#/components/schemas/FinancialInstitution"
},
"amount": {
"type": "number",
"format": "double",
"description": "Instructed amount",
"minimum": 0.01
},
"currency": {
"type": "string",
"description": "ISO 4217 currency code",
"pattern": "^[A-Z]{3}$"
},
"requestedExecutionDate": {
"type": "string",
"format": "date",
"description": "Requested execution date"
},
"endToEndId": {
"type": "string",
"description": "End-to-end identification"
},
"remittanceInformation": {
"type": "string",
"description": "Remittance information"
},
"chargeBearer": {
"type": "string",
"enum": [
"DEBT",
"CRED",
"SHAR",
"SLEV"
]
},
"categoryPurpose": {
"type": "string",
"description": "Category purpose code for the payment"
},
"serviceLevel": {
"type": "string",
"description": "Service level code (e.g., SEPA for SEPA payments)"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/montran-credittransferinitiation"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.