|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Easy Get Paid (ranked 4845 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/JQvHM4c1pF0TqqC6AK7RU_easy_get_paid_json.jsonGENERAL INFORMATION
<h1>Welcome to EGP Switch</h1>
<p>Here you can review transaction types supported by our platform and the definitions of the web services.</p>
<h2>Service Families</h2>
<p>We divide our services on several families. Each family has it's own transaction types as described below.</p>
<pre>
<strong>EGPS100 family - CLARO</strong>
EGPS121 - Chip
EGPS122 - Reversal
EGPS123 - Adjustment
EGPS124 - Swipe
EGPS125 - Keyed
EGPS126 - Keyed recurrent
EGPS128 - Keyed check-in / pre authorization
EGPS129 - Keyed check-out / authorization
EGPS130 - Keyed MSI
EGPS131 - Keyed MCI
EGPS132 - Keyed deferred payment
<strong>EGPS200 family - DUKPT</strong>
EGPS221 - Chip
EGPS222 - Reversal
EGPS224 - Swipe
EGPS227 - RSA key initialization
<strong>EGPS300 family - mPOS (TLV deserialization)</strong>
EGPS321 - Chip
EGPS324 - Swipe
<strong>EGPS400 family - Semi DUKPT</strong>
EGPS421 - Chip
EGPS424 - Swipe
EGPS427 - RSA key initialization
<strong>EGPS600 family - Agregador
...
Contact
- Name: vmosso@csa-consultores.com
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API7:2023
PERFORMANCE 0/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 5,000 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 1/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 2.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 0/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!