geowallet
    • Overview
    • Authentication
    • APIs
      • Ledger Balance
        • Get Balance of all ledgers
        • Get Balance for a single currency
      • Funding
        • Get deposit instruments
      • Payers
        • Create original payer
      • Beneficiaries
        • Create beneficiary
      • Quotes
        • Get FX quotation
      • Payments
        • Confirm quote and create payment
        • Payment result inquiry
      • Files
        • Create file upload session
        • Get file processing status
        • Upload file binary to pre-signed URL
    • Payment Status Webhook
    • About Us
    • Schemas
      • ErrorResponse
      • DepositInstrumentsResponse
      • DepositInstruction
      • FiatBankAccount
      • CreatePayerRequest
      • PayerInfo
      • IdentityInfo
      • Address
      • CompanyInfo
      • Director
      • UBO
      • DocumentReference
      • CreatePayerResponse
      • CreateBeneficiaryRequest
      • BeneficiaryInfo
      • BeneficiaryBankAccount
      • IntermediaryBank
      • OriginatorInfo
      • LocalClearing
      • CreateBeneficiaryResponse
      • QuoteRequest
      • QuoteResponse
      • PaymentRequest
      • PaymentInstruction
      • Amount
      • Compliance
      • Metadata
      • PaymentResponse
      • FileUploadSessionRequest
      • FileUploadSessionResponse
      • FileStatusResponse

    Overview

    The GeoSwift Platform API is a RESTful interface that provides programmatic access to GeoSwift's global payment and compliance infrastructure.
    All endpoints return JSON-formatted responses and adhere to standard HTTP methods, status codes, and idempotency patterns.

    Before You Start#

    To integrate with the GeoSwift API, ensure you have the following:
    1.
    Valid API Credentials
    Obtain your Client ID, API Key, and Secret Key from the GeoSwift Partner Dashboard. These credentials are used for application identification and request signing.
    2.
    Understanding of Multi-Layer Authentication
    The API enforces a three-layer security model:
    Application identity via X-API-Key and X-Client-ID
    Scoped authorization via short-lived OAuth 2.0 Bearer tokens
    Request integrity and anti-replay protection via HMAC-SHA256 signatures
    Familiarity with cryptographic signing and secure credential handling is required.
    3.
    RESTful API Fundamentals
    Basic knowledge of HTTP methods (POST, GET, etc.), headers, JSON payloads, and idempotency is recommended for effective integration.

    Core API resources#

    ResourcePurpose
    PaymentPayment creation and execution
    Modified at 2026-03-12 10:41:51
    Next
    Authentication
    Built with