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
- 1cf36091c6d254dd572dfeebfe0b99e0c018f064c674a3a882284c2df89170be
- request
- f3cc7a69f19ba51eb33c4b8c8f6d010a49723d54eec65624456a0ed00098338d
- transaction
- 070787c2ac1c8782e5664d3bfa46e93cf13cc78f22412032da34c71d913c31becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48735
the chainentry 48735
- sealed to the entry before
- dc41f88f60bae59e0ce2fd2bc6655626dc2c7c1f7768176fdff970a4d04a8469
- this leaf
- 76a1141f6ba37b1314acd18949dd466d381505afcb9e84aed8926c4da5ac0669
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BTk5w3krXx2so2RVzw8AZzRoS1eKSqxM4UCiIcXbbtf1PkIYPkwv9SxQU5/uIek7lybLAusSNx/FjiFYSNAQBg==