Groupe BPCE · Schema
HalPaymentCoverageReport
HYPERMEDIA structure used for returning the payment coverage report to the CBPII
CompanyBankingFinancial ServicesOpen BankingPSD2PaymentsInsuranceFrance
Properties
| Name | Type | Description |
|---|---|---|
| request | object | |
| result | boolean | Result of the coverage check : - true: the payment can be covered - false: the payment cannot be covered |
| _links | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/groupe-bpce/main/json-schema/groupe-bpce-hal-payment-coverage-report-schema.json",
"title": "HalPaymentCoverageReport",
"description": "HYPERMEDIA structure used for returning the payment coverage report to the CBPII",
"x-generated": "2026-10-09",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/groupe-bpce-psd2-funds-availability-openapi.yml#/components/schemas/HalPaymentCoverageReport",
"type": "object",
"properties": {
"request": {
"$ref": "#/$defs/PaymentCoverageRequestResource"
},
"result": {
"description": "Result of the coverage check :\n- true: the payment can be covered\n- false: the payment cannot be covered\n",
"type": "boolean"
},
"_links": {
"$ref": "#/$defs/PaymentCoverageReportLinks"
}
},
"required": [
"request",
"result",
"_links"
],
"$defs": {
"AccountIdentification": {
"description": "Unique and unambiguous identification for the account between the account owner and the account servicer.\nCard accounts must provide the identification of the card through the \"other\" substructure by giving, for instance, the masked PAN (MPAN).\nThe currency used for the account, when needed, can be specified through the [currency] field.\n",
"type": "object",
"properties": {
"workspace": {
"description": "Workspace to which the account is linked.\nThis workspace might be specified by the AISP when forwarding the consent on accounts.\nIf not provided, the default workspace is computed from the authentication that was used for getting the OAuth2 Access Token.\n",
"type": "string",
"maxLength": 32
},
"iban": {
"description": "ISO20022: International Bank Account Number (IBAN) - identification used internationally by financial institutions to uniquely identify the account of a customer.\n\nFurther specifications of the format and content of the IBAN can be found in the standard ISO 13616 \"Banking and related financial services - International Bank Account Number (IBAN)\" version 1997-10-01, or later revisions.\n",
"type": "string",
"pattern": "^[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}$"
},
"other": {
"$ref": "#/$defs/GenericIdentification"
},
"currency": {
"$ref": "#/$defs/CurrencyCode"
}
}
},
"AmountType": {
"description": "Structure aiming to embed the amount and the currency to be used.\n",
"type": "object",
"properties": {
"amount": {
"description": "ISO20022: Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.\n",
"type": "number",
"format": "float",
"pattern": "^\\-{0,1}[0-9]{1,13}(\\.[0-9]{0,5}){0,1}$"
},
"currency": {
"$ref": "#/$defs/CurrencyCode"
}
},
"required": [
"amount",
"currency"
]
},
"CurrencyCode": {
"description": "Specifies the currency of the amount or of the account.\nA code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international standard ISO 4217 \"Codes for the representation of currencies and funds\".\n",
"type": "string",
"pattern": "^[A-Z]{3,3}$"
},
"GenericIdentification": {
"description": "ISO20022: Unique identification of an account, a person or an organisation, as assigned by an issuer.\nAPI: The ASPSP will document which account reference type it will support.\n",
"type": "object",
"properties": {
"identification": {
"description": "API: Identifier\n",
"type": "string",
"maxLength": 70
},
"schemeName": {
"description": "Name of the identification scheme.\nPossible values for the scheme name, partially based on ISO20022 external code list, are the following:\n| Code | Name | Description |\n| ---- | ---- | ----------- |\n| BANK | BankPartyIdentification | Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. |\n| BBAN | BBANIdentifier | Basic Bank Account Number (BBAN) - identifier used nationally by financial institutions, ie, in individual countries, generally as part of a National Account Numbering Scheme(s), to uniquely identify the account of a customer. |\n| COID | CountryIdentificationCode) : Country authority given organisation identification (e.g., corporate registration number) |\n| SREN | SIREN | The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. |\n| SRET | SIRET | The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. |\n| NIDN | NationalIdentityNumber | Number assigned by an authority to identify the national identity number of a person. |\nOther values are also permitted, for instance:\n| Code | Name | Description |\n| ---- | ---- | ----------- |\n| OAUT | OAUTH2 | OAUTH2 access token that is owned by the PISP being also an AISP and that can be used in order to identify the PSU |\n| CPAN | CardPan | Card PAN |\n| MPAN | MaskedPan | Card PAN where some digits were replaced for security reason |\n| TPAN | TokenizedPan | Token which was provided by a Token Service Provider (TSP) in order to obfuscate a real card PAN. The TSP must be identified in the issuer field |\n| TBAN | TokenizedIBAN | Token which was provided by a Token Service Provider (TSP) in order to obfuscate an IBAN. The TSP must be identified in the issuer field |\nEach implementation of the STET PSD2 API must specify in its own documentation which schemes can actually been used\n",
"type": "string",
"maxLength": 70
},
"issuer": {
"description": "ISO20022: Entity that assigns the identification. this could a country code or any organisation name or identifier that can be recognized by both parties\n",
"type": "string",
"maxLength": 35
}
},
"required": [
"identification",
"schemeName"
]
},
"GenericLink": {
"description": "hypertext reference",
"type": "object",
"properties": {
"href": {
"description": "URI to be used. HREF stands for Hypertext REFerence.",
"type": "string",
"maxLength": 2000
},
"templated": {
"description": "This field must be set with \"true\" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570.\nOtherwise, this property must be absent or set to false\ndefault value: false\n",
"type": "boolean"
}
},
"required": [
"href"
]
},
"PaymentCoverageReportLinks": {
"description": "links that can be used for further navigation to post another coverage request.\n",
"type": "object",
"properties": {
"self": {
"$ref": "#/$defs/GenericLink"
}
},
"required": [
"self"
],
"readOnly": true
},
"PaymentCoverageRequestResource": {
"description": "Payment coverage request structure.\nThe request must rely either on a cash account or a payment card.\nThe [instructedAmount] property is the payment account on wihich the request is processed. This amount must be positive.\nAmounts must always be set as positive values.\n",
"type": "object",
"properties": {
"paymentCoverageRequestId": {
"description": "Identification of the payment Coverage Request",
"type": "string",
"maxLength": 35
},
"payee": {
"description": "The merchant where the card is accepted as information to the PSU.",
"type": "string",
"maxLength": 70
},
"instructedAmount": {
"$ref": "#/$defs/AmountType"
},
"accountId": {
"$ref": "#/$defs/AccountIdentification"
}
},
"required": [
"paymentCoverageRequestId",
"accountId"
]
}
}
}
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/groupe-bpce-hal-payment-coverage-report"
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.