Notify the payment facilitator about a successful credit

Credit Notification tells the payment facilitator that its acquiring bank has successfully collected money for a merchant. The payment facilitator uses the notification to keep its own record of the successful credit. The receiving institution acknowledges the notification; receiving it does not move money or create another credit to the merchant.

Before you begin

• Implement Secure every request and response.
• Follow How to Encrypt and Decrypt Data for the request envelope and message-opening sequence.
• Follow Format identifiers and date-times.
• Read Understand common payment fields.
• Read Understand code values.
• Support lookup by message ID, instruction ID, end-to-end ID, and clearing-system reference.
• Confirm that the notification reports a completed BOOK credit.

Endpoint and headers

Create an HTTPS POST endpoint and provide its URL to Blinc. For example:

https://sandbox.examplebank.com/blinc/credit-notifications

Every request must contain Content-Type: application/json, Accept: application/json, x-timestamp, and x-signature. Every response, including a business rejection, must contain Content-Type: application/json, x-timestamp, and x-signature. See Secure every request and response for what each header protects and how to validate it. Decrypt before verifying x-signature.

Request business message

{
  "GrpHdr": {
    "MsgId": "00000120260817130000000000000000040",
    "CreDtTm": "2026-08-17T13:00:00.000Z"
  },
  "Ntfctn": {
    "Acct": {
      "Id": {
        "Othr": {
          "Id": "0123456789",
          "SchmeNm": {
            "Cd": "NUBAN"
          }
        }
      },
      "Ccy": "NGN",
      "Nm": "Ada Okafor"
    },
    "Ntry": {
      "Amt": {
        "Amt": 250000,
        "Ccy": "NGN"
      },
      "CdtDbtInd": "CRDT",
      "Sts": "BOOK",
      "BookgDt": {
        "Dt": "2026-08-17T13:00:00.000Z"
      },
      "ValDt": {
        "Dt": "2026-08-17T13:00:00.000Z"
      },
      "NtryDtls": {
        "TxDtls": {
          "Refs": {
            "EndToEndId": "E2E-0000000040",
            "InstrId": "INSTR-0000000040",
            "ClrSysRef": "CLR-0000000040"
          },
          "RltdPties": {
            "Dbtr": {
              "Nm": "Example Store",
              "Id": {
                "Othr": {
                  "Id": "CREDITOR-001",
                  "SchmeNm": {
                    "Cd": "BLINC"
                  }
                }
              }
            },
            "DbtrAcct": {
              "Id": {
                "IBAN": null,
                "Othr": {
                  "Id": "0987654321",
                  "SchmeNm": {
                    "Cd": "NUBAN"
                  }
                }
              }
            }
          },
          "RmtInf": {
            "Ustrd": "Merchant payment credit notification",
            "Strd": {
              "RfrdDocAmt": {
                "DuePyblAmt": {
                  "Amt": 250000,
                  "Ccy": "NGN"
                },
                "AdjstmntAmtAndRsn": {
                  "Amt": {
                    "Amt": 1250,
                    "Ccy": "NGN"
                  },
                  "Rsn": "PAYMENT_FACILITATOR",
                  "AddtlInf": "Payment facilitator share of the transaction fee.",
                  "TttlCharges": { "Amt": 2500, "Ccy": "NGN" }
                },
                "RmtdAmt": {
                  "Amt": 247500,
                  "Ccy": "NGN"
                }
              },
              "RfrdDocInf": {
                "Nb": null
              }
            }
          }
        }
      }
    }
  },
  "SplmtryData": {
    "PlcAndNm": "AdditionalDetails",
    "Envlp": {
      "PaymentMethod": "STATICQR",
      "Merchant": {
        "TerminalId": "TERM-0001",
        "MerchantName": "Example Store",
        "MerchantCategoryCode": "5411",
        "TerminalLocation": null,
        "TerminalReference": null,
        "TerminalTimestamp": null
      }
    }
  }
}

Receive and acknowledge the credit report

1. Decrypt the body, verify the header signature, then validate the timestamp and replay state.
2. Validate the message ID and all transaction references.
3. Confirm the notified account exists, is eligible, and uses the stated currency.
4. Require CdtDbtInd to be CRDT; this operation does not report debits.
5. Confirm that the reported credit has BOOK status.
6. Match amount, currency, booking/value dates, debtor, remittance, payment method, and merchant data with the referenced transaction.
7. Save the acknowledgement with the notification references. If Blinc sends the same notification again, send the same acknowledgement without treating it as a new credit.
8. Sign and encrypt the acknowledgement.

Request field reference

Protected acknowledgement

Return a signed and encrypted acknowledgement whose readable plaintext is:

{
  "GrpHdr": {
    "MsgId": "00000120260816103501000000000000104",
    "CreDtTm": "2026-08-16T10:35:01.000Z",
    "OrgnlMsgId": "12345620260816103500000000000000005",
    "OrgnlMsgNmId": "camt.054.001.11"
  },
  "NtfctnSts": {
    "OrgnlInstrId": "DD-INSTR-0001",
    "OrgnlEndToEndId": "DD-E2E-0001",
    "OrgnlClrSysRef": "DD-CLR-0001",
    "Sts": "ACSC",
    "StsRsnInf": null
  }
}

GrpHdr.MsgId is a new institution-generated response ID. The other header fields identify when the response was created and which notification it answers. NtfctnSts groups the acknowledgement result; its three Orgnl... fields copy the request references. Sts is ACSC when recorded or RJCT when rejected. For RJCT, populate StsRsnInf.Orgtr.Nm, StsRsnInf.Rsn.Cd, and StsRsnInf.AddtlInf with the decision owner, stable reason, and corrective action.

Fee and settlement

DuePyblAmt is the gross amount. TttlCharges is the total fee paid by the merchant, while the payment-facilitator amount in AdjstmntAmtAndRsn.Amt identifies the payment facilitator's share of that fee. RmtdAmt is the amount settled to the beneficiary after the total fee is deducted: DuePyblAmt - TttlCharges. In this example, NGN 250,000 - NGN 2,500 = NGN 247,500.

Common mistakes

Test before certification

• A BOOK notification is acknowledged as a successful credit report.
• The same notification delivered again receives the same acknowledgement.
• Reused IDs with changed amount, account, state, or references reject.
• DBIT, unsupported status, zero amount, currency mismatch, and unknown account reject.
• Invalid encryption, signature, timestamp, or replay state fails before recording the notification.

Next

Learn how to return clear errors and handle repeated deliveries in Return clear errors and handle repeated deliveries.