pain.014 — Creditor Payment Activation Request Status Report

Returns to the creditor (originator of a pain.013 Request-to-Pay) the activation status after the creditor PSP's check and the debtor's decision. Key element of the European Request-to-Pay (R2P) workflow under EPC's SEPA Request-to-Pay scheme (SRTP), typically paired with SCT Inst for instant execution.

Purpose: R2P activation status

The R2P workflow happens in 4 messages: (1) pain.013 — creditor sends a Request-to-Pay to debtor via their PSP; (2) debtor PSP forwards to debtor app (mobile banking); (3) debtor accepts/refuses; (4) pain.014 — creditor PSP relays the status to the creditor. If accepted, payment is then executed via pain.001/SCT Inst.

XML structure

Wrapped in <CdtrPmtActvtnReqStsRpt>. Components: GrpHdr (header), OrgnlGrpInfAndSts (group status), OrgnlPmtInfAndSts (per-payment status), TxInfAndSts (per-transaction status).

Example: activation status

BNP Paribas R2P Gateway notifies ACME Export that the EUR 1,250 R2P was accepted by debtor — SCT Inst scheduled for 18:00:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.014.001.10">
  <CdtrPmtActvtnReqStsRpt>
    <GrpHdr>
      <MsgId>R2P-STAT-20260519-001</MsgId>
      <CreDtTm>2026-05-19T14:00:00+02:00</CreDtTm>
      <InitgPty>
        <Nm>ACME EXPORT SARL</Nm>
        <Id>
          <OrgId><LEI>969500ABCDEFGHIJKL12</LEI></OrgId>
        </Id>
      </InitgPty>
    </GrpHdr>
    <OrgnlGrpInfAndSts>
      <OrgnlMsgId>R2P-INIT-20260518-001</OrgnlMsgId>
      <OrgnlMsgNmId>pain.013.001.10</OrgnlMsgNmId>
      <OrgnlCreDtTm>2026-05-18T10:00:00+02:00</OrgnlCreDtTm>
      <OrgnlNbOfTxs>1</OrgnlNbOfTxs>
      <OrgnlCtrlSum>1250.00</OrgnlCtrlSum>
      <GrpSts>ACCP</GrpSts>
    </OrgnlGrpInfAndSts>
    <OrgnlPmtInfAndSts>
      <OrgnlPmtInfId>PMT-INFO-001</OrgnlPmtInfId>
      <PmtInfSts>ACCP</PmtInfSts>
      <TxInfAndSts>
        <OrgnlEndToEndId>INV-2026-887</OrgnlEndToEndId>
        <TxSts>ACTC</TxSts>
        <StsRsnInf>
          <Orgtr><Nm>BNP PARIBAS R2P GATEWAY</Nm></Orgtr>
          <Rsn><Cd>G002</Cd></Rsn>
          <AddtlInf>DEBTOR APPROVED REQUEST-TO-PAY ON 20260519 13:45 - INSTANT PAYMENT SCHEDULED FOR 20260519 18:00</AddtlInf>
        </StsRsnInf>
        <OrgnlTxRef>
          <Amt><InstdAmt Ccy="EUR">1250.00</InstdAmt></Amt>
          <ReqdExctnDt>
            <Dt>2026-05-19</Dt>
          </ReqdExctnDt>
        </OrgnlTxRef>
      </TxInfAndSts>
    </OrgnlPmtInfAndSts>
  </CdtrPmtActvtnReqStsRpt>
</Document>

Common pitfalls

• OrgnlMsgId wrong: must exactly echo the MsgId of pain.013 — otherwise creditor doesn't know which R2P the status applies to.
• RJCT status without EPC Rsn/Cd: EPC SRTP codes (G001 to G099) are mandatory. Custom code = R2P gateway rejection.
• No pain.014 within SRTP SLA (15 min): creditor escalates automatically and may consider the R2P refused.
• Confusion pain.014 vs pain.002: pain.002 is the status of a pain.001 (Customer Credit Transfer Initiation); pain.014 is the status of a pain.013 (Request-to-Pay).

Related messages (Request-to-Pay workflow)

• pain.013 — Creditor Payment Activation Request (initial R2P).
• pain.001 — Customer Credit Transfer Initiation (SCT Inst execution following pain.014 ACCP).
• pain.002 — Customer Payment Status Report.
• pacs.008 — FI to FI Customer Credit Transfer (interbank SCT Inst).