-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathPlatformCurrencyConfig.yaml
More file actions
107 lines (107 loc) · 3.8 KB
/
PlatformCurrencyConfig.yaml
File metadata and controls
107 lines (107 loc) · 3.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
type: object
properties:
currencyCode:
type: string
description: Three-letter currency code (ISO 4217)
example: USD
minAmount:
type: integer
format: int64
description: >-
Minimum amount that can be sent in the smallest unit of this currency.
Note that the effective minimum for transactions may be higher than this
value if the underlying UMA provider enforces a higher minimum (see
umaProviderMinAmount). The effective minimum used in receiver lookups is
max(minAmount, umaProviderMinAmount).
minimum: 0
example: 100
maxAmount:
type: integer
format: int64
description: >-
Maximum amount that can be sent in the smallest unit of this currency.
Note that the effective maximum for transactions may be lower than this
value if the underlying UMA provider enforces a lower maximum (see
umaProviderMaxAmount). The effective maximum used in receiver lookups is
min(maxAmount, umaProviderMaxAmount).
minimum: 0
example: 1000000
umaProviderMinAmount:
type: integer
format: int64
description: >-
The minimum transaction amount enforced by the underlying UMA provider
for this currency, in the smallest unit of the currency. This is a
read-only value that reflects provider-level constraints such as minimum
trade values on the underlying exchange (which may be denominated in BTC
and converted to this currency at current rates). The effective minimum
for transactions is max(minAmount, umaProviderMinAmount).
readOnly: true
minimum: 0
example: 500
umaProviderMaxAmount:
type: integer
format: int64
description: >-
The maximum transaction amount enforced by the underlying UMA provider
for this currency, in the smallest unit of the currency. This is a
read-only value that reflects provider-level constraints. The effective
maximum for transactions is min(maxAmount, umaProviderMaxAmount).
readOnly: true
minimum: 0
example: 1000000
requiredCounterpartyFields:
type: array
items:
$ref: ../common/CounterpartyFieldDefinition.yaml
description: >-
List of fields which the platform requires from the counterparty
institutions about counterparty users. Platforms can set mandatory to
false if the platform does not require the field, but would like to have
it available. Some fields may be required by the underlying UMA provider.
example:
- name: FULL_NAME
mandatory: true
- name: BIRTH_DATE
mandatory: true
- name: NATIONALITY
mandatory: true
umaProviderRequiredUserFields:
type: array
items:
$ref: ../users/UserInfoFieldName.yaml
description: >-
List of user info field names that are required by the underlying UMA
provider when creating a user for this currency. These fields must be
supplied when creating or updating a user if this currency is intended to
be used by that user. If no fields are required, this field is omitted.
readOnly: true
example:
- NATIONALITY
- BIRTH_DATE
umaProviderRequiredCounterpartyUserFields:
type: array
items:
$ref: ../users/UserInfoFieldName.yaml
description: >-
List of fields that are required by the underlying UMA provider for this
currency. If the counterparty does not provide these fields, quote
requests will fail.
readOnly: true
example:
- FULL_NAME
- COUNTRY_OF_RESIDENCE
enabledTransactionTypes:
type: array
items:
$ref: ../transactions/TransactionType.yaml
description: List of transaction types that are enabled for this currency.
example:
- OUTGOING
- INCOMING
required:
- currencyCode
- minAmount
- maxAmount
- requiredCounterpartyFields
- enabledTransactionTypes