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
- 3d0f7e269f846bd0736221dc7d89bb31fa838f4e6f984e44ef6ce38b36c191ef
- request
- 65deda733c1f45be416a57f79211ec3797ef8a779c60e8d0b290400eac66e199
- transaction
- 5500390b7b38750f0da40639f9503d6e798ecb0061283d896dbe1dd972c2d374computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60574
the chainentry 60574
- sealed to the entry before
- 2f76d1962d164754b55b44583da119f77f76effd42c9bd606c64c67a65aab911
- this leaf
- ce5cb3fe0f0bd47338a9f06f2fbae33204e5b627e7ae0593ba722f5c9364a06b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DayaQ4K1BVPAo5IYgBJBvWNrKFRxysnv65DJnUEJI9fkROLsX9TlW9tombPOmvXrM8X6m7xXuAbJLCZrUyEpCg==