Authentication Overview

Localpayment uses OAuth 2.0 Bearer token authentication to secure API access. All API requests require a valid access token included in the Authorization header. This guide provides an overview of authentication concepts and security requirements.

Overview

Secure authentication is fundamental to API integration. Localpayment's token-based authentication ensures only authorized requests can access your account data and process transactions.

Security Requirements

🔒

Critical Security Requirements: Follow these practices to ensure secure API integration

Authentication Endpoints

Manage your API authentication using these dedicated endpoints:

Quick Example

Generate Token:

curl --request POST \
     --url https://api.stage.localpayment.com/api/token/ \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "username": "[email protected]",
  "password": "KD##ow^&Z2zD6^2FL29m"
}
'

Use Token:

curl --request POST \
     --url https://api.stage.localpayment.com/api/validation/document \
     --header 'Authorization: Bearer <your_access_token>' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "country": "ARG",
  "document": {
    "id": "1791234561009",
    "type": "RUC"
  }
}
'

Token Expiration

Localpayment uses short-lived tokens for enhanced security:

Token Refresh Flow

1. Initial Authentication: Get access and refresh tokens
2. API Requests: Use access token for 5 minutes
3. Token Expiry: Receive 401 Unauthorized response
4. Token Refresh: Use refresh token to get new access token
5. Continue Requests: Use new access token for API calls

💡

Implementation Tip: Build automatic token refresh into your integration. Check token expiration and refresh proactively to avoid 401 errors during API operations.

Error Handling