Skip to content

feat: implement EMSP role for Payments module (2.3.0) #14

@alfonsosastre

Description

@alfonsosastre

Description

The Payments module in OCPI 2.3.0 only implements CPO (receiver) and PTP roles. The EMSP role is missing, making the payments module asymmetric and incomplete.

Current state

  • ocpi/modules/payments/v_2_3_0/api/cpo.py — implemented
  • ocpi/modules/payments/v_2_3_0/api/ptp.py — implemented
  • ocpi/modules/payments/v_2_3_0/api/emsp.pymissing

No EMSP router is registered for payments in ocpi/routers/.

Expected

Full EMSP sender/receiver interface for the Payments module, following the same pattern as other modules (e.g. sessions, cdrs).

Acceptance criteria

  • ocpi/modules/payments/v_2_3_0/api/emsp.py implemented
  • EMSP payments router registered in ocpi/routers/
  • Tests in tests/test_modules/test_v_2_3_0/test_payments/test_emsp.py

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions