Get available receiving methods types

curl --request GET \
  --url https://raas-partner-cv.nomas.cash/v1/user/corridors/available-receiver-methodtypes/{userToken} \
  --header 'api_key: <api-key>'

[
  "CreditCard",
  "DebitCard",
  "UBN"
]

GET

user

corridors

available-receiver-methodtypes

{userToken}

Get available receiving methods types

curl --request GET \
  --url https://raas-partner-cv.nomas.cash/v1/user/corridors/available-receiver-methodtypes/{userToken} \
  --header 'api_key: <api-key>'

[
  "CreditCard",
  "DebitCard",
  "UBN"
]

Authorizations

api_key

string

header

required

Path Parameters

userToken

string

required

User identifier or token.

Response

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[]`