1. Background

Requests are inquiries made by clients to the Pingwire system, primarily sent through the API, but can also be initiated manually via the Pingwire interface. These requests serve various purposes, such as conducting investigations on entities and verifying KYC forms, among others.

2. Key Elements of a Request Body:

1. customId: An internal identifier used within the Client's system to reference the request.

2. process: Specifies the set of rules to be applied during request processing.

3. requestType: Defines the type of request, such as "transaction", "individualKyc", or "businessKyc", which indicates the purpose of the request.

4. extraInformation: Contains the core details for the request. The structure of this field varies depending on the request type but generally includes:

   • Transaction Requests:
     • amount: The transaction amount.
     • currency: The currency for the transaction.
     • transactionTypes: A list of transaction types relevant to the request.
     • transactionChannel: The channel through which the transaction was initiated (e.g., "bank-giro").
     • initiator: Details about the entity initiating the transaction, such as account ID, IBAN, and bank account status.
     • recipient: Details about the entity receiving the transaction.
   • KYC Requests (Individual/Business):
     • entity: Information about the individual or business, including identifiers like Swedish Social Security Number (SSN) or Organization Number.
     • ownedAccounts: A list of accounts owned by the entity, with account details like IBAN, account status, and account type.
     • email: Contact email for the entity.
     • phoneNumber: Contact phone number for the entity.

5. groups: A list of groups to categorize or organize the request, replacing the deprecated "segment" field.

3. Different Types of Requests:

The Pingwire system accommodates various types of requests, each designed for specific actions, such as investigations, KYC form verification, etc. These types ensure that the system can respond appropriately to the diverse needs of clients.

For comprehensive details on request content, types and flow, we refer to Pingwire Documentation.

3.1 Recommendations Assigned to Requests:

1. Block: Instructs to halt the process and block the entity.
2. Review: Advises reviewing the request within the Pingwire interface before proceeding.
3. Proceed: Suggests continuing with the process as planned.

3.2 Action by User:

Upon receiving a Review recommendation, the user should decide whether to block or proceed with the request. The client system can then retrieve the updated recommendation.

3.3 Reprocessing a request

Reprocessing a request means running it again through the platform’s current rule framework so it is evaluated with the latest rule configuration. This is useful if a rule has been created or adjusted after the request was first made and you want the request evaluated retroactively against the new conditions.