Skip to main content

Overview

Yuno uses category codes to classify transactions, shipping methods, and payout purposes. These codes affect how providers process transactions, influence risk scoring, and determine regulatory compliance requirements.

Transaction Category Types

The transaction category indicates the nature of the payment and affects how providers handle authorization, settlement, and risk assessment.
CategoryCodeDescriptionUse Case
PurchasePURCHASEStandard one-time purchase of goods or servicesE-commerce checkout, in-app purchase
RecurringRECURRINGScheduled repeat charge on a stored payment methodMonthly subscriptions, membership fees
InstallmentINSTALLMENTPurchase split into multiple scheduled paymentsBuy-now-pay-later, installment plans
Pre-authorizationPRE_AUTHFunds reserved without immediate captureHotel check-in, car rental deposit
Account fundingACCOUNT_FUNDINGTransfer to a stored-value account or walletDigital wallet top-up, prepaid card load
Quasi-cashQUASI_CASHPurchase of items convertible to cashGift cards, money orders, lottery tickets
Set the transaction category in the transaction_type field of the payment request.

When to Use Each Category

PURCHASE. Use for all standard single-payment transactions. This is the default and most common category. RECURRING. Use when charging a customer on a schedule using a previously stored payment method. The first transaction in a recurring series should be flagged as the initial recurring payment. Subsequent charges reference the initial transaction. Card networks require clear disclosure of recurring terms to the cardholder. INSTALLMENT. Use when a single purchase is divided into multiple payments over time. The total number of installments and current installment number must be specified. Installment support varies by country and provider. It is widely used in Latin America (Brazil, Mexico, Colombia). PRE_AUTH. Use when you need to reserve funds before the final amount is known. Pre-authorizations must be captured or cancelled within the authorization window (typically 7 days for cards, varies by provider). ACCOUNT_FUNDING. Use for wallet top-ups and prepaid card loads. Some issuers apply different risk rules and limits to account funding transactions. QUASI_CASH. Use for items that can be readily converted to cash. These transactions may be subject to higher scrutiny and lower approval rates from some issuers.

Shipping Reference Types

Shipping type codes indicate how purchased goods will be delivered. Providers and risk engines use this information for fraud scoring.
Shipping TypeCodeDescriptionTypical Delivery Time
Same daySAME_DAYDelivery on the day of purchaseHours
Next dayNEXT_DAYDelivery on the next business day1 business day
Two dayTWO_DAYDelivery within two business days2 business days
StandardSTANDARDStandard ground shipping3-7 business days
InternationalINTERNATIONALCross-border shipping7-30 business days
Pick upPICK_UPCustomer picks up from store or locationN/A
DigitalDIGITALElectronic delivery (no physical shipment)Immediate
Set the shipping type in the shipping.type field of the payment request.
Transactions with DIGITAL shipping type and a physical shipping address may be flagged by fraud engines. Use DIGITAL only when there is no physical delivery component.

Purpose Codes for Payouts

When processing payouts or disbursements, purpose codes indicate the reason for the transfer. These codes are required by some providers and regulators for compliance.
PurposeCodeDescription
SalarySALARYEmployee salary or wage payment
VendorVENDORPayment to a vendor or supplier
RefundREFUNDCustomer refund for returned goods or services
LoanLOANLoan disbursement or repayment
InvestmentINVESTMENTInvestment-related transfer
CommissionCOMMISSIONCommission payment to agent or affiliate
PensionPENSIONPension or retirement fund payment
GovernmentGOVERNMENTGovernment benefit or tax payment
InsuranceINSURANCEInsurance premium or claim payment
OtherOTHERPurpose not covered by other categories
Set the purpose code in the purpose field of the payout request.
Using incorrect purpose codes may result in payout rejections or compliance issues. Some countries require specific purpose codes for cross-border transfers. Verify requirements with your provider for the target country.