Update card
This operation will update given fields given a card id
Path Parameters
The card id for given card
Query Parameters
The audit user to log the request
Body
The account id card is linked to
"1234567890"
Address used to deliver card. Full address object is expected to be set when updating.
Valid card delivery types in API
CUSTOM_1
, CUSTOM_2
, CUSTOM_3
, CUSTOM_4
, CUSTOM_5
, MAIL
, COURIER
The customer id card is linked to
"1234567890"
Default set of allowed characters for fields embossed onto the card:
A-Z, a-z, Áá, Ää, Åå, Ææ, Éé, Íí, Ðð, Óó, Öö, Øø, Úú, Üü, Ýý, Þþ, 0-9, symbols -/.,&+' and space.
For printed cards allowed characters are: (including the above)
ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõöøùúûüý þÿĀāĂ㥹ĆćĈĉĊċČčĎďĐđĒēĔĕĖėĘęĚěĜĝĞğĠġĢģĤĥĦħĨĩĪīĬĭĮįİıIJijĴĵĶķĸĹ ĺĻļĽľĿŀŁłŃńŅņŇňʼnŊŋŌōŎŏŐőŒœŔŕŖŗŘřŚśŜŝŞşŠšŢţŤťŦŧŨũŪūŬŭŮůŰűŲųŴŵ ŶŷŸŹźŻżŽžſǪǫȘșȚțȪȫȮȯȲȳḐḑṢṣẞỌọ
Printed or others characters sets must be agreed in advance.
Address used to deliver pin. Full address object is expected to be set when updating.
Valid pin delivery types in API
CUSTOM_1
, CUSTOM_2
, CUSTOM_3
, CUSTOM_4
, CUSTOM_5
, MAIL
, COURIER
, EPIN
Card ecomm and geo-region blocking
Reason for contract status change
32
Field enables to group an entity into a segment. This field will be exported but no logic is applied to this in Enfuce API
SEGMENT_A
, SEGMENT_B
, SEGMENT_C
, SEGMENT_D
, SEGMENT_E
, SEGMENT_F
CARD_OK
, CARD_BLOCKED
, SUSPECTED_FRAUD
, CARD_CLOSED_DUE_TO_FRAUD
, CARD_NO_RENEWAL
, CARD_LOST
, CARD_STOLEN
, CARD_CLOSED
Usage limits
Use cases:
- No spend or usage limits
If spend and usage should not be limited, then the default configuration is applied. By default, both the singleAmount and sumAmount are set to 0, indicating that no spend limit is set. The count is set to 9999999 indicating that a high (almost unlimited) number of transactions are allowed without any usage limit set.
__usageLimits.values.singleAmount__ = 0
__usageLimits.values.sumAmount__ = 0
__usageLimits.values.count__ = 9999999
2. Spend limit per transaction
If the maximum spend should be limited for the defined transaction type, set the singleAmount to the desired maximum. If only the singleAmount is set, then both the singleAmount and the count will default to 0 indicating that there is no cumulative spend limit and the number of allowed transactions are not limited.
Example: Maximum allowed spend per transaction is 1000
__usageLimits.values.singleAmount__ = 1000
__usageLimits.values.sumAmount__ = 0
__usageLimits.values.count__ = 0
3. Cumulative spend limit
If the amount spent under a time period should be limited, set the sumAmount to the desired maximum. If only the sumAmount is set, then both the singleAmount and the count will default to 0 indicating that there is no limit on the number of allowed transactions or on single amounts.
Example: Maximum allowed spend under a certain period of time is 1200
__usageLimits.values.singleAmount__ = 0
__usageLimits.values.sumAmount__ = 1200
__usageLimits.values.count__ = 0
4. Usage limit
If the number of allowed transaction under a time period should be limited, set the count to the desired maximum. If only the count is set, then both the singleAmount and the sumAmount will default to 0 indicating that there is no limit on the allowed amounts.
Example: Maximum number of allowed transactions under a certain period of time is 5
__usageLimits.values.singleAmount__ = 0
__usageLimits.values.sumAmount__ = 0
__usageLimits.values.count__ = 5
5. Combinations of usage and spend limits
If multiple limits should apply, set each applicable limit to the desired value. Any unset limiter will default back to 0.
Example: Limit the allowed number of transactions to 5 and the allowed amount to 1000 under a certain period of time
__usageLimits.values.singleAmount__ = 0
__usageLimits.values.sumAmount__ = 1000
__usageLimits.values.count__ = 5
6. Restrict Usage
To disable a specific use case for the card—such as ATM transactions—set all corresponding values for that usage type to 0.
Example: Disable ATM usage by setting all limits to 0
__usageLimits.values.singleAmount__ = 0
__usageLimits.values.sumAmount__ = 0
__usageLimits.values.count__ = 0
This flag will indicate current status for PIN generation. If not specified system will automatically assign D as default and make sure a PIN is calculated during next embossing process. If set to W, then card will be excluded from embossing process until a PIN has been set and status has been updated to S. It is also possible to revert to D, in order for system to generate PIN. Note that system will update to status S automatically when a PIN is set successfully.
New card
In order for a new card to not get a system generated PIN then pinStatus flag must be set to W when created, this will then halt the embossing process for given card until a PIN has been set.
Reissue card
When reissuing a card it is possible to set pinStatus to W in order to hold embossing process for given card until a PIN has been set. Update pinStatus is done on same card id that is reissued.
Replace card
When replacing a card it is possible to set pinStatus to W in order to hold embossing process for given card until a PIN has been set. Update pinStatus is done on new card id that is returned when replacing.
- D - default and a random PIN will be generated
- W - waiting for PIN to be manually set
- S - PIN has been set successfully
D
, W
, S