Implementation
Overview
Geopagos provides a transactional API designed to enable your application to accept payments using your own physical device.
Sequence diagram
This flow represents a generic way to perform an authorization.
info
the application backend can be provided by the implementor or Geopagos.
Sale
| Operation | Method | Endpoint | |
|---|---|---|---|
| Initialize | POST | /api/v4/payments/present | Documentation |
| Request authorization | POST | /api/v1/sales | Documentation |
| Confirm authorization | POST | /api/v1/sales/confirm | Documentation |
| Confirm | POST | /api/v4/payments/{reference_number}/confirm | Documentation |
Refund
| Operation | Method | Endpoint | |
|---|---|---|---|
| Initialize | POST | /api/v4/refunds/present | Documentation |
| Request authorization | POST | /api/v1/refunds | Documentation |
| Confirm authorization | POST | /api/v1/refunds/confirm | Documentation |
| Confirm | POST | /api/v4/refunds/{reference_number}/confirm | Documentation |
Annulment
| Operation | Method | Endpoint | |
|---|---|---|---|
| Request authorization | POST | /api/v1/annulments | Documentation |
| Confirm authorization | POST | /api/v1/annulments/confirm | Documentation |
| Confirm | POST | /api/v4/refunds/{reference_number}/confirm | Documentation |
info
If the application backend doesn't send the final confirmation (last step), the transaction will be reversed.
More information
See the API Reference for detail information about the integration.