How vusalabdurahmanovx/epoint-az works
epoint-az is a small Python client for E-Point payment flows. An application calls the client to build and sign checkout, saved-card, wallet, token-widget, reversal, or status requests; the client sends them to E-Point and returns a normalized response. In the other direction, applications can pass callback data to the client for verification and decoding, then use bank-code lookups to interpret results. The graph reflects the sampled client implementation and README; unsampled method details are not expanded.
Main entry points: client.py HTTP transport · codes.py Bank code lookup
Components 10
Payment requests
- EPointClient
src/epoint_az/client.py - Payment operations
src/epoint_az/client.py - Payload signing
src/epoint_az/client.py - HTTP transport
src/epoint_az/client.py - HTTP response
src/epoint_az/client.py
Callback results
- Callback verification
src/epoint_az/client.py - Decoded callback
src/epoint_az/client.py
Bank codes
- Bank code lookup
src/epoint_az/codes.py
Other components
- Integrating application
- E-Point API
Connections 11
- Integrating application → EPointClient: calls
README.md - EPointClient → Payment operations: exposes
src/epoint_az/client.py - Payment operations → Payload signing: builds and signs
src/epoint_az/client.py - Payment operations → HTTP transport: posts through
src/epoint_az/client.py - HTTP transport → Payload signing: encodes with
src/epoint_az/client.py - HTTP transport → E-Point API: sends request
src/epoint_az/client.py - HTTP transport → HTTP response: parses response
src/epoint_az/client.py - Integrating application → Callback verification: submits data
README.md - Callback verification → Decoded callback: decodes to
src/epoint_az/client.py - Decoded callback → Bank code lookup: looks up code
src/epoint_az/client.py - Integrating application → Bank code lookup: queries
README.md