Short answer: Use POST /v1/sms/otp to start phone verification and POST /v1/sms/resend/{id} when delivery needs another attempt. Keep the code, expiration policy, attempt counter, and receipt evidence in the marketplace application. The SMS provider should be the delivery boundary, not the compliance record.
That is the least complex design for a marketplace that sends an order receipt after payment settles. The application owns the verification decision. The provider receives a request to send a one-time message. A durable internal event connects a settled payment to a verified phone number and then to receipt delivery.
What exactly should the SMS provider own?
For an OTP or 2FA login flow, the provider can accept a phone number, generate and send a code, and expose the delivery operation. The application should keep a protected representation of the code, an expiration timestamp, the number of failed attempts, the login or account binding, and the provider's delivery identifier.…