# Roles and responsibilities

What the Payment Network, the client, and Axiym each do.

Product: PNSL API
Guides follow API reference 2.0.0 and event reference 1.0.0.
Canonical page: https://docs.axiym.io/pnsl-api/concepts/roles-and-responsibilities

Every PNSL transaction involves three parties.

## Payment Network

The institution that integrates with the PNSL API and operates the payment
system in which its clients originate payments. It is the only party that
calls the API.

The Payment Network:

* onboards clients with Axiym;
* decides which client payments to fund and requests the funding;
* executes the client payment in its own system once the funds arrive;
* routes client funds to Axiym and applies unallocated funds to clients;
* receives webhook events and reconciles Axiym's records with its own.

## Client

The business whose payments are funded, such as a Money Service Business or a
Payment Service Provider. It originates payments through the Payment Network
and owes each receivable created for it.

The client:

* provides the information needed for onboarding and underwriting;
* is addressed in the API by its `clientId`; its client `code` (for example
  `AXI000221`) is used only in payment memos;
* has a credit account per currency and payment rail;
* repays its receivables, usually by sending funds to Axiym with its client
  `code` or settlement reference in the memo.

The client has no API credentials of its own. The Payment Network acts for it
through the `/clients/{clientId}/...` endpoints.

## Axiym

Axiym operates PNSL and provides the funding.

Axiym:

* reviews clients (compliance and underwriting) and sets their credit limits;
* creates receivables and disburses funds to the Payment Network's bank
  account;
* tracks outstanding principal, interest, and fees;
* attributes incoming funds to clients and applies them to receivables;
* sends signed webhook events when a client, credit account, or receivable
  changes.

## How the roles interact



```mermaid
sequenceDiagram
    participant C as Client
    participant PN as Payment Network
    participant A as Axiym

    C->>PN: Originates a payment
    PN->>A: Checks the client's availableBalance
    PN->>A: Requests funding for the payment
    A-->>PN: Creates the receivable and disburses the funds
    PN->>PN: Executes the client payment
    C->>A: Sends funds with its code or settlement reference in the memo
    A-->>PN: Applies the funds to receivables and sends events
```



## Onboarding

A client must be onboarded and `ACTIVE` before it can be funded. Submit the
client with
[`POST /onboardings`](/pnsl-api/api-reference/2.0.0/onboarding/startOnboarding)
and track the review with
[`GET /onboardings/{clientId}`](/pnsl-api/api-reference/2.0.0/onboarding/getOnboardingStatus).
The response gives you the `clientId` used in every client endpoint. See
[Client onboarding](/pnsl-api/integration-guide/implementation-guides/client-onboarding)
for the steps.