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
- 28e80cc149a3a0c76203090f36362fe7334d200a0b77ab24e826b2892f7547ac
- request
- 903d700d084b02e4067a46b7489ed1e03a773f33954ae31137eb4f42ff359471
- transaction
- c780a9ff6556faf78474d847142d89c2c3621915618d8acc51cd72ab7090596fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46617
the chainentry 46617
- sealed to the entry before
- bbce91562e71a3966cce6201fb19fe6ee00e6144178ec621f587d4cb76e2a0fa
- this leaf
- 5b7de2a20a5f04abf2091b671965ad66d6bd4f299d431096f36726664e3e61a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w/oW+3Pqdlly7mBQUj0P60udaCtrU5Ik31YGt3uIsmAqVN9FQNlECpEJa2XUK3h+vztjiqvY936x1X08AC2XDg==