> ## 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 receiving methods > Retrieves the available receiving methods to get money via Request Money. ## OpenAPI ````yaml /raas/swagger-partner.json get /user/funding/source/get-receiving-methods/{userToken} openapi: 3.0.0 info: title: '' version: 0.0.1 servers: - url: https://raas-partner-cv.nomas.cash/v1 security: [] paths: /user/funding/source/get-receiving-methods/{userToken}: get: tags: - Funding summary: Get receiving methods description: >- Retrieves the available receiving methods to get money via Request Money. operationId: getReceivingMethods parameters: - description: User token. in: path name: userToken required: true schema: type: string - description: |- Source country code. ISO 3166-1 alpha-2. Example: `US` for United States, `MX` for Mexico. in: query name: sourceCountry required: false schema: type: string - description: |- Destination country code. ISO 3166-1 alpha-2. Example: `MX` for Mexico, `US` for United States. in: query name: destinationCountry required: false schema: type: string responses: '200': description: >- **200 — OK.** Receiving methods for RequestFunds. **Scenarios for this response**: | Scenario | How to reproduce | Typical `code` / body | |------------|------------------|------------------------| | SOF list | Valid tenant + user + query params. | `SourceOfFunding[]` | See also [Full scenario matrix](/raas/guides/testing-sandbox#get-receiving-methods-scenario-matrix). content: application/json: schema: items: $ref: '#/components/schemas/PartnerPayoutMethod' type: array example: - id: 6af8e158-be29-422a-8d69-703d6c343c3c name: VISA-1234 type: CreditCard isPrimary: true number: TOK_SANDBOX_9PNaaaqpqwertnD1jYkdw1_1234 '400': description: >- **400 — Bad request.** **Scenarios for this response**: | Scenario | How to reproduce | Typical `code` / body | |------------|------------------|------------------------| | Invalid tenant | Missing tenant id or tenant not found. | `ERROR_INVALID_TENANT` | See also [Full scenario matrix](/raas/guides/testing-sandbox#get-receiving-methods-scenario-matrix). content: application/json: schema: properties: reason: type: string required: - reason type: object example: reason: Bad request from funding layer. '401': description: >- **401 — Unauthorized.** **Scenarios for this response**: | Scenario | How to reproduce | Typical `code` / body | |------------|------------------|------------------------| | Missing / bad API key | Omit `api_key` or invalid `partner` key. | OpenAPI `401` via `@Response`. | See also [Full scenario matrix](/raas/guides/testing-sandbox#get-receiving-methods-scenario-matrix). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: reason: Missing or invalid API key '500': description: >- **500 — Internal server error.** **Scenarios for this response**: | Scenario | How to reproduce | Typical `code` / body | |------------|------------------|------------------------| | Service failure | `NumiError` or unexpected exception. | `ERROR_INTERNAL_SERVER_ERROR` or `NumiError` payload | See also [Full scenario matrix](/raas/guides/testing-sandbox#get-receiving-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 components: schemas: PartnerPayoutMethod: description: >- Partner API view of a payout / source-of-funding payment method. Properties are optional at the type level so partners can receive sparse payloads; individual endpoints may still validate required subsets at runtime. properties: id: type: string description: Stable identifier for the payment method when already persisted. name: type: string description: Cardholder or account display name. isPrimary: type: boolean description: >- When true, this method is the subscriber’s primary source of funding. accountNumber: type: string description: Bank account number (or equivalent account identifier for the rail). bankEntityNumber: type: string description: >- Bank or entity routing / CLABE-style identifier, depending on corridor. type: type: string description: >- Rail / instrument type (e.g. `BankAccount`, `DebitCard`, `CLABE`, `VNA`). expirationDate: type: string description: Card or instrument expiration date. expirationMonth: type: string description: Expiration month (string for leading zeros and channel consistency). expirationYear: type: string description: Expiration year (string for leading zeros and channel consistency). cardType: type: string description: Card product type label, e.g. `Credit` or `Debit`. number: type: string description: Primary account number or masked PAN as agreed for the integration. tokenData: type: string description: >- Opaque tokenized payload for the payment network (never raw PAN in logs). This is a JSON string. Deprecated. cardNetwork: type: string description: >- Card network / brand. Examples: `Visa`, `MasterCard`, `American Express`, `Discover`, `Diners Club`, `JCB`, `UnionPay`, `Maestro`, `Mir`, `Verve`, `Troy`, `UATP`. currency: type: string description: ISO 4217 currency code (e.g. `USD`, `MXN`). country: type: string description: ISO 3166-1 alpha-2 country code (e.g. `US`, `MX`). status: type: string description: >- Lifecycle / validation status string for the method. Values align with `PaymentMethodStatus` (e.g. `Created`, `Validated`, `Blocked`). allowPullCrossBorder: type: boolean description: Whether pull (debit) is allowed across borders for this card. allowPullDomestic: type: boolean description: Whether pull (debit) is allowed domestically for this card. allowPushCrossBorder: type: boolean description: Whether push (credit/load) is allowed across borders for this card. allowPushDomestic: type: boolean description: Whether push (credit/load) is allowed domestically for this card. allowReviewAddress: type: boolean description: Whether the network allows address review flows for this instrument. paymentMethodOwner: type: string description: VNA / corridor-specific method owner (e.g. `BCP`). externalId: type: string description: >- Partner or upstream system identifier for idempotent registration or correlation. canOperate: type: boolean description: >- Whether the instrument is allowed to operate (network / policy gate). type: object additionalProperties: false 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 ````