P2p commission

[!info] Overview The P2P Commission REST API manages commission rules for peer-to-peer payment transactions in the pkbillms billing system. P2P commissions define fee structures, transaction amount ranges, and percentage-based charges that are applied to P2P transfers.

📋 Table of Contents

• Quick Reference

• Data Models

• API Endpoints

  • Create P2P Commission

  • Update P2P Commission

  • Partial Update

  • Get All P2P Commissions

  • Get Single P2P Commission

  • Count P2P Commissions

  • Delete P2P Commission

• Request & Response Examples

• Error Handling

• Validation Rules

• Business Logic

---

Quick Reference

[!abstract] API Configuration

• Base URL: /api

• Entity Name: pkbillmsP2PCommission

• Controller: P2pCommissionResource

• Framework: Spring Boot + JHipster

• Auth: Required (Spring Security)

• Content-Type: application/json

Endpoints Summary

Method	Endpoint	Description	Status
POST	/api/p-2-p-commissions	Create new commission	201
POST	/api/p-2-p-commissions/v1	Create (versioned)	201
PUT	/api/p-2-p-commissions/{id}	Full update	200
PUT	/api/p-2-p-commissions/v1/{id}	Full update (versioned)	200
PATCH	/api/p-2-p-commissions/{id}	Partial update	200
GET	/api/p-2-p-commissions	Get all with criteria	200
GET	/api/p-2-p-commissions/{id}	Get by ID	200
GET	/api/p-2-p-commissions/count	Count by criteria	200
DELETE	/api/p-2-p-commissions/{id}	Delete commission	204

---

Data Models

Field Specifications

Field	Type	Required	Max/Range	Description
id	Long	❌ Auto	-	Primary key
name	String	✅	-	Unique commission name
commissionDetails	String	❌	-	JSON string for detailed commission
fromAmount	Long	❌	-	Minimum transaction amount
toAmount	Long	❌	-	Maximum transaction amount
up	Double	❌	0-100	Commission added on top (percentage)
down	Double	❌	0-100	Commission deducted from amount (%)
fee	Double	❌	0-100	Service fee (percentage)
description	String	❌	-	Commission description
commissionPartGroup	Object	❌	-	Associated commission part group

P2pCommissionDTO

[!note] Data Transfer Object Used for API responses and data exchange.

public class P2pCommissionDTO {
    private Long id;
    private String name;
    private String commissionDetails;
    private Long fromAmount;
    private Long toAmount;
    private Double up;
    private Double down;
    private Double fee;
    private String description;
    private P2pCommPartGroupInfoDTO commissionPartGroup;
}

P2pCommissionCriteria

[!note] Query Criteria Used for filtering and searching P2P commissions.

public class P2pCommissionCriteria {
    private LongFilter id;
    private StringFilter name;
    private StringFilter commissionDetails;
    private LongFilter fromAmount;
    private LongFilter toAmount;
    private DoubleFilter up;
    private DoubleFilter down;
    private DoubleFilter fee;
    private StringFilter description;
}

Available Filters:

• id.equals, id.in, id.greaterThan, id.lessThan

• name.equals, name.contains, name.specified

• fromAmount.equals, fromAmount.greaterThan, fromAmount.lessThan

• toAmount.equals, toAmount.greaterThan, toAmount.lessThan

• up.equals, up.greaterThan, up.lessThan

• down.equals, down.greaterThan, down.lessThan

• fee.equals, fee.greaterThan, fee.lessThan

Audit Fields (Inherited)

[!success] Auto-managed These fields are automatically populated by the system.

Field	Type	Description
createdBy	String	Creator username
createdDate	Instant	Creation timestamp
lastModifiedBy	String	Last modifier
lastModifiedDate	Instant	Last modification

---

API Endpoints

Create P2P Commission

POST /api/p-2-p-commissions or /api/p-2-p-commissions/v1

Creates a new P2P commission rule.

Request

Headers:

Content-Type: application/json
Authorization: Bearer {token}

Body:

{
  "name": "Standard Transfer Fee",
  "commissionDetails": "{\"type\":\"standard\",\"category\":\"p2p\"}",
  "fromAmount": 10000,
  "toAmount": 1000000,
  "up": 2.5,
  "down": 0.0,
  "fee": 1.0,
  "description": "Standard commission for transfers between 10K and 1M",
  "commissionPartGroup": {
    "id": 1
  }
}

[!warning] Validation Rules

• id must be null (auto-generated)

• name must be unique

• name is required

• up, down, fee must be between 0 and 100

Response

✅ Success (201 Created):

HTTP/1.1 201 Created
Location: /api/p-2-p-commissions/1

{
  "id": 1,
  "name": "Standard Transfer Fee",
  "commissionDetails": "{\"type\":\"standard\",\"category\":\"p2p\"}",
  "fromAmount": 10000,
  "toAmount": 1000000,
  "up": 2.5,
  "down": 0.0,
  "fee": 1.0,
  "description": "Standard commission for transfers between 10K and 1M",
  "commissionPartGroup": {
    "id": 1
  },
  "createdBy": "admin",
  "createdDate": "2026-01-29T10:30:00Z",
  "lastModifiedBy": "admin",
  "lastModifiedDate": "2026-01-29T10:30:00Z"
}

❌ Error (400 - Has ID):

{
  "status": 400,
  "detail": "A new p2pCommission cannot already have an ID",
  "message": "error.cannot.have.id",
  "entityName": "pkbillmsP2PCommission",
  "errorKey": "id"
}

❌ Error (400 - Duplicate Name):

{
  "status": 400,
  "detail": "Commission name already exists",
  "message": "error.existed.name",
  "entityName": "pkbillmsP2PCommission",
  "errorKey": "name"
}

---

Update P2P Commission

PUT /api/p-2-p-commissions/{id} or /api/p-2-p-commissions/v1/{id}

Completely updates an existing P2P commission.

Path Parameters

• id (Long) - P2P commission identifier

Request

Headers:

Content-Type: application/json
Authorization: Bearer {token}

Body:

{
  "id": 1,
  "name": "Updated Standard Fee",
  "commissionDetails": "{\"type\":\"updated\",\"category\":\"p2p\"}",
  "fromAmount": 20000,
  "toAmount": 2000000,
  "up": 3.0,
  "down": 0.5,
  "fee": 1.5,
  "description": "Updated commission for standard transfers",
  "commissionPartGroup": {
    "id": 1
  }
}

[!warning] Validation

• Body id must not be null

• Path id must match body id

• P2P commission must exist in database

• name must remain unique (excluding current record)

• up, down, fee must be between 0 and 100

Response

✅ Success (200 OK):

{
  "id": 1,
  "name": "Updated Standard Fee",
  "commissionDetails": "{\"type\":\"updated\",\"category\":\"p2p\"}",
  "fromAmount": 20000,
  "toAmount": 2000000,
  "up": 3.0,
  "down": 0.5,
  "fee": 1.5,
  "description": "Updated commission for standard transfers",
  "commissionPartGroup": {
    "id": 1
  },
  "lastModifiedBy": "admin",
  "lastModifiedDate": "2026-01-29T14:20:00Z"
}

❌ Errors:

Status	Detail	Message
400	Invalid id	error.not.null
400	ID mismatch	error.not.equal.id
400	Entity not found	error.entity.not.found
400	Duplicate name	error.existed.name

---

Partial Update

PATCH /api/p-2-p-commissions/{id}

Updates only specified fields. Null fields are ignored.

Path Parameters

• id (Long) - P2P commission identifier

Request

Headers:

Content-Type: application/merge-patch+json
Authorization: Bearer {token}

Body (Example - update fee only):

{
  "id": 1,
  "fee": 2.0
}

Body (Example - update description and up):

{
  "id": 1,
  "up": 3.5,
  "description": "New description with higher commission rate"
}

[!tip] Partial Update Behavior

• Only non-null fields are updated

• Other fields remain unchanged

• Perfect for single field updates

• Name uniqueness is still enforced

• Percentage validations still apply (0-100)

Response

✅ Success (200 OK):

{
  "id": 1,
  "name": "Standard Transfer Fee",
  "commissionDetails": "{\"type\":\"standard\",\"category\":\"p2p\"}",
  "fromAmount": 10000,
  "toAmount": 1000000,
  "up": 3.5,
  "down": 0.0,
  "fee": 2.0,
  "description": "New description with higher commission rate",
  "lastModifiedDate": "2026-01-29T15:45:00Z"
}

---

Get All P2P Commissions

GET /api/p-2-p-commissions

Retrieves paginated list with filtering criteria.

Query Parameters

Pagination:

• page - Page number (0-indexed, default: 0)

• size - Items per page (default: 20)

• sort - Sort criteria (e.g., name,asc)

• unPaged - Boolean for unpaged results

Filters (P2pCommissionCriteria):

• id.equals, id.in, id.greaterThan, id.lessThan

• name.equals, name.contains, name.specified

• fromAmount.equals, fromAmount.greaterThan, fromAmount.lessThan

• toAmount.equals, toAmount.greaterThan, toAmount.lessThan

• up.equals, up.greaterThan, up.lessThan

• down.equals, down.greaterThan, down.lessThan

• fee.equals, fee.greaterThan, fee.lessThan

Example Requests

GET /api/p-2-p-commissions?page=0&size=10&sort=name,asc
GET /api/p-2-p-commissions?name.contains=Standard
GET /api/p-2-p-commissions?fromAmount.greaterThan=50000
GET /api/p-2-p-commissions?up.greaterThan=2.0&up.lessThan=5.0
GET /api/p-2-p-commissions?fee.specified=true
GET /api/p-2-p-commissions?unPaged=true

Response

✅ Success (200 OK):

HTTP/1.1 200 OK
X-Total-Count: 15
Link: </api/p-2-p-commissions?page=0&size=20>; rel="first",
      </api/p-2-p-commissions?page=1&size=20>; rel="next"

[
  {
    "id": 1,
    "name": "Standard Transfer Fee",
    "fromAmount": 10000,
    "toAmount": 1000000,
    "up": 2.5,
    "down": 0.0,
    "fee": 1.0,
    "description": "Standard commission for transfers",
    "createdBy": "admin",
    "createdDate": "2026-01-29T10:30:00Z"
  },
  {
    "id": 2,
    "name": "Premium Transfer Fee",
    "fromAmount": 1000000,
    "toAmount": 10000000,
    "up": 1.5,
    "down": 0.0,
    "fee": 0.5,
    "description": "Lower commission for large transfers",
    "createdBy": "admin",
    "createdDate": "2026-01-29T11:00:00Z"
  },
  {
    "id": 3,
    "name": "Micro Transaction Fee",
    "fromAmount": 1000,
    "toAmount": 10000,
    "up": 0.0,
    "down": 5.0,
    "fee": 2.0,
    "description": "Higher fee for small transactions",
    "createdBy": "admin",
    "createdDate": "2026-01-29T12:00:00Z"
  }
]

---

Get Single P2P Commission

GET /api/p-2-p-commissions/{id}

Retrieves a single P2P commission by ID.

Path Parameters

• id (Long) - P2P commission identifier

Request

GET /api/p-2-p-commissions/1
Authorization: Bearer {token}

Response

✅ Success (200 OK):

{
  "id": 1,
  "name": "Standard Transfer Fee",
  "commissionDetails": "{\"type\":\"standard\",\"category\":\"p2p\"}",
  "fromAmount": 10000,
  "toAmount": 1000000,
  "up": 2.5,
  "down": 0.0,
  "fee": 1.0,
  "description": "Standard commission for transfers between 10K and 1M",
  "commissionPartGroup": {
    "id": 1,
    "name": "Standard Group"
  },
  "createdBy": "admin",
  "createdDate": "2026-01-29T10:30:00Z",
  "lastModifiedBy": "admin",
  "lastModifiedDate": "2026-01-29T14:20:00Z"
}

❌ Error (404 Not Found):

{
  "status": 404,
  "detail": "P2P commission not found with id: 999",
  "title": "Not Found",
  "path": "/api/p-2-p-commissions/999"
}

---

Count P2P Commissions

GET /api/p-2-p-commissions/count

Returns the count of P2P commissions matching criteria.

Query Parameters

• Same filters as "Get All P2P Commissions"

Example Requests

GET /api/p-2-p-commissions/count
GET /api/p-2-p-commissions/count?name.contains=Standard
GET /api/p-2-p-commissions/count?up.greaterThan=2.0
GET /api/p-2-p-commissions/count?fromAmount.greaterThan=50000

Response

✅ Success (200 OK):

15

---

Delete P2P Commission

DELETE /api/p-2-p-commissions/{id}

Deletes a P2P commission if not related to any commission part group.

Path Parameters

• id (Long) - P2P commission identifier

Request

DELETE /api/p-2-p-commissions/1
Authorization: Bearer {token}

Response

✅ Success (204 No Content):

HTTP/1.1 204 No Content

❌ Error (400 - Related to Group):

{
  "status": 400,
  "detail": "Cannot delete commission - it is related to a commission part group",
  "message": "error.related.to.group",
  "entityName": "pkbillmsP2PCommission",
  "errorKey": "id",
  "params": "P2pCommission"
}

[!danger] Delete Warning Permanently deletes:

• P2P commission entity

• Cannot delete if commission is associated with a commission part group

• Check group relationships before deletion

Use with caution! This cannot be undone.

---

Examples

Example 1: Create Tiered Commission Structure

• Setup Commission Tiers Request - Small Transactions:

curl -X POST http://localhost:8080/api/p-2-p-commissions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer TOKEN" \
  -d '{
    "name": "Small Transfer Commission",
    "fromAmount": 1000,
    "toAmount": 50000,
    "up": 3.0,
    "down": 0.0,
    "fee": 1.5,
    "description": "Higher percentage for small transactions"
  }'

Request - Medium Transactions:

curl -X POST http://localhost:8080/api/p-2-p-commissions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer TOKEN" \
  -d '{
    "name": "Medium Transfer Commission",
    "fromAmount": 50000,
    "toAmount": 500000,
    "up": 2.0,
    "down": 0.0,
    "fee": 1.0,
    "description": "Standard commission for medium transactions"
  }'

Request - Large Transactions:

curl -X POST http://localhost:8080/api/p-2-p-commissions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer TOKEN" \
  -d '{
    "name": "Large Transfer Commission",
    "fromAmount": 500000,
    "toAmount": 10000000,
    "up": 1.0,
    "down": 0.0,
    "fee": 0.5,
    "description": "Lower commission for large transactions"
  }'

Example 2: Create Commission with Deduction

• Commission Deducted from Amount Request:

curl -X POST http://localhost:8080/api/p-2-p-commissions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer TOKEN" \
  -d '{
    "name": "Deduction Commission",
    "fromAmount": 10000,
    "toAmount": 100000,
    "up": 0.0,
    "down": 2.5,
    "fee": 0.0,
    "description": "Commission deducted from transfer amount"
  }'

Example 3: Update Commission Rates

• Adjust Commission Percentages Request:

curl -X PATCH http://localhost:8080/api/p-2-p-commissions/1 \
  -H "Content-Type: application/merge-patch+json" \
  -H "Authorization: Bearer TOKEN" \
  -d '{
    "id": 1,
    "up": 2.8,
    "fee": 1.2,
    "description": "Updated rates for Q1 2026"
  }'

Response:

{
  "id": 1,
  "name": "Standard Transfer Fee",
  "fromAmount": 10000,
  "toAmount": 1000000,
  "up": 2.8,
  "down": 0.0,
  "fee": 1.2,
  "description": "Updated rates for Q1 2026",
  "lastModifiedDate": "2026-01-29T17:30:12.456Z"
}

Example 4: Search by Amount Range

• Find Commissions for Amount Range Request:

curl -X GET "http://localhost:8080/api/p-2-p-commissions?fromAmount.lessThan=100000&toAmount.greaterThan=50000&sort=up,desc" \
  -H "Authorization: Bearer TOKEN"

Response:

[
  {
    "id": 2,
    "name": "Medium Transfer Commission",
    "fromAmount": 50000,
    "toAmount": 500000,
    "up": 2.5,
    "fee": 1.0,
    "description": "Standard commission"
  },
  {
    "id": 5,
    "name": "Special Promotion",
    "fromAmount": 30000,
    "toAmount": 200000,
    "up": 1.5,
    "fee": 0.5,
    "description": "Promotional rates"
  }
]

Example 5: Check Commission Count

• Count Active Commissions Request:

curl -X GET "http://localhost:8080/api/p-2-p-commissions/count?fee.greaterThan=0.0" \
  -H "Authorization: Bearer TOKEN"

Response:

12

---

Error Handling

Error Response Format

[!failure] RFC 7807 Problem Details All errors follow standardized format.

{
  "type": "https://www.jhipster.tech/problem/{error-type}",
  "title": "Error Title",
  "status": 400,
  "detail": "Detailed error message",
  "path": "/api/p-2-p-commissions",
  "message": "error.code",
  "entityName": "pkbillmsP2PCommission",
  "errorKey": "fieldName",
  "params": "additionalInfo"
}

HTTP Status Codes

Code	Type	Description	Common Causes
201	Created	Resource created	Successful POST
200	OK	Success	Successful GET/PUT/PATCH
204	No Content	Deleted	Successful DELETE
400	Bad Request	Invalid request	Validation failure, ID mismatch, duplicate name
401	Unauthorized	Auth required	Missing/invalid token
403	Forbidden	Access denied	Insufficient permissions
404	Not Found	Resource missing	Invalid ID, deleted entity
409	Conflict	Resource conflict	Duplicate name
500	Server Error	Internal error	Database error, foreign key constraint

Validation Error Examples

[!bug] Field Validation Errors

Duplicate Name:

{
  "type": "https://www.jhipster.tech/problem/constraint-violation",
  "title": "Bad Request",
  "status": 400,
  "detail": "Commission name already exists",
  "path": "/api/p-2-p-commissions",
  "message": "error.existed.name",
  "entityName": "pkbillmsP2PCommission",
  "errorKey": "name"
}

Invalid Percentage Range:

{
  "type": "https://www.jhipster.tech/problem/constraint-violation",
  "title": "Method argument not valid",
  "status": 400,
  "path": "/api/p-2-p-commissions",
  "message": "error.validation",
  "fieldErrors": [
    {
      "objectName": "p2pCommission",
      "field": "up",
      "message": "must be between 0 and 100"
    }
  ]
}

Related to Group Error:

{
  "status": 400,
  "detail": "Cannot delete commission - it is related to a commission part group",
  "message": "error.related.to.group",
  "entityName": "pkbillmsP2PCommission",
  "errorKey": "id",
  "params": "P2pCommission"
}

---

Validation Rules

Field Constraints

Field	Rules	Error Messages
id	Null for POST	"cannot.have.id"
id	Not null for PUT/PATCH	"not.null"
id	Must match path ID	"not.equal.id"
name	Required	"name is required"
name	Must be unique	"existed.name"
up	0 ≤ value ≤ 100	"must be between 0 and 100"
down	0 ≤ value ≤ 100	"must be between 0 and 100"
fee	0 ≤ value ≤ 100	"must be between 0 and 100"
fromAmount	Optional	-
toAmount	Optional	-
commissionDetails	Optional (JSON format)	-
description	Optional	-

Business Rules

[!info] Business Validation

• name must be unique across all commissions

• fromAmount defines the minimum transaction amount for this commission

• toAmount defines the maximum transaction amount for this commission

• up is commission added on top of the transaction amount (percentage)

• down is commission deducted from the transaction amount (percentage)

• fee is an additional service fee (percentage)

• commissionDetails stores JSON string with additional configuration

• Cannot delete commission if it's associated with a commission part group

• All percentage fields (up, down, fee) must be between 0 and 100

---

Business Logic

Commission Structure

[!info] How Commissions Work

P2P commissions define the fee structure for peer-to-peer transfers:

Transaction Amount: 100,000 UZS
Commission Rule:
├── fromAmount: 50,000
├── toAmount: 500,000
├── up: 2.5% (added on top)
├── down: 0.0% (deducted from amount)
└── fee: 1.0% (service fee)

Calculation:
├── Base Amount: 100,000
├── Commission (up): 100,000 × 2.5% = 2,500
├── Service Fee: 100,000 × 1.0% = 1,000
└── Total Charged: 100,000 + 2,500 + 1,000 = 103,500

Commission Types

[!tip] Three Commission Components

1. UP Commission (up):

• Added on top of transaction amount

• Sender pays more than the transaction amount

• Example: 100,000 transfer with 2% up = 102,000 charged

2. DOWN Commission (down):

• Deducted from transaction amount

• Recipient receives less than the transaction amount

• Example: 100,000 transfer with 2% down = 98,000 received

3. Service Fee (fee):

• Additional flat percentage fee

• Usually combined with up or down

• Example: 100,000 transfer with 1% fee = 1,000 additional charge

Amount Range Matching

[!note] Transaction Routing

Commissions are selected based on transaction amount:

Amount Ranges:
├── 1,000 - 50,000: Small Transaction Commission (up: 3%)
├── 50,000 - 500,000: Medium Transaction Commission (up: 2%)
└── 500,000 - 10,000,000: Large Transaction Commission (up: 1%)

Transaction: 75,000 UZS
→ Matches: Medium Transaction Commission
→ Applied: 2% commission

Commission Part Groups

[!info] Grouping Commissions

Commissions can be organized into groups:

Commission Part Group: "HUMO Domestic"
├── Commission 1: Small Amount (1K-50K, up: 3%)
├── Commission 2: Medium Amount (50K-500K, up: 2%)
└── Commission 3: Large Amount (500K-10M, up: 1%)

Group Relationship:

• A commission can belong to one commission part group

• Groups organize related commissions together

• Cannot delete commission if associated with a group

• Groups are used in P2P parameters for routing

Commission Details JSON

[!note] Extended Configuration

The commissionDetails field stores JSON for additional settings:

{
  "type": "tiered",
  "category": "p2p_domestic",
  "processor": "payme",
  "effectiveDate": "2026-01-01",
  "expiryDate": "2026-12-31",
  "rules": {
    "maxDailyAmount": 10000000,
    "maxTransactionCount": 50
  }
}

Use Case Scenarios

Common Scenarios

Scenario 1: Standard Transfer

• Amount: 100,000 UZS

• Commission: up = 2.5%, fee = 1.0%

• Total charged: 103,500 UZS

Scenario 2: Large Transfer (Lower Rate)

• Amount: 5,000,000 UZS

• Commission: up = 1.0%, fee = 0.5%

• Total charged: 5,075,000 UZS

Scenario 3: Deduction Commission

• Amount: 50,000 UZS

• Commission: down = 3.0%

• Recipient receives: 48,500 UZS

---

🔧 cURL Command Reference

Create

curl -X POST http://localhost:8080/api/p-2-p-commissions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "name": "New Commission",
    "fromAmount": 10000,
    "toAmount": 100000,
    "up": 2.5,
    "down": 0.0,
    "fee": 1.0,
    "description": "Description of the new commission"
  }'

Create (Versioned)

curl -X POST http://localhost:8080/api/p-2-p-commissions/v1 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "name": "Versioned Commission",
    "fromAmount": 50000,
    "toAmount": 500000,
    "up": 2.0,
    "fee": 1.0,
    "description": "Commission using versioned endpoint"
  }'

Update

curl -X PUT http://localhost:8080/api/p-2-p-commissions/1 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "id": 1,
    "name": "Updated Commission",
    "fromAmount": 20000,
    "toAmount": 200000,
    "up": 3.0,
    "down": 0.5,
    "fee": 1.5,
    "description": "Updated description"
  }'

Partial Update

curl -X PATCH http://localhost:8080/api/p-2-p-commissions/1 \
  -H "Content-Type: application/merge-patch+json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"id": 1, "up": 2.8, "description": "New description"}'

Get All

curl -X GET "http://localhost:8080/api/p-2-p-commissions?page=0&size=10&sort=name,asc" \
  -H "Authorization: Bearer YOUR_TOKEN"

Get All (Filtered)

curl -X GET "http://localhost:8080/api/p-2-p-commissions?name.contains=Standard&up.greaterThan=2.0" \
  -H "Authorization: Bearer YOUR_TOKEN"

Get Single

curl -X GET http://localhost:8080/api/p-2-p-commissions/1 \
  -H "Authorization: Bearer YOUR_TOKEN"

Count

curl -X GET "http://localhost:8080/api/p-2-p-commissions/count?fee.greaterThan=1.0" \
  -H "Authorization: Bearer YOUR_TOKEN"

Delete

curl -X DELETE http://localhost:8080/api/p-2-p-commissions/1 \
  -H "Authorization: Bearer YOUR_TOKEN"

---

---