---
title: Business types
slug: concepts/payments/cos-card-payments/business-types
description: Business types classify transaction purposes and are sent to card networks. In APIs, businessType codes map to Visa BAI or Mastercard TTI codes for push/pull payments.
docTags: 
createdAt: 2024-11-04T15:36:12.525Z
---

## Cross River business types

Business types define the purpose of transactions according to specific categories. The business type is passed on to the card network when making a transaction. Business types are sometimes called *use cases*.

In our APIs, the `businessType` identifier is a two-character code Cross River uses to identify the purpose of a push or pull payment. We ultimately pass these to the Visa Direct and MasterCard Send payment rails as BAI codes (Visa) or TTIs (MasterCard).

## Purpose of business type code

Business type codes determine the following: 

- The data that a push or pull payment message must contain.
  Some business types require additional information in the request. For example a value of **PP** (person to person) for the `businessType` means the `correspondingEntity` object is required.
- The limits and economic conditions relevant to a particular transaction.

Based on the business type, a payment sender or receiver can make an authorization decision.

## Source of the business type code

The possible business type for a transaction is determined together with Cross River and the card networks during onboarding and is based on the use case of the money movement.

If you are approved for only a single business type, Cross River configures this for you, so the information properly passes to the card networks. This is your *Default Business Type*. In this case it is not necessary to pass the `businessType` in the API request.

If you are approved for multiple business types, you can pass a specific`businessType` code in the API request, to be passed along to the card networks. Otherwise, Cross River will pass the Default Business Type for you. 

### Business type codes

| Code | Application type                | Payment category   |
| ---- | ------------------------------- | ------------------ |
| AA   | Account to account              | Money transfer     |
| BB   | Business to business            | Funds disbursement |
| CD   | Cash deposit                    | Money transfer     |
| CP   | Card bill payment               | Money transfer     |
| FD   | Funds disbursement (general)    | Funds disbursement |
| FT   | Funds transfer                  | Money transfer     |
| PP   | Person to person                | Money transfer     |
| WT   | Wallet transfer                 | Money transfer     |
| BI   | Money transfer (bank-initiated) | Money transfer     |
| CI   | Cash In                         | TDB                |
| CO   | Cash Out                        | TDB                |
| GD   | Government disbursement         | TDB                |
| GP   | Gambling payout                 | TDB                |
| LO   | Loyalty credits and rebates     | TDB                |
| MD   | Merchant disbursement           | TDB                |
| MP   | Face-to-face merchant payment   | TDB                |
| OG   | Online gambling payout          | TDB                |
| PD   | Payroll Disbursement            | TDB                |
| TU   | Prepaid Card Load or Top-Up     | Money transfer     |

In the framework of *money transfers*: 

- AA applies to transactions where sender and recipient are the same person.
- PP is when sender and recipient are *not* the same.

## Corresponding entity

In card payments, corresponding entities are either the receiver of a pull transaction (AFT) or the sender of a push transaction (OCT). This information must be included in the request for money transfers (business type code: AA, PP, BI, CD, FT, WT, CP, TU) in the `correspondingEntity` object of the request.