DP Postman Collection

This Postman collection provides API testing capabilities for Data Providers (DP).

Setup Instructions

1. Download the DP Postman Collection

   • You can download the collection from the Resources section of the documentation.
   • Import the collection into your Postman workspace.

2. Environment Configuration

   • Use the same Postman environment as your DC (Data Consumer) setup. Ensure you have transport certificates configured for mTLS authentication with the PayNet Hub.
   • Verify that in the environment, you have values in place for dc_id, redirectUrl, and signing/encryption keys are pre-configured

3. Initial Context Setup

   • Run the "0 - Set Context" request to initialize DP-specific variables:
     • dp_id - The Data Provider identifier
     • dp_rs - URL to the DP resource server (The default https://httpbin.org/anything simply "plays back" the request for testing purposes)
     • dp_consent_id - Consent ID for the test flow
     • account_id - Account ID for the test flow

What does this collection do ?

What This Collection Is

• A testing and simulation tool that lets you see exactly what requests the PayNet Open Finance Hub will send to your DP endpoints
• A way to validate your DP API implementation by replaying realistic OFP-to-DP calls against your implementation of the DP specification.
• A reference for request/response formats, including signed JWTs (x-signature headers), encrypted payloads (JWE), and consent event bodies
• A companion to the DC (Data Consumer) collection — together they cover both sides of the Open Finance Hub

What This Collection Is Not

• This is not a production client — it uses Postman utilities (e.g. postman-echo.com, httpbin.org) for context setup and playback
• This is not a substitute for the PayNet specification — always refer to the official PayNet Open Finance API specification for authoritative field definitions, error codes, and business rules

Collection Structure

The collection is organized into two main folders that represent the two directions of API calls in the Open Finance Hub:

📁 PayNet → DP

This folder contains requests that simulate the PayNet Open Finance Hub calling your DP endpoints. It covers the following flows:

Data Providers are responsible for implementing the DP APIs. Once your DP endpoints are implemented:

• Configure transport certificates for mutual TLS (mTLS) authentication with the Hub
• Update the dp_rs environment variable to point to your DP resource server
• For each flow folder, run the requests in numbered order (e.g. step 10 signs the request, step 20 sends it to your DP, step 30 decrypts the response)
• Use the default https://httpbin.org/anything as dp_rs first to understand the request shape — httpbin will echo back exactly what was sent, allowing you to inspect headers, query parameters, and body content
• Once familiar with the request format, switch dp_rs to your actual DP resource server and verify your implementation returns the expected responses
• Responses from your DP resource endpoints for account, balances, and transactions must be JWE-encrypted — use the "Decrypt [Utility]" step (step 30) to decrypt and inspect them
• Review the x-signature header on incoming requests. For the purposes of testing, you can use the DC signing and encryption keys that were issued.

📁 DP → PayNet [For Reference Only]

This folder contains reference implementations for DP-to-PayNet Hub API calls, including:

Note: The implementations for these collections are not yet available on the PayNet Sandbox environment. They are provided as guidance and reference for understanding how the APIs should be called.