Target-2-Payments API

Target-2-Payments API 1.3.2

0
No votes yet
Payment Initiation Service (PIS) Common Services
production
development
https://api.rba.hr

Paths

/{payment-service}/{payment-product}

post /{payment-service}/{payment-product}

Payment initiation request

This method is used to initiate a payment.

clientIdHeader
X-IBM-Client-Id
(apiKey located in header)
payment-service
Required in path
string
{
    "enum": [
        "payments"
    ]
}
payment-product
Required in path
string
{
    "enum": [
        "target-2-payments"
    ]
}
X-Request-ID
Required in header
string / uuid

ID of the request, unique to the call, as determined by the initiating party.

PSU-IP-Address
Required in header
string

The forwarded IP Address header field consists of the corresponding http request IP Address field between PSU and TPP.

body
Required in body
object

JSON request body for a payment inition request message

paymentInitiationTarget
Digest
Optional in header
string

Is contained if and only if the "Signature" element is contained in the header of the request.

Signature
Optional in header
string

A signature of the request by the TPP on application level. This might be mandated by ASPSP.

TPP-Signature-Certificate
Optional in header
string

The certificate used for signing the request, in base64 encoding. Must be contained if a signature is contained.

PSU-ID
Optional in header
string

Client ID of the PSU in the ASPSP client interface. Might be mandated in the ASPSP's documentation. Is not contained if an OAuth2 based authentication was performed in a pre-step or an OAuth2 based SCA was performed in an preceeding AIS service in the same session.

PSU-ID-Type
Optional in header
string

Type of the PSU-ID, needed in scenarios where PSUs have several PSU-IDs as access possibility.

PSU-Corporate-ID
Optional in header
string

Might be mandated in the ASPSP's documentation. Only used in a corporate context.

PSU-Corporate-ID-Type
Optional in header
string

Might be mandated in the ASPSP's documentation. Only used in a corporate context.

Consent-ID
Optional in header
string

This data element may be contained, if the payment initiation transaction is part of a session, i.e. combined AIS/PIS service. This then contains the consentId of the related AIS consent, which was performed prior to this payment initiation.

TPP-Redirect-Preferred
Optional in header
string

If it equals "true", the TPP prefers a redirect over an embedded SCA approach. If it equals "false", the TPP prefers not to be redirected for SCA. The ASPSP will then choose between the Embedded or the Decoupled SCA approach, depending on the choice of the SCA procedure by the TPP/PSU. If the parameter is not used, the ASPSP will choose the SCA approach to be applied depending on the SCA method chosen by the TPP/PSU.

{
    "enum": [
        "true",
        "false"
    ]
}
TPP-Redirect-URI
Optional in header
string

URI of the TPP, where the transaction flow shall be redirected to after a Redirect.

Mandated for the Redirect SCA Approach (including OAuth2 SCA approach), specifically when TPP-Redirect-Preferred equals "true". It is recommended to always use this header field.

Remark for Future: This field might be changed to mandatory in the next version of the specification.

TPP-Nok-Redirect-URI
Optional in header
string

If this URI is contained, the TPP is asking to redirect the transaction flow to this address instead of the TPP-Redirect-URI in case of a negative result of the redirect SCA method. This might be ignored by the ASPSP.

TPP-Explicit-Authorisation-Preferred
Optional in header
string

If it equals "true", the TPP prefers to start the authorisation process separately, e.g. because of the usage of a signing basket. This preference might be ignored by the ASPSP, if a signing basket is not supported as functionality.

If it equals "false" or if the parameter is not used, there is no preference of the TPP. This especially indicates that the TPP assumes a direct authorisation of the transaction in the next step, without using a signing basket.

{
    "enum": [
        "true",
        "false"
    ]
}
TPP-Rejection-NoFunds-Preferred
Optional in header
string

If it equals "true" then the TPP prefers a rejection of the payment initiation in case the ASPSP is providing an integrated confirmation of funds request an the result of this is that not sufficient funds are available. If it equals "false" then the TPP prefers that the ASPSP is dealing with the payment initiation like in the ASPSPs online channel, potentially waiting for a certain time period for funds to arrive to initiate the payment.This parameter might be ignored by the ASPSP.

{
    "enum": [
        "true",
        "false"
    ]
}
PSU-IP-Port
Optional in header
string

The forwarded IP Port header field consists of the corresponding HTTP request IP Port field between PSU and TPP, if available.

PSU-Accept
Optional in header
string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-Accept-Charset
Optional in header
string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-Accept-Encoding
Optional in header
string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-Accept-Language
Optional in header
string

The forwarded IP Accept header fields consist of the corresponding HTTP request Accept header fields between PSU and TPP, if available.

PSU-User-Agent
Optional in header
string

The forwarded Agent header field of the HTTP request between PSU and TPP, if available.

PSU-Http-Method
Optional in header
string

HTTP method used at the PSU ? TPP interface, if available. Valid values are:

  • GET
  • POST
  • PUT
  • PATCH
  • DELETE
{
    "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE"
    ]
}
PSU-Device-ID
Optional in header
string / uuid

UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID need to be unaltered until removal from device.

PSU-Geo-Location
Optional in header
string

The forwarded Geo Location of the corresponding http request between PSU and TPP if available.

{
    "pattern": "GEO:-?[0-9]{1,2}\\.[0-9]{6};-?[0-9]{1,3}\\.[0-9]{6}"
}
Content-Type
Optional in header
string
application/json
Accept
Optional in header
string
application/json
201

CREATED

{
    "schema": {
        "type": "object"
    },
    "examples": {
        "application\/json": "{\"description\":\"Response in case of a redirect with an implicitly created authorisation sub-resource\",\"value\":{\"transactionStatus\":\"RCVD\",\"paymentId\":\"1234-wertiq-983\",\"_links\":{\"scaRedirect\":{\"href\":\"https:\/\/www.testbank.com\/asdfasdfasdf\"},\"self\":{\"href\":\"\/v1\/payments\/sepa-credit-transfers\/1234-wertiq-983\"},\"status\":{\"href\":\"\/v1\/payments\/1234-wertiq-983\/status\"},\"scaStatus\":{\"href\":\"\/v1\/payments\/1234-wertiq-983\/authorisations\/123auth456\"}}}}"
    },
    "headers": {
        "X-Request-ID": {
            "type": "string",
            "default": "99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
        },
        "Location": {
            "type": "string"
        },
        "ASPSP-SCA-Approach": {
            "type": "string",
            "default": "EMBEDDED"
        }
    }
}
400

Bad Request

Error400_NG_PIS
401

Unauthorized

Error401_NG_PIS
403

Forbidden

Error403_NG_PIS
404

Not found

Error404_NG_PIS
405

Method Not Allowed

Error405_NG_PIS
406

Not Acceptable

408

Request Timeout

409

Conflict

Error409_NG_PIS
415

Unsuported Media Type

429

Too Many Requests

500

Internal Server Error

503

Service Unavailable

Example Request
Example Response
POST https://api.rba.hr/psd2-target-2-payments-api-1.3.2/v1/{payment-service}/{payment-product}
Try this operation
https://api.rba.hr/psd2-target-2-payments-api-1.3.2/v1/{payment-service}/{payment-product}
content-type
accept
X-Request-ID
PSU-IP-Address
Digest
Signature
TPP-Signature-Certificate
PSU-ID
PSU-ID-Type
PSU-Corporate-ID
PSU-Corporate-ID-Type
Consent-ID
TPP-Redirect-Preferred
TPP-Redirect-URI
TPP-Nok-Redirect-URI
TPP-Explicit-Authorisation-Preferred
TPP-Rejection-NoFunds-Preferred
PSU-IP-Port
PSU-Accept
PSU-Accept-Charset
PSU-Accept-Encoding
PSU-Accept-Language
PSU-User-Agent
PSU-Http-Method
PSU-Device-ID
PSU-Geo-Location
payment-service
payment-product

Definitions

Body for a target-2-payments initation via JSON.

{
    "title": "paymentInitiationTarget",
    "type": "object",
    "required": [
        "debtorAccount",
        "instructedAmount",
        "creditorAccount",
        "creditorName"
    ],
    "properties": {
        "endToEndIdentification": {
            "$ref": "#/definitions/endToEndIdentification"
        },
        "debtorName": {
            "$ref": "#/definitions/debtorName"
        },
        "debtorAccount": {
            "$ref": "#/definitions/accountReference"
        },
        "instructedAmount": {
            "$ref": "#/definitions/amount"
        },
        "creditorAccount": {
            "$ref": "#/definitions/accountReference"
        },
        "creditorAgent": {
            "$ref": "#/definitions/bicfi"
        },
        "creditorName": {
            "$ref": "#/definitions/creditorName"
        },
        "creditorAddress": {
            "$ref": "#/definitions/address"
        },
        "chargeBearer": {
            "$ref": "#/definitions/chargeBearer"
        },
        "remittanceInformationUnstructured": {
            "$ref": "#/definitions/remittanceInformationUnstructured"
        },
        "requestedExecutionDate": {
            "$ref": "#/definitions/requestedExecutionDate"
        }
    }
}

Creditor Name

{
    "type": "string",
    "maxLength": 70,
    "example": "Creditor Name"
}

Reference as contained in the structured remittance reference structure (without the surrounding XML structure).

{
    "type": "object",
    "required": [
        "reference"
    ],
    "properties": {
        "reference": {
            "type": "string",
            "maxLength": 35
        },
        "referenceType": {
            "type": "string",
            "maxLength": 35
        },
        "referenceIssuer": {
            "type": "string",
            "maxLength": 35
        }
    }
}

Unstructured remittance information.

{
    "type": "string",
    "maxLength": 140,
    "example": "Ref Number Merchant"
}
              
{
    "type": "string",
    "maxLength": 35
}
              
{
    "type": "string",
    "maxLength": 70,
    "example": "Debtor Name"
}
              
{
    "type": "string",
    "format": "date",
    "example": "2019-10-10"
}

Reference to an account by either

  • IBAN, of a payment accounts, or
  • BBAN, for payment accounts if there is no IBAN, or
  • the Primary Account Number (PAN) of a card, can be tokenised by the ASPSP due to PCI DSS requirements, or
  • the Primary Account Number (PAN) of a card in a masked form, or
  • an alias to access a payment account via a registered mobile phone number (MSISDN).
{
    "title": "accountReference",
    "type": "object",
    "properties": {
        "iban": {
            "description": "IBAN of an account",
            "example": "FR7612345987650123456789014",
            "type": "string",
            "pattern": "[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}"
        },
        "bban": {
            "description": "Basic Bank Account Number (BBAN) Identifier\n\nThis data element can be used in the body of the Consent Request\n  Message for retrieving Account access Consent from this Account. This\n  data elements is used for payment Accounts which have no IBAN.\n  ISO20022: Basic Bank Account Number (BBAN). \n  \n  Identifier used nationally by financial institutions, i.e., in individual countries, \n  generally as part of a National Account Numbering Scheme(s), \n  which uniquely identifies the account of a customer.",
            "example": "BARC12345612345678",
            "type": "string",
            "pattern": "[a-zA-Z0-9]{1,30}"
        },
        "pan": {
            "description": "Primary Account Number according to ISO/IEC 7812.",
            "example": "5409050000000000",
            "type": "string",
            "maxLength": 35
        },
        "maskedPan": {
            "description": "Masked Primary Account Number",
            "example": "123456xxxxxx1234",
            "type": "string",
            "maxLength": 35
        },
        "msisdn": {
            "description": "Mobile phone number.",
            "example": "+49 170 1234567",
            "type": "string",
            "maxLength": 35
        },
        "currency": {
            "description": "ISO 4217 Alpha 3 currency code",
            "example": "EUR",
            "type": "string",
            "pattern": "[A-Z]{3}"
        }
    }
}
              
{
    "title": "address",
    "example": {
        "street": "rue blue",
        "buildingNumber": "89",
        "city": "Paris",
        "postalCode": "75000",
        "country": "FR"
    },
    "type": "object",
    "properties": {
        "street": {
            "type": "string",
            "maxLength": 70
        },
        "buildingNumber": {
            "type": "string"
        },
        "city": {
            "type": "string"
        },
        "postalCode": {
            "type": "string"
        },
        "country": {
            "description": "ISO 3166 ALPHA2 country code",
            "example": "SE",
            "type": "string",
            "pattern": "[A-Z]{2}"
        }
    },
    "required": [
        "country"
    ]
}
              
{
    "title": "amount",
    "example": {
        "currency": "EUR",
        "amount": "123"
    },
    "type": "object",
    "properties": {
        "currency": {
            "description": "ISO 4217 Alpha 3 currency code",
            "example": "EUR",
            "type": "string",
            "pattern": "[A-Z]{3}"
        },
        "amount": {
            "description": "The amount given with fractional digits, where fractions must be compliant to the currency definition.\nUp to 14 significant figures. Negative amounts are signed by minus.\nThe decimal separator is a dot.\n\n**Example:**\nValid representations for EUR with up to two decimals are:\n\n  * 1056\n  * 5768.2\n  * -1.50\n  * 5877.78",
            "example": "5877.78",
            "type": "string",
            "pattern": "-?[0-9]{1,14}(\\.[0-9]{1,3})?"
        }
    },
    "required": [
        "currency",
        "amount"
    ]
}

BICFI

{
    "type": "string",
    "pattern": "[A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}",
    "example": "AAAADEBBXXX"
}

Charge Bearer. ChargeBearerType1Code from ISO20022

{
    "type": "string",
    "enum": [
        "DEBT",
        "CRED",
        "SHAR",
        "SLEV"
    ]
}

A _link object with all availabel link types

{
    "title": "_linksAll",
    "type": "object",
    "properties": {
        "scaRedirect": {
            "$ref": "#/definitions/hrefType"
        },
        "scaOAuth": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisation": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisationWithPsuIdentification": {
            "$ref": "#/definitions/hrefType"
        },
        "updatePsuIdentification": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisationWithProprietaryData": {
            "$ref": "#/definitions/hrefType"
        },
        "updateProprietaryData": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisationWithPsuAuthentication": {
            "$ref": "#/definitions/hrefType"
        },
        "updatePsuAuthentication": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisationWithEncryptedPsuAuthentication": {
            "$ref": "#/definitions/hrefType"
        },
        "updateEncryptedPsuAuthentication": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisationWithAuthenticationMethodSelection": {
            "$ref": "#/definitions/hrefType"
        },
        "selectAuthenticationMethod": {
            "$ref": "#/definitions/hrefType"
        },
        "startAuthorisationWithTransactionAuthorisation": {
            "$ref": "#/definitions/hrefType"
        },
        "authoriseTransaction": {
            "$ref": "#/definitions/hrefType"
        },
        "self": {
            "$ref": "#/definitions/hrefType"
        },
        "status": {
            "$ref": "#/definitions/hrefType"
        },
        "scaStatus": {
            "$ref": "#/definitions/hrefType"
        },
        "account": {
            "$ref": "#/definitions/hrefType"
        },
        "balances": {
            "$ref": "#/definitions/hrefType"
        },
        "transactions": {
            "$ref": "#/definitions/hrefType"
        },
        "transactionDetails": {
            "$ref": "#/definitions/hrefType"
        },
        "cardAccount": {
            "$ref": "#/definitions/hrefType"
        },
        "cardTransactions": {
            "$ref": "#/definitions/hrefType"
        },
        "first": {
            "$ref": "#/definitions/hrefType"
        },
        "next": {
            "$ref": "#/definitions/hrefType"
        },
        "previous": {
            "$ref": "#/definitions/hrefType"
        },
        "last": {
            "$ref": "#/definitions/hrefType"
        },
        "download": {
            "$ref": "#/definitions/hrefType"
        }
    }
}

Category of the TPP message category

{
    "title": "tppMessageCategory",
    "example": "ERROR",
    "type": "string",
    "enum": [
        "ERROR",
        "WARNING"
    ]
}

Message codes defined for PIS for HTTP Error code 400 (BAD_REQUEST).

{
    "title": "MessageCode400_PIS",
    "example": "FORMAT_ERROR",
    "type": "string",
    "enum": [
        "FORMAT_ERROR",
        "PARAMETER_NOT_CONSISTENT",
        "PARAMETER_NOT_SUPPORTED",
        "SERVICE_INVALID",
        "RESOURCE_UNKNOWN",
        "RESOURCE_EXPIRED",
        "RESOURCE_BLOCKED",
        "TIMESTAMP_INVALID",
        "PERIOD_INVALID",
        "SCA_METHOD_UNKNOWN",
        "CONSENT_UNKNOWN",
        "PAYMENT_FAILED",
        "EXECUTION_DATE_INVALID"
    ]
}

Message codes defined for PIS for HTTP Error code 401 (UNAUTHORIZED).

{
    "title": "MessageCode401_PIS",
    "example": "CERTIFICATE_INVALID",
    "type": "string",
    "enum": [
        "CERTIFICATE_INVALID",
        "CERTIFICATE_EXPIRED",
        "CERTIFICATE_BLOCKED",
        "CERTIFICATE_REVOKE",
        "CERTIFICATE_MISSING",
        "SIGNATURE_INVALID",
        "SIGNATURE_MISSING",
        "CORPORATE_ID_INVALID",
        "PSU_CREDENTIALS_INVALID",
        "CONSENT_INVALID",
        "CONSENT_EXPIRED",
        "TOKEN_UNKNOWN",
        "TOKEN_INVALID",
        "TOKEN_EXPIRED",
        "REQUIRED_KID_MISSING"
    ]
}

Message codes defined defined for PIS for PIS for HTTP Error code 403 (FORBIDDEN).

{
    "title": "MessageCode403_PIS",
    "example": "CONSENT_UNKNOWN",
    "type": "string",
    "enum": [
        "CONSENT_UNKNOWN",
        "SERVICE_BLOCKED",
        "RESOURCE_UNKNOWN",
        "RESOURCE_EXPIRED",
        "PRODUCT_INVALID"
    ]
}

Message codes defined for PIS for HTTP Error code 404 (NOT FOUND).

{
    "title": "MessageCode404_PIS",
    "example": "RESOURCE_UNKNOWN",
    "type": "string",
    "enum": [
        "RESOURCE_UNKNOWN",
        "PRODUCT_UNKNOWN"
    ]
}
              
{
    "title": "tppMessage400_PIS",
    "type": "object",
    "properties": {
        "category": {
            "$ref": "#/definitions/tppMessageCategory"
        },
        "code": {
            "$ref": "#/definitions/MessageCode400_PIS"
        },
        "path": {
            "type": "string"
        },
        "text": {
            "description": "Additional explaining text to the TPP.",
            "type": "string",
            "maxLength": 512
        }
    },
    "required": [
        "category",
        "code"
    ]
}
              
{
    "title": "tppMessage401_PIS",
    "type": "object",
    "properties": {
        "category": {
            "$ref": "#/definitions/tppMessageCategory"
        },
        "code": {
            "$ref": "#/definitions/MessageCode401_PIS"
        },
        "path": {
            "type": "string"
        },
        "text": {
            "description": "Additional explaining text to the TPP.",
            "type": "string",
            "maxLength": 512
        }
    },
    "required": [
        "category",
        "code"
    ]
}
              
{
    "title": "tppMessage403_PIS",
    "type": "object",
    "properties": {
        "category": {
            "$ref": "#/definitions/tppMessageCategory"
        },
        "code": {
            "$ref": "#/definitions/MessageCode403_PIS"
        },
        "path": {
            "type": "string"
        },
        "text": {
            "description": "Additional explaining text to the TPP.",
            "type": "string",
            "maxLength": 512
        }
    },
    "required": [
        "category",
        "code"
    ]
}
              
{
    "title": "tppMessage404_PIS",
    "type": "object",
    "properties": {
        "category": {
            "$ref": "#/definitions/tppMessageCategory"
        },
        "code": {
            "$ref": "#/definitions/MessageCode404_PIS"
        },
        "path": {
            "type": "string"
        },
        "text": {
            "description": "Additional explaining text to the TPP.",
            "type": "string",
            "maxLength": 512
        }
    },
    "required": [
        "category",
        "code"
    ]
}
              
{
    "title": "tppMessage405_PIS",
    "type": "object",
    "properties": {
        "category": {
            "$ref": "#/definitions/tppMessageCategory"
        },
        "code": {
            "description": "Message codes defined for payment cancelations PIS for HTTP Error code 405 (METHOD NOT ALLOWED).",
            "example": "SERVICE_INVALID",
            "type": "string",
            "default": "SERVICE_INVALID"
        },
        "path": {
            "type": "string"
        },
        "text": {
            "description": "Additional explaining text to the TPP.",
            "type": "string",
            "maxLength": 512
        }
    },
    "required": [
        "category",
        "code"
    ]
}
              
{
    "title": "tppMessage409_PIS",
    "type": "object",
    "properties": {
        "category": {
            "$ref": "#/definitions/tppMessageCategory"
        },
        "code": {
            "description": "Message codes defined for PIS for HTTP Error code 409 (CONFLICT).",
            "example": "STATUS_INVALID",
            "type": "string",
            "default": "STATUS_INVALID"
        },
        "path": {
            "type": "string"
        },
        "text": {
            "description": "Additional explaining text to the TPP.",
            "type": "string",
            "maxLength": 512
        }
    },
    "required": [
        "category",
        "code"
    ]
}

NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 400.

{
    "title": "Error400_NG_PIS",
    "type": "object",
    "properties": {
        "tppMessages": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/tppMessage400_PIS"
            }
        },
        "_links": {
            "$ref": "#/definitions/_linksAll"
        }
    }
}

NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 401.

{
    "title": "Error401_NG_PIS",
    "type": "object",
    "properties": {
        "tppMessages": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/tppMessage401_PIS"
            }
        },
        "_links": {
            "$ref": "#/definitions/_linksAll"
        }
    }
}

NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 403.

{
    "title": "Error403_NG_PIS",
    "type": "object",
    "properties": {
        "tppMessages": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/tppMessage403_PIS"
            }
        },
        "_links": {
            "$ref": "#/definitions/_linksAll"
        }
    }
}

NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 404.

{
    "title": "Error404_NG_PIS",
    "type": "object",
    "properties": {
        "tppMessages": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/tppMessage404_PIS"
            }
        },
        "_links": {
            "$ref": "#/definitions/_linksAll"
        }
    }
}

NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 405.

{
    "title": "Error405_NG_PIS",
    "type": "object",
    "properties": {
        "tppMessages": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/tppMessage405_PIS"
            }
        },
        "_links": {
            "$ref": "#/definitions/_linksAll"
        }
    }
}

NextGenPSD2 specific definition of reporting error information in case of a HTTP error code 409.

{
    "title": "Error409_NG_PIS",
    "type": "object",
    "properties": {
        "tppMessages": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/tppMessage409_PIS"
            }
        },
        "_links": {
            "$ref": "#/definitions/_linksAll"
        }
    }
}

Link to a resource

{
    "type": "object",
    "properties": {
        "href": {
            "$ref": "#/definitions/hrefEntry"
        }
    }
}

Link to a resource

{
    "type": "string",
    "example": "/v1/payments/sepa-credit-transfers/1234-wertiq-983"
}