Open Master Beneficiary Registry workspace ↗Skip to main content
NSIPA — National Social Investment Programmes AgencyNSIPA
Registration & enrollment
SYNTHETIC SANDBOX • Use fictional people and households. This service does not verify NIN or issue real payments.

Ask the local knowledge assistant

NSIPA knowledge library

Task guidance for each service and workflow stage. Local guides describe NSIPA; upstream references may describe other releases. Your account determines available actions.

531 published entries across 18 services · 64 source-linked guides

Persona workspace

4 matching entries · Page 1 of 1

Registry integration configuration · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Inspect incoming or outgoing data mappings.

What to do

  1. Open the intended key path, subscription, semantic pattern, template or topic.
  2. Check the source and destination against the approved integration contract.
  3. Verify the change using a synthetic message.

What you need

Use the scope and environment shown in the configuration.

Next step

Trace the message through Incoming messages or Outgoing messages.

Published version 1 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Outgoing integration configuration · Master Beneficiary Registry · all

NSIPA local workflow

Provisional guidance

Maintain the configured topics and templates for outgoing registry integration.

What to do

  1. Select the intended topic or template.
  2. Check its field mappings, destination and expected record type.
  3. Save authorised changes and verify an approved test message before relying on the integration.

What you need

Integration configuration permission and the approved destination schema.

Next step

Inspect outgoing message status for the configured integration.

Common issues

A template change can affect future messages. Confirm dependencies and avoid using live personal data in troubleshooting examples.

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Understand importing a registry data source into PBMS · Beneficiary programme administration · all

Upstream reference — confirm feature availability

Provisional guidance

Legacy PBMS can use configured data sources to retrieve social registry records.

What to do

  1. Check the source service and the target individual or group register.
  2. Have the authorised administrator confirm endpoint and authentication configuration.
  3. Test a small fictional dataset and check field mapping.

What you need

Approved integration access and a configured data source.

Next step

Verify imported records before programme processing.

Common issues

Do not place passwords or tokens in knowledge content. Source and target identifiers must remain consistent.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?

Monitor imported registry submissions · Master Beneficiary Registry · all

Upstream reference — confirm feature availability

Provisional guidance

Partner and staff ingestion can create intake submissions or proposed updates.

What to do

  1. Identify the source, target register and intake form.
  2. Retain the returned correlation reference.
  3. Check classification, transformation and processing status where available.
  4. Investigate failed items before resubmitting.

What you need

An authorised integration and supported ingestion configuration.

Next step

Verify the resulting submission or change request.

Common issues

Acceptance by an API is not proof of successful registry processing; do not repeatedly send the same payload.

References

Sources checked: 2026-10-05

Published version 2 · public guidance

Open this guide · Download plain text

Was this guide helpful?