why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- d41cd63dd643cfd3940a51ef6eb973d8bc1676dc0488fd1b2f7caa4fb2e5148a
- request
- 32c2d85ac3af61c83a627cd55d82e767688090acfaeb93cbfbe2384d4eb2cb5e
- transaction
- a9333669bb4753b0ab21afff827a1f863914bb1901666977f8aa4aac64f8a16bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39001
the chainentry 39001
- sealed to the entry before
- 9cfced71990466f1ba8298bf1fa486d4a8608388e33dcac85b79ac70f1e67508
- this leaf
- 10dd73c6125de828b230c736caf0b9bafaa6d366e330c5fd8681548b04c5e883
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w7z5CfjznOydHlZ3yEoV0YcdefHl3RJ2ti3D1Hw47sjqEEGrsaaSSsbRtfykMZ1lcLVNyGCLlsV93QhQM96TDA==