NPP RTN User Acceptance Testing Scenarios


Question

What UAT scenarios does ANZ recommend a customer complete prior to activating the NPP Real Time Notification service?

Answer

Using the Fileactive Self Service Testing API it is recommended a customer complete the following testing scenarios.

# Scenario Description RTN Self-Service Request NPP Payment Notification Response Snipet
1 ARM customer receipt The Corporate Customer is configured with an ARM account and receives a payment to their virtual account
  {
    "account_identification": "014814800000010",
    "entry_reference": "Trading transfer",
    "amount": "100.50",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "arm_creditor_account_identification": "063678965323010",
    "remittance_information": {
      "unstructured": [
        "Testing ARM Customer"
      ]
    }
  }
    
  {
    "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
    "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
    "account_identification": "014814800000010",
    "account_issuer": "014814",
    "entry": [
      {
        "related_parties": {
          "creditor_account_identification": "965323010",
          "creditor_account_issuer": "063678"
        }
      }
    ]
  }
    
2 Non-ARM customer receipt The Corporate Customer receives a payment to their settlement account.
  {
    "account_identification": "014814800000010",
    "entry_reference": "Bill payment",
    "amount": "200.25",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "remittance_information": {
      "unstructured": [
        "Testing Non-ARM Customer"
      ]
    }
  }
    
  {
    "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
    "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
    "account_identification": "014814800000010",
    "account_issuer": "014814",
    "entry": [
      {
        "related_parties": {
          "creditor_account_identification": "800000010",
          "creditor_account_issuer": "014814"
        }
      }
    ]
  }
    
3 Remittance information with emojis - binary Include any emoji in the remittance information
  {
    "account_identification": "014814800000010",
    "entry_reference": "Bill payment",
    "amount": "10.50",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "remittance_information": {
      "unstructured": [
        " 😀🚀 Testing with emojis"
      ]
    }
  }
    
  {
    "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
    "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
    "account_identification": "014814800000010",
    "account_issuer": "014814",
    "entry": [
      {
        "remittance_information": {
          "unstructured": [
            "😀🚀 Testing with emojis"
          ]
        }
      }
    ]
  }
    
4 Remittance information with emojis - NCR HEX code points Include any emoji in the remittance information
  {
    "account_identification": "014814800000010",
    "entry_reference": "Bill payment",
    "amount": "10.50",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "remittance_information": {
      "unstructured": [
        "🛸 TC-04 testing emoji"
      ]
    }
  }
    
  {
    "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
    "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
    "account_identification": "014814800000010",
    "account_issuer": "014814",
    "entry": [
      {
        "remittance_information": {
          "unstructured": [
            "🛸 TC-04 testing emoji"
          ]
        }
      }
    ]
  }
    
5 Pay ID - Mobile The payer/debtor has used a Pay ID when making the payment to the Corporate Customer's account.
  {
    "account_identification": "014814800000010",
    "entry_reference": "Bill payment",
    "amount": "150.00",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "creditor_alias": {
      "type": "TELI",
      "identification": "+61403736550"
    },
    "remittance_information": {
      "unstructured": [
        "Testing with PayId"
      ]
    }
  }
    
  {
    "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
    "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
    "account_identification": "014814800000010",
    "account_issuer": "014814",
    "entry": [
      {
        "related_parties": {
          "creditor_account_proxy": {
            "proxy_type": "TELI",
            "proxy_identification": "+61403736550"
          }
        }
      }
    ]
  }
    
6 Pay ID - eMail The payer/debtor has used a Pay ID when making the payment to the Corporate Customer's account.
  {
    "account_identification": "014814800000010",
    "entry_reference": "Bill payment",
    "amount": "150.00",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "creditor_alias": {
      "type": "EMAL",
      "identification": "npp@mail.com"
    },
    "remittance_information": {
      "unstructured": [
        "Testing with PayId"
      ]
    }
  }
    
  {
    "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
    "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
    "account_identification": "014814800000010",
    "account_issuer": "014814",
    "entry": [
      {
        "related_parties": {
          "creditor_account_proxy": {
            "proxy_type": "EMAL",
            "proxy_identification": "npp@mail.com"
          }
        }
      }
    ]
  }
    
7 Return of Funds (PACS.004) The Corporate Customer is receiving a credit to their settlement account.
  {
    "account_identification": "014814800000010",
    "entry_reference": "Bill payment",
    "amount": "500.00",
    "debtor_name": "Andras Arato",
    "creditor_name": "Holden Holdings",
    "remittance_information": {
      "unstructured": [
        "Testing Return of Funds"
      ]
    },
    "return_information": {
      "reason_code": "NARR",
      "additional_information": [
        "Beneficiary is",
        "unknown"
      ]
    }
  }
    
  {
      "identification": "D942DD0B23674C3FBDC2702ECB0C837F",
      "creation_date_time": "2022-07-27T23:44:01.9842888+00:00",
      "account_identification": "014814800000010",
      "account_issuer": "014814",
      "entry": [
        {
          "return_information": {
              "reason": {
                "code": "NARR"
              },
              "additional_information": [
                "Beneficiary is",
                "unknown"
              ]
            }
          }
        }
      ]
    }
    
8 Duplicate Check ANZ to reposcess a previously sent Notification which the customer should not process. n/a ANZ will send a previously sent Notification which has the same account_servicer_reference.
9 Invalid API Key ANZ to update customer Notificaiton profile with incorrect API Key. Customer to reject Notifications with invalid API key. Send a valid RTN request ANZ will send a well formed Notification which customer should reject with HTTP 401