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
- a5b37102d6c39081f6a1b5634babf7666ce41bffc5e71095154a5ae8aeff1853
- request
- ecad2e4ee5965639527b30e0bec1379d581087535b748e625bb11a3a60db57ef
- transaction
- d3d50829a5d6e161f064881db4847b0a2ca5cddf8f5a47328bc009abbe743e2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49462
the chainentry 49462
- sealed to the entry before
- 5f94186286d4f8d692c93f5308e83552154af75b2d3ba17b22b9499657e49825
- this leaf
- 4f56277c6ddaf819e1e65c076bef4cea9d781136d49ee955494445f712acdf9b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 64509lguDfDbkk8fFn+r1n5FTGejm77K8nu5w7fySGcuPm76dcqaijZrGkUZH5cskhsWduiJ3o00eqrt6wDzAw==