Papaya Global · Controlled Vocabulary

Papaya Global Vocabulary

0 Terms Updated
View Vocabulary File View on GitHub

Papaya Global publishes a controlled vocabulary on the APIs.io network, but no terms could be read from it — the file declares no recognizable term collection. Treat the count as unknown rather than as zero.

Terms

No terms could be read from this vocabulary file — it declares no recognizable term collection. The source file is linked above.

Controlled Vocabulary

Raw ↑
vocabulary:
  - term: Wallet
    definition: >
      An organizational account that stores balances in a configured currency (USD, GBP, EUR, etc.)
      and is used to fund payment instructions. Wallets belong to the organization, not to individual
      beneficiaries. Each wallet has a unique ID, currency, balance, and funding bank details.
    related:
      - WalletStatement
      - PaymentGroup
      - PaymentInstruction

  - term: WalletStatement
    definition: >
      A record of all transactions processed through a wallet within a specified date range,
      including debits, credits, fees, exchange rates, and running balance. Used for reconciliation
      and audit purposes.
    related:
      - Wallet

  - term: PaymentGroup
    definition: >
      A logical container for consolidating payment instructions based on criteria such as time period,
      location, or business unit. Groups can be locked to prevent further modifications and are
      associated with a specific wallet. Locking a group signals readiness for approval and execution.
    related:
      - Wallet
      - PaymentInstruction

  - term: Beneficiary
    definition: >
      A payment recipient — either an individual or a company — who receives payments via the Papaya
      Global platform. Each beneficiary has entity information (name, address), bank details,
      country, and currency. Beneficiaries must be created before payment instructions can reference them.
    related:
      - BankDetails
      - Entity
      - PaymentInstruction

  - term: BankDetails
    definition: >
      Banking information required to route a payment to a beneficiary. The required fields vary
      significantly by country and currency (e.g., BSB + account number for Australia, IBAN + BIC
      for SEPA). Use the schema endpoint to retrieve the correct field structure for a given
      country/currency/entity_type combination.
    related:
      - Beneficiary

  - term: Entity
    definition: >
      The identifying information for a beneficiary, such as full name, date of birth, and address
      for individuals, or company name and registration details for companies. Structure varies
      by entity_type and country.
    related:
      - Beneficiary

  - term: PaymentInstruction
    definition: >
      A record specifying a payment to be made from an organizational wallet to a beneficiary,
      including amount, currency, execution date, purpose, and approval status. Payment instructions
      go through a lifecycle: created → approved → executed (sent).
    related:
      - Beneficiary
      - Wallet
      - PaymentGroup
      - PaymentStatus

  - term: PaymentStatus
    definition: >
      The current state of a payment instruction in its lifecycle. Common statuses include
      pending (created but not approved), approved (ready for execution), processing (being
      executed), completed (successfully sent), cancelled, and failed.
    related:
      - PaymentInstruction

  - term: AccessToken
    definition: >
      A JWT (JSON Web Token) obtained by providing an API key and client secret to the /token
      endpoint. Tokens are valid for 24 hours and must be included in the Authorization header
      as a Bearer token for all API requests. Separate credentials exist for sandbox and production.
    related:
      - APIKey
      - ClientSecret

  - term: APIKey
    definition: >
      A unique identifier assigned to an API client. Combined with a client_secret to obtain
      access tokens. Must be kept confidential and never exposed in client-side code or
      public repositories.
    related:
      - AccessToken

  - term: ImportJob
    definition: >
      An asynchronous background job for bulk operations such as importing multiple beneficiaries
      or payment instructions at once. Returns a job_id that can be polled to check status,
      progress, and any failed records.
    related:
      - Beneficiary
      - PaymentInstruction

  - term: UserTags
    definition: >
      Custom key-value metadata that clients can attach to beneficiaries, wallets, payment groups,
      and payment instructions for filtering, categorization, and reconciliation purposes
      (e.g., department, employee_id, payroll_cycle).
    related:
      - Beneficiary
      - Wallet
      - PaymentGroup
      - PaymentInstruction

  - term: CollectInformation
    definition: >
      A feature that generates a secure, time-limited URL allowing a beneficiary to self-serve
      enter their own bank details, reducing the need for organizations to handle sensitive
      banking data directly. The URL expires after a set period.
    related:
      - Beneficiary
      - BankDetails

  - term: Webhook
    definition: >
      An HTTPS callback notification sent from Papaya Global to a pre-configured endpoint
      when events occur (e.g., payment completed, status changed). Webhooks are set up through
      the account manager and require IP whitelisting. They provide real-time event-driven
      integration without polling.
    related:
      - PaymentInstruction
      - PaymentStatus

  - term: RateLimit
    definition: >
      API usage constraint of 500 requests per minute per authenticated user. Rate limit status
      is communicated via response headers: X-RateLimit-Limit, X-RateLimit-Remaining,
      X-RateLimit-Used, and X-RateLimit-Reset. Exceeding the limit returns HTTP 429.
    related:
      - AccessToken

  - term: Sandbox
    definition: >
      A non-production environment for testing API integrations without processing real payments.
      The sandbox has its own separate credentials and base URL
      (https://sandbox.papayaglobal.com/api/v1). Use the API Test page in docs for interactive
      sandbox testing.
    related:
      - AccessToken

Work with this as data

Every vocabulary here is available over the APIs.io API and to AI agents over MCP. Vocabularies is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for vocabularies

3 MCP tools reach this
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=papaya-global-vocabulary&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/papaya-global-vocabulary"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.