Skip to main content
Verifies a Masivo TOTP code with the merchant’s server API key. Spark calls Masivo’s authorize endpoint, keeps the bearer token on the server, then calls Masivo verify and returns Masivo’s data unchanged (customer, wallet, metadata).
Requires a Fire spark access token from token exchange. There is no channel or integration toggle for this route. It works when this environment has an active Masivo connection, and returns 409 MASIVO_NOT_CONNECTED otherwise.
The Masivo customer id is data.customer.id. Pass order_id when a kiosk is about to hand this open order to that customer. Spark checks that the order is OPEN and owned by the caller, that data.customer.id is a customer of this merchant, and adds customer_switch_proof. The proof is a 60-second token signed by Fire spark. Send it to token exchange as subject_token. Without order_id, the response stays the Masivo payload and includes no proof. With the SDK:
auth.switchCustomer also accepts verified.customer_switch_proof on its own.

Query parameters

Request

Response

200 with Masivo’s data object.
An invalid code is 422. Spark keeps Masivo’s error and details. Other Masivo failures use Spark’s upstream mapping (502 for rate limits and server errors) and still keep Masivo’s error and details when Masivo sent them. No active Masivo connection for this merchant and environment:
The error text follows Accept-Language (es, en, or pt). The code stays MASIVO_NOT_CONNECTED.