Move a key to another engine
The migration-wave operation. Records the previous owner and the reason. Once the move commits, the next lookup answers the new owner. On the SPB rail an operation already in flight resolves to the engine that originated it. On the Pix rail a message decided after the move reaches the new owner, and one an earlier attempt already sent to the previous owner is retained for a person, never sent to the new one. A Pix Automático debit, its reversal and a schedule’s cancellation status stay with the engine that holds the payment’s block or schedule, whoever owns the account after the move.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Idempotency key; a retry with the same key and body replays the first answer.
Parâmetros de caminho
Surrogate identifier of the assignment. Find one by keyKind + keyValue on the collection.
Corpo
Resposta
OK
^[a-z0-9-]{1,32}$ACCOUNT, DOCUMENT, PIX_KEY_EMAIL, PIX_KEY_PHONE, PIX_KEY_RANDOM, PAYMENT_ID, PIX_RECURRENCE_ID, PIX_RECURRENCE_ID_CHARGER Normalized form. This is what the rails resolve against. ACCOUNT is :, and : for a payment account.
256Exactly what the operator typed.
256Present after a move.
128
