Campaign dashboards that treat 00 as “updated” lie. PoR OK is the card saying the security wrapper and counter were acceptable and the application saw the message. The application-level status word still lives in the additional response data. An UPDATE BINARY that hits a file the card will not write returns 00 at the PoR and a failing SW in the payload. Decode the response packet, then read that SW — do not stop at the status byte.
Usual cause
The card accepted the command packet: security checks passed, the counter was accepted and the application processed the message. Any additional response data carries the application-level result.
What to do
Note that "PoR OK" is transport-level success only. An RFM UPDATE that returned 00 can still carry an APDU status word reporting that the update itself failed — check the additional response data before recording the card as done.
TS 102 225 §5.2