LogoLogo
NymCardAPI catalogContact usnFront catalog
  • NYMCARD DOCUMENTATION
  • Get Started
    • nCore API Quick Tutorial
    • API Core Principles
    • Program management
      • Manage documents by APIs
      • User KYB process
      • Necessary parameters per user type
      • User ID verification by SDK
      • User KYC process
    • Issuance
      • Users
      • Cards
    • Issuing Physical Cards
      • Individual card issuance
      • Bulk card issuance
      • Card fulfillment
      • Card PIN management
      • Card replacement
      • Proxy number usage
    • Issuing Virtual Cards
      • Migration of virtual to physical card
    • Funding and transfers
      • Funding
      • Internal funding source
      • External funding source
        • From card
        • From bank account
        • Lean API flow
        • DAPI direct API flow
      • Transfers
      • Western Union APIs
    • Product Management
      • Card product
      • Balance limits
      • Velocity limits
      • Fees
      • Charges
      • Multi-currency
      • Authorization controls
        • Enhancements for MCC list management
    • Transactions
      • Payment ecosystem
      • Transaction lifecycle
      • Transaction types
      • Transaction endpoints scenarios
      • Multi-clearing process
    • Webhooks
      • Introduction to webhooks
      • nCore webhook events
      • Steps to configure a webhook
      • Webhooks samples
      • Webhook changes for simulation
      • Webhooks management
    • Security
      • PCI widget
      • 3D Secure
      • OTP SMS templates
    • Release announcements
      • Embedded Lending Release Notes
      • Changes in the release on 13/07/2023
      • Changes in the release on 23/05/2023
      • Changes in the release on 04/04/2023
  • For developers
    • nCore API catalog
    • nFront API catalog
Powered by GitBook
On this page

Was this helpful?

  1. Get Started
  2. Product Management
  3. Authorization controls

Enhancements for MCC list management

PreviousAuthorization controlsNextTransactions

Last updated 9 months ago

Was this helpful?

We’ve implemented enhancements for MCC list management.

Now you can have allowed and blocked MCCs in one list so that transactions can be authorized based on configured settings.

' API has the following updates:

  • "name" and "allow" parameters are removed

  • "mccs" parameter is changed to array list

MCC list can be updated even for ACTIVE card products using '' API.

'Update MCC list API': To add new mcc code(s), all existing mcc codes should be passed in the update payload in addition to the new one(s). To remove mcc code(s), all mcc codes should be passed in the update payload except for the one(s) to be removed.

Now the system creates and links default MCC list while creating card product with the ALL mcc codes = true (DEFAULT).

The impact on the existing card products/cards is the following:

  • Existing card product with no MCC list > MCC list will be created and linked to it (default of ALL = true)

  • Existing card product with one or more MCC lists (having some of the mcc codes = false) > migrated into 1 default MCC list with default ALL = true while the other MCC codes will still be read as "false".

Moreover, changes will be applied to the cards associated with the existing card products.

The below indicates that all MCC codes are supported:

"mccs": [
{
"mcc_id":"ALL",
"allow":true
} ]

The below indicates that all MCC codes are supported except for MCC code = "9852":

"mccs": [
{
"mcc_id":"ALL",
"allow":true
},
{
"mcc_id":"9852",
"allow":false
} ]

Also "allowed_mccs_id " parameter continues to be reflected in the response of the following APIs:

1. Get card product

2. Get list of card products

3. Create card product

4. Update card product

5. Create card

6. Update card

7. Get card details

8. Get list of cards

9. Get card authorization settings data

10. Update card authorization settings data

11. Change card status

The "allowed_mccs_id" parameter is removed from ' and '' APIs requests.

You can still create a new MCC list and add it at the card level via '' API.

Besides, you can find the list of supported MCCs in this.

'Update allowed MCCs list by ID
Update allowed MCCs list by ID
Create card product'
Update card product
Update card auth settings
GSG doc