ReceiptType is used to work with server-sided receipt processing.

ReceiptType works with MarketplaceService:BindReceiptHandler() to indicate the different type of receipts a developer can bind to for processing. When you call BindReceiptHandler, you pass a ReceiptType to specify which kind of receipt your handler should process.

For Robux transfers initiated with PromptRobuxTransferAsync, two receipts are generated: one for the sender (RobuxTransferSender) and one for the receiver (RobuxTransferReceiver). You should register handlers for both types to fully process a transfer.

Transfer receipts may not be delivered while the player is still in the originating server. RobuxTransferReceiver is always deferred to the receiver's next session join. RobuxTransferSender is immediate if no receiver approval was required, otherwise deferred to the sender's next session join. See BindReceiptHandler for details.