> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leapfinancial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get available receiving methods types

> Computes available receiving methods types for the corridor.



## OpenAPI

````yaml /raas/swagger-partner.json get /user/corridors/available-receiver-methodtypes/{userToken}
openapi: 3.0.0
info:
  title: ''
  version: 0.0.1
servers:
  - url: https://raas-partner-cv.nomas.cash/v1
security: []
paths:
  /user/corridors/available-receiver-methodtypes/{userToken}:
    get:
      tags:
        - Funding
      summary: Get available receiving methods types
      description: Computes available receiving methods types for the corridor.
      operationId: getAvailablePaymentMethods
      parameters:
        - description: User identifier or token.
          in: path
          name: userToken
          required: true
          schema:
            type: string
      responses:
        '200':
          description: >-
            **200 — OK.** Receiver method types for corridors.


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Types resolved | Valid user + tenant + corridor config. |
            `string[]` |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-available-payment-methods-scenario-matrix).
          content:
            application/json:
              schema:
                items:
                  type: string
                type: array
              example:
                - CreditCard
                - DebitCard
                - UBN
        '401':
          description: >-
            **401 — Unauthorized.**


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Missing / bad API key | Omit `api_key` or invalid key for corridor
            routes. | OpenAPI `401` via `@Response<ErrorResponse>`. |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-available-payment-methods-scenario-matrix).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                reason: Missing or invalid API key
        '404':
          description: >-
            **404 — Not found.**


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Unknown path user | `userToken` does not resolve to a stored user.
            | `ERROR_USER_NOT_FOUND` |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-available-payment-methods-scenario-matrix).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                reason: User not found for path userToken.
        '500':
          description: >-
            **500 — Internal server error.**


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Resolution failed | Tenant/corridor or unexpected error after user
            resolved. | `ERROR_INTERNAL_SERVER_ERROR` or `NumiError` `reason` |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-available-payment-methods-scenario-matrix).
          content:
            application/json:
              schema:
                properties:
                  reason:
                    type: string
                required:
                  - reason
                type: object
              example:
                reason: An unhandled error has occurred
      security:
        - api_key:
            - partner_full
            - partner_send
            - partner
components:
  schemas:
    ErrorResponse:
      properties:
        detail:
          type: string
        code:
          type: string
        reason:
          type: string
      required:
        - code
        - reason
      type: object
  securitySchemes:
    api_key:
      type: apiKey
      name: api_key
      in: header

````