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.
Starting with the new version of sdk 19.1.15 the in-person payments flow, one of the methods has been deprecated for new integrations, although it will continue to function for previous versions during a transition period.
This update brings performance improvements and allows the removal of the /api/v1/sales/confirm call, as long as the new flow is properly implemented.
To enable this functionality, the /authorization_code/ field must be included in the response.
When this field is provided, the following endpoints are no longer necessary:
POST | /api/v1/sales/confirm
POST | /api/v1/refunds/confirm
POST | /api/v1/annulments/confirm
The value for authorization_code must be taken from the response received when calling POST /api/v1/sales.
You can see the details in Confirm a payment
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 | PATCH | /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 | PATCH | /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 | PATCH | /api/v4/refunds/{reference_number}/confirm | Documentation |
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.