How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Geidea Transaction Management API

Capture, void, refund, cancel, and fetch transactions and orders.

Geidea Transaction Management API is one of 6 APIs that Geidea publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 3 base URLs: https://api.ksamerchant.geidea.net, https://api.merchant.geidea.net, https://api.geidea.ae.

5 operations 5 paths 4 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.merchant.geidea.net
Authentication
HTTP Basic
Contact
Resource Areas
1

Authentication & Security 1

Geidea Transaction Management API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using the merchant Public Key as the username and the API Password as the password. Requests additionally carry an HMAC signature fie…

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Transaction Management 5

Capture, void, refund, cancel, and fetch transactions and orders.

POST
/pgw/api/v1/direct/capture
Capture Transaction
captureTransaction body → 200401
POST
/pgw/api/v3/direct/void
Void Payment
voidPayment body → 200401
POST
/pgw/api/v2/direct/refund
Refund - Full or Partial
refund body → 200401
POST
/pgw/api/v1/direct/cancel
Cancel Order
cancelOrder body → 200401
GET
/pgw/api/v1/direct/order/{orderId}
Fetch Transaction or Order
getOrder 1 param → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are AmountOperationRequest (5 properties), Error (4 properties), OrderResponse (3 properties), OrderReferenceRequest (2 properties). Each schema is shown below with its type and property counts.

Error
object
4 properties
OrderResponse
object
3 properties
AmountOperationRequest
object
5 properties 1 required
OrderReferenceRequest
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

geidea-transaction-management-api-openapi.yml Raw ↑

Other APIs Geidea publishes across the network.

Geidea Pay by Link API
Geidea Pay by Invoice API
Geidea Checkout API
Geidea Direct API API
Geidea Tokenization API
Where this information came from

This is an independent, third-party profile of Geidea Transaction Management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.