Card payments
Transaction management
Business types
5min
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) what the business type code does 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 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 who provides the business type 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 the businesstype code in the api request, to be passed along to the card networks 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 credit card bill payment fd funds disbursement (general) funds disbursement ft funds transfer money transfer pp person to person money transfer wt wallet transfer 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 pp and aa money transfers in the correspondingentity object of the request related api reference transaction management