PaymentRequestResource
ISO20022: The PaymentRequestResource message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used by a Creditor to request movement of funds from the debtor account to a creditor. API: Information about the creditor (Id, account and agent) must be placed at instruction level. Thus multi-beneficiary payments can be handled. The requested execution date must be placed at payment level even when all instructions are requested to be executed at the same date. The latest case includes:
- multiple instructions having different requested execution dates
- standing orders settings
Fields (20)
- resourceIdResourceId
Schema: ResourceId
- paymentInformationIdPaymentInformationIdrequired
Schema: PaymentInformationId
- batchBookingBatchBookingIndicator
Schema: BatchBookingIndicator
- creationDateTimeCreationDateTimerequired
Schema: CreationDateTime
- numberOfTransactionsintegerrequired
ISO20022: Number of individual transactions contained in the message.
ISO20022: Number of individual transactions contained in the message. API: Each ASPSP will specify a maximum value for this field taking into accounts its specificities about payment request handling
- initiatingPartyPartyIdentificationrequired
Schema: PartyIdentification
- acceptDebtorAccountChangeboolean
indicator that the debtor account can be changed in the payment request by the ASPSP if needed
indicator that the debtor account can be changed in the payment request by the ASPSP if needed
- true: debtor account can be changed (default value)
- false: debtor account cannot be changed
- acceptChargeHandlingChangeboolean
indicator that the charge handling can be changed in the payment request by the ASPSP if needed
indicator that the charge handling can be changed in the payment request by the ASPSP if needed
- true: charge handling can be changed (default value)
- false: charge handling cannot be changed
- acceptInstantPaymentDowngradeboolean
Indicator that the requested instant SEPA Credit Transfer method can be downgraded by the ASPSP into a plain-vanilla SEPA Credit Transfer, when Instant SCT cannot apply or is refused by the PSU.
Indicator that the requested instant SEPA Credit Transfer method can be downgraded by the ASPSP into a plain-vanilla SEPA Credit Transfer, when Instant SCT cannot apply or is refused by the PSU. Eventually, it is up to the ASPSP to downgrade or reject the payment. In case of a downgrade, the ASPSP will have to update de relevant field [LocalInstrument] and remove the "INST" value in order to keep the PISP informed.
- true: payment method can be downgraded
- false: payment method cannot be downgraded (default value)
- paymentTypeInformationPaymentTypeInformationrequired
Schema: PaymentTypeInformation
- debtorPartyIdentification
Schema: PartyIdentification
- debtorAccountAccountIdentification
Schema: AccountIdentification
- debtorAgentFinancialInstitutionIdentification
- chargeBearerChargeBearerCode
Schema: ChargeBearerCode
- paymentInformationStatusPaymentInformationStatusCode
Schema: PaymentInformationStatusCode
- statusReasonInformationStatusReasonInformation
Schema: StatusReasonInformation
- fundsAvailabilityFundsAvailabilityInformation
Schema: FundsAvailabilityInformation
- bookingBookingInformation
Schema: BookingInformation
- creditTransferTransactionarray<CreditTransferTransactionResource>required
ISO20022: Payment processes required to transfer cash from the debtor to the creditor.
ISO20022: Payment processes required to transfer cash from the debtor to the creditor. API: Each ASPSP will specify a maxItems value for this field taking into accounts its specificities about payment request handling
Item schema: CreditTransferTransactionResource
- supplementaryDataSupplementaryDatarequired
Schema: SupplementaryData