Search...
Log inGet started
Airwallex logo
Home
Core API
Payments
Transactional FX
Payouts
Issuing
Back to home
OverviewHow Airwallex Issuing worksSupported regions and currenciesSupported card programs
Use Cases
Get started
Choose your issuing solutionFund your issuing balanceCreate cardholders
Create cards
Create commercial cards
Create consumer cardsPhysical and digital cardsWhitelabel card offeringCard statuses
Test and go live

Create commercial cards

Airwallex’s commercial cards enable you to pay for your business-related expenses. This tutorial guides you through the steps for creating personalized and non-personalized commercial cards.

Commercial cards can be issued to either Delegate or Individual type cardholders and can be personalized or non-personalized.

Create a commercial card

To create a commercial card, submit Create a card API request by providing the following fields.

  • program.purpose: Set this to COMMERCIAL to indicate that you want the card issued to a business.
  • program.type: The type of card. If you do not provide a value, the default configuration on your account setting is used. Possible values: PREPAID, DEBIT, CREDIT or DEFERRED_DEBIT.
  • program.sub_type: Sub type of the program. Possible values: B2B_TRAVEL, GOOD_FUNDS_CREDIT. This is used for specific products under the defined program types, e.g., B2B_TRAVEL which designates BINs for travel use cases such as OTAs.
  • created_by: Your full legal name.
  • request_id: Specify a unique request ID.
  • purpose: The purpose of the commercial card’s usage. If you do not provide a value, defaults to BUSINESS_EXPENSES. Other possible values: CLIENT_EXPENSES, MARKETING_EXPENSES, OFFICE_SUPPLIES, ONLINE_PURCHASING, OTHER, SUBSCRIPTIONS, TEAM_EXPENSES, TRAVEL_EXPENSES.
  • authorization_controls.allowed_transaction_count: Specify whether the card is a single (SINGLE) or multi-use (MULTIPLE) card. Single-use cards can only be used for one successful debit transaction.
  • authorization_controls.allowed_transaction_limits: Set limits on transactions such as transaction amount, intervals, etc. See Transaction limits.

The required input for the following fields will differ based on whether you opt to personalize or not personalize this commercial card.

Non-personalized commercial card requirements

  • is_personalized: Set this field to false if you want to create a non-personalized card. This allows the card to be assigned to a business with the business name used on the card. The card can be associated with multiple authorized cardholders.
  • form_factor: Set this to VIRTUAL as this is the only supported form for non-personalized cards.
  • cardholder_id: Provide the ID of either a DELEGATE or INDIVIDUAL type cardholder as returned in Create a Cardholder API response.
  • additional_cardholder_ids: Optional. The IDs of additional cardholders (up to a maximum of two) of either DELEGATE or INDIVIDUAL type that you want to associate this commercial card with. All cardholders including the primary cardholder represented in cardholder_id will receive 3DS OTP verification codes on the contact (email or mobile_number) listed on their cardholder record.

At least one cardholder is required at all times. If cardholder_id is not present and additional_cardholder_ids is empty the request is rejected.

Shell
Example request (Non-personalized commercial card)
JSON
Example response (Non-personalized commercial card)

Personalized commercial card requirements

  • is_personalized: Set this field to true if you want to create a personalized card. This allows the card to be assigned to a single named individual with their legal name used on the card.
  • form_factor: You can set it to VIRTUAL or PHYSICAL. Personalized cards can be added to digital wallet providers.
  • cardholder_id: Provide the ID of an INDIVIDUAL type cardholder as returned in Create a Cardholder API response.
Shell
Example request (Personalized commercial card)
JSON
Example response (Personalized commercial card)

Card API response

The response returns the card object with all the request fields, and the following card details:

  • card_id: A unique identifier of the card object. You can use this to:
  • card_number: A masked card number.
  • card_status: The status of the card (see Card statuses). The card will automatically transition from PENDING to ACTIVE for virtual cards so you can proceed to transact immediately.
On this page
  • Create a commercial card
  • Next steps