PATCH
/
v4
/
{multiCurr}
/
{id}
{
  "description": "<string>",
  "id": "<string>"
}

Path Parameters

​
multiCurr
enum<string>
required

Specific multicurrency template

Available options:
MULTICURR_DKK_DK,
MULTICURR_EUR_AT,
MULTICURR_EUR_DE,
MULTICURR_EUR_ES,
MULTICURR_EUR_FI,
MULTICURR_EUR_FR,
MULTICURR_EUR_IE,
MULTICURR_EUR_IT,
MULTICURR_GBP_GB,
MULTICURR_SEK_SE,
MULTICURR_EUR_NL,
MULTICURR_EUR_LU,
MULTICURR_EUR_BE,
MULTICURR_NOK_NO,
MULTICURR_EUR_PT,
MULTICURR_EUR_EE,
MULTICURR_EUR_LV,
MULTICURR_EUR_LT,
MULTICURR_EUR_MT,
MULTICURR_PLN_PL
​
id
string<biginteger>
required

The account id for given account

Query Parameters

​
auditUser
string
required

The audit user to log the request

Body

application/json

The fields that you want to apply to your newly cr, these values will override the predefined template values

Updating set values

​
address
object

Address connected to an account that will override the address set on customer level. This is for example used when sending out statements. Full address object is expected to be set when updating.

​
additionalValues
object[]

List of additional key-value pairs that can be associated with the account. Known keys:

  • BALC: Balance check configuration. Possible values: true (Shadow Balancing Disabled) or false (Shadow Balancing Enabled)
Maximum length: 4
​
customerId
string

Customer id for account owner

Example:

55667788990

​
name
string

Human readable name of an account

Maximum length: 64
Example:

"My example account name"

​
number
string

Unique account number for given account. Must be numeric if paymentRefence.type defined as MOD10 or FINNISH_7_3_1! Note that selected account numbers might be reserved by Enfuce for internal usage.

Maximum length: 64
Example:

123456789

​
reason
string

Reason for contract status change

Maximum length: 32
​
segment
enum<string>

Field enables to group an entity into a segment. This field will be exported but no logic is applied to this in Enfuce API

Available options:
SEGMENT_A,
SEGMENT_B,
SEGMENT_C,
SEGMENT_D,
SEGMENT_E,
SEGMENT_F
​
closureReason
enum<string>

Field enables to define entity's closure reason. This field will be exported but no logic is applied to this in Enfuce API

Available options:
CLOSED1,
CLOSED2,
CLOSED3,
CLOSED4,
CLOSED5
​
usageLimits
usageLimit · object[]
​
paymentReference
object

Number connected to account that will be used to map incoming payments to

​
status
enum<string>
Available options:
ACCOUNT_BLOCKED,
ACCOUNT_OK,
ACCOUNT_TO_CLOSE
​
creditLimit
number

Credit limit of the account

Example:

10000

​
externalBalanceCheck
boolean

The external balance check parameter enables the issuer to determine per account, whether the available balance during authorisation process should be checked by Enfuce or issuer (utilising Authorisation Control service). When set to “true”, Enfuce will not check the available balance of the account rather the issuer is expected to do it. As the parameter is set on account level, it will automatically apply to all cards linked to account in question. Please note that utilisation of this parameter requires implementation of the Authorisation Control service.

​
interestPostingEnabled
boolean

Indicates if interest posting enabled or disabled. With a boolean type of False, interest accrual is blocked, and with a boolean type of True, interest accrual will continue

Example:

true

​
underInvestigation
boolean

If account is under investigation

Example:

true

​
subAccountTemplates
enum<string>[]

Templates for sub accounts to be created. Check usage with Enfuce!

Response

Successful update of the account

​
description
string

Short description of the result of the action

​
id
string

Will contain the ID of the resource that has been created or updated