Worldline | Unauthorized

Documentation

Home
Features
- Getting started
- Overview
- Supported currencies
- Card based
  - Authorizations
    - Authorization
    - Partial approval
    - Authorization validity
  - Pre-Authorization adjustments
  - Cardholder verification
    - Card Security Code
    - Strong Customer Authentication
    - SCA Exemptions
    - Account verification
    - Address verification service
  - Card-On-File
  - Dynamic Currency Conversion
  - Reversals
    - Authorization reversal
    - Technical reversal
  - Captures
  - Refunds
    - Referenced refund
    - Standalone refund
- Additional features
  - Retrieve payment
  - Retrieve refund
- References
  - MCC codes
Developer Tools
- Overview
- API
  - API overview
  - Environments
  - API versioning
  - API authentication
  - Error handling
    - General
    - Bad Request
    - Unauthorized
    - Forbidden
    - Not found
    - Method Not Allowed
    - Conflict
    - Internal Server Error
  - Response handling
- Software Developer Kits
  - .NET SDK
  - Go SDK
  - Java SDK
  - Node.js SDK
  - PHP SDK
  - Python SDK
  - Ruby SDK
Support
API Reference

worldline

Documentation

401 - Unauthorized

Description

Authentication is required and has failed or has not yet been provided. This response indicates that the client must authenticate itself to get the requested response.

Common Scenarios

Missing token : The token is not provided in the request headers..
Incorrect header : The token is provided in a incorrect HTTP header.
Incorrect header prefix : The Authorization header does not contain the right prefix.

Resolution Steps

Confirm that you retrieve a valid token.
Ensure that the token is provided in the Authorization HTTP header
Ensure that the Authorization HTTP header contains "Bearer " as prefix.
Check the API documentation for proper authentication methods and requirements.