Purpose codes reference

Some countries' bank compliance processes require you to specify each payment's purpose:

CodeDescription
EPFAMTFamily maintenance.
ISMDCSPayment for medical care services.
ISSTDYPayment of study/tuition costs.
ISCHARPayment for charity reasons.
EPPROPPayment of property purchase.
EPSHARPayment of shares.
EPIVSTPayment of an investment.
ISUBILPayment to common utility provider.
ISTAXSPayment of taxes.
EPTOURTourism.
EPTKAGPayment of travel tickets or tourism agencies.
ISSAVGPayment to savings/retirement account.
ISPENSPension payment.
ISPAYRPayment of payroll.
ISGDDSPurchase sale of physical goods.
ISDGGDPurchase sale of digital goods.
ISSUPPSupplier payment.
EPREMTRemittances.
ISSCVEPurchase sale of services.
EPCAPIPayment of capital contribution.
EPRENTPayment of movable property rental.
ISLOGSPayment for logistic and/or delivery services.
EPIVFEPayment of an investment (interest) owed to a financial entity.
EPDISPDisponibilidades.
EPINSUPayment of Insurances.
ISREWDRewards.
ISENTREntertainment.
ISPUBSPublic/government services.
ISAFFIAffiliation programs.
EPBTOBBusiness to Business.
ISRSVCPurchase sale of recurring services.
EPLOANForeign or inter-company loans.

In Payouts API version 2.0, the Flow Type is not sent as a standalone field. Instead, it is inferred by our system based on the purpose code you provide. It is critical to select the correct purpose code to ensure your payout includes all necessary beneficiary and remitter information required by local regulators.

The following logic is applied during inference:

  • P2P: Automatically inferred if the purpose is EPFAMT, EPDISP or EPREMT.
  • B2B: Automatically inferred if the purpose is EPBTOB.
  • B2C: Default flow. All other purpose codes not listed above are processed as B2C.

To improve developer experience and reduce integration errors, Payouts API v3 introduces a dedicated flow_type field. This decoupling allows for more granular control and clearer validation messages.