Introduction

The terms used across the Astrada API and these guides, in one place. Where a term is returned by the API, the entry names the field. For how the resources relate to each other, see Core Resources.

Accounts and cards

Account

The tenant Astrada provisions for your organization. It sets which networks, countries and card types you can enroll. Every subaccount operates within it. See Core Resources and Account & Subaccount Configuration.

Subaccount

A segment of your account, usually one per customer of yours: a company whose cards you enroll, not an individual cardholder. That customer's network bulk feeds, card subscriptions and transactions belong to its subaccount. See Subaccounts.

Card

The physical or virtual payment card: its network, country of issuance, expiry date and other facts that do not change. See Cards, Subscriptions, and Verifications.

Card subscription

The enrollment of a card in a subaccount. Its state says whether data is flowing, and enrollmentType says how the card was enrolled: cardholder-single (the cardholder entered one card), network-bulk (the card came from a network bulk feed) or bank-feed (the card came from a bank connection). Fetch it with expand=card,cardholder to get the card and the cardholder in the same response. See Cards, Subscriptions, and Verifications and Retrieve a card subscription.

Cardholder

The person a card belongs to: name, email, postal code and their company details in corporate. Only cards enrolled through a network bulk feed have one, and its values come from the feed unless they were set with PATCH /cards/{cardId}/cardholder. See Retrieve a cardholder.

Bulk enrollment

Network bulk feed

A feed of a company's cards that the bank or card network sends to Astrada, so the cards are enrolled without each cardholder signing up. Each feed is identified by its network reference and belongs to one subaccount. See Network Bulk Enrollment and Sandbox Bulk Enrollment.

Network reference

The identifier of a network bulk feed, as the card network knows it. Its format depends on the network:

The setup guides for corporates explain where each network reference comes from: American Express, Mastercard and Visa.

RPIC and PIC

Visa's identifier for a company's card feed, made of four IDs joined by underscores: Region, Processor, Issuer and Company (RegionId_ProcessorId_IssuerId_CompanyId). The PIC is the same thing without the Region (ProcessorId_IssuerId_CompanyId). The last segment, the C, is always the company ID.

Company ID

The identifier the bank or card network gives a cardholder's company in the network bulk feed. It is returned as cardholder.corporate.id, and every card from the same company has the same value.

Legal entity

The legal company within a company ID that a card belongs to, for example one subsidiary of a group. It is returned as cardholder.corporate.legalEntity, with an id and a name, when the card network supplies a company hierarchy. For Visa VCF it is the hierarchy node directly under the root (the root being the company). It is absent, never null, when the feed has no hierarchy.

Employee ID

The identifier of the cardholder as an employee of their company, returned as cardholder.corporate.employeeId. alternativeEmployeeId holds a second identifier for some enterprise integrations.

Delivery rail

The route a network bulk feed's data takes, returned as the feed's type: GL for American Express, SMARTDATA for Mastercard, and VBDS or VCF for Visa. It is null for a Visa feed created without a type while its rail is still being discovered. See Network Bulk Enrollment.