SecureDto

The SecureDto (Secure Data Transfer Object) defines the security measures required by an operator for different transaction types within the NoWallet API.
This DTO is especially useful for understanding whether a transaction method (like MERCHANT, CASHIN, or CASHOUT) needs an extra layer of validation, such as an SMS or a QR code, before processing.

JSON Example

The example JSON illustrates that no security validation is currently required across all transaction methods (MERCHANT, CASHIN, and CASHOUT) — neither through SMS nor QR code. This implies a default configuration with no added friction for the end user.

{
  "sms": {
    "MERCHANT": false,
    "CASHIN": false,
    "CASHOUT": false
  },
  "qrcode": {
    "MERCHANT": false,
    "CASHIN": false,
    "CASHOUT": false
  }
}

Properties

• sms: This object specifies if an SMS verification step is required for each transaction method. For example, if CASHOUT is set to true, the user would receive an SMS code they must input before completing a cash-out transaction.
• qrcode: This field references the OperatorNeedQrDto, which indicates whether a QR code is necessary for each transaction type. It allows for flexible configuration per method and is essential for operators requiring visual code scans as part of their security process.

Name	Type	Required	Restrictions	Description
sms	object	true	none	operator need sms
qrcode	OperatorNeedQrDto	true	none	operator need qrcode

This DTO enhances transparency and configurability for integrators, letting them adjust their UI/UX and backend flows according to the operator’s security requirements.

This page was helpful?