Verify OTP
Completes OTP verification for either payment or unbinding flows. Use transaction_id for payment OTP (after POST /charge returns requires_otp=true), or binding_id + unbind_context for unbind OTP (after POST /binding/{id}/unbind returns otp_handoff). Submitting both or neither returns 422 SP018.
Authorizations
Body
Submits an OTP to complete either a payment authorization or an unbind operation. Use transaction_id for payment-OTP flows, or binding_id + unbind_context for unbind-OTP flows. Exactly one of these flow definitions must be present.
Response
SP000 Successfully. For the payment flow, data matches DirectDebitTransactionData and status moves PENDING_OTP → PENDING (final SUCCESS arrives via webhook). For the unbinding flow, data matches DirectDebitBindingData; the binding stays ACTIVE until the direct-debit.unbinding.succeeded callback flips it to UNBOUND.
SingaPay Merchant API v2 custom response envelope (ApiResponderHelper::responseJson, ApiResponseTrait). Business outcome is determined by response_code (SP000–SP020), not by HTTP status alone. On success (SP000), data holds the operation payload. On errors, data often includes a message and may echo request fields.
