Card Enrollment Controls

Configure card enrollment controls to enforce card acceptance policies at the subaccount level, including card type, funding source, and country restrictions.

Introduction

Card enrollment controls are rules configured on a Subaccount that determine which cards are eligible for enrollment. When a card is submitted for enrollment, Astrada validates it against the target subaccount's controls and rejects cards that do not meet the configured criteria.

Controls are defined per network (Visa, Mastercard, Amex) and can be configured independently for cardholder individual enrollment (single-enrollment) and network bulk enrollment (bulk-enrollment).

Control Types

Each network's enrollment configuration supports three types of controls:

ControlFieldDescription
Country restrictionscountriesList of permitted countries of card issuance (ISO 3166 alpha-3). Cards issued outside these countries are rejected.
Card type restrictionsblockedCardTypesCard types to block from enrollment. For example, blocking CONSUMER cards restricts enrollment to commercial cards only.
Funding source restrictionsblockedFundingCardTypesFunding types to block from enrollment. For example, blocking DEBIT cards restricts enrollment to credit cards only.

These controls are nested under single-enrollment and bulk-enrollment within each network's configuration, allowing you to apply different policies per enrollment method.

Configuration

Enrollment controls are set through the subaccount's configurations object when you create or update a subaccount. Each network entry contains a top-level countries array for general eligibility, plus optional single-enrollment and bulk-enrollment objects for enrollment-specific controls.

Example Configuration

The following configuration allows Visa cards issued in the USA and Canada, blocks consumer cards and debit cards for single enrollment, and applies the same restrictions for bulk enrollment:

{
  "VISA": {
    "countries": ["USA", "CAN"],
    "single-enrollment": {
      "countries": ["USA"],
      "blockedCardTypes": ["CONSUMER"],
      "blockedFundingCardTypes": ["DEBIT"]
    },
    "bulk-enrollment": {
      "countries": ["CAN"],
      "blockedCardTypes": ["CONSUMER"],
      "blockedFundingCardTypes": ["DEBIT"]
    }
  },
  "MASTERCARD": {
    "countries": ["USA"],
    "single-enrollment": {
      "countries": ["USA"],
      "blockedCardTypes": ["CONSUMER"],
      "blockedFundingCardTypes": ["DEBIT"]
    },
    "bulk-enrollment": {
      "countries": ["GBR"],
      "blockedCardTypes": ["CONSUMER"],
      "blockedFundingCardTypes": ["DEBIT"]
    }
  }
}

In this example:

  • Visa single enrollment accepts only commercial, non-debit cards issued in the USA.
  • Visa bulk enrollment accepts only commercial, non-debit cards issued in Canada.
  • Mastercard single enrollment accepts only commercial, non-debit cards issued in the USA.
  • Mastercard bulk enrollment accepts only commercial, non-debit cards issued in the United Kingdom.

Scoping Per Subaccount

Each subaccount has its own set of enrollment controls. This allows you to:

  • Apply different card acceptance policies to different business units or programs
  • Restrict specific subaccounts to certain card types or regions without affecting others
  • Support multiple enrollment programs under a single account

Configurations at the subaccount level cannot exceed the capabilities of the parent account. For example, if your account supports cards issued in the USA and Canada, you cannot configure a subaccount to also accept cards from the United Kingdom. You can, however, restrict a subaccount to only accept cards from Canada. For more details, see Subaccounts.

Validation Behavior

When a card is submitted for enrollment, Astrada validates it against the target subaccount's controls. The same validation applies whether cards are enrolled individually or in bulk:

  • Card passes all checks — enrollment proceeds normally.
  • Card matches a blocked rule — the request is rejected with a validation response indicating which policy was violated. No partial or hidden enrollment occurs.

This behavior is consistent across both cardholder-single and network-bulk enrollment types, keeping outcomes predictable regardless of enrollment method.

API

Enrollment controls are managed through the Subaccount endpoints. See Create subaccount and Update subaccount in the API reference.