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
- 6bdbabb9164689e5af693124e02e564867a6a08a34ccff4490b0712e6fd052d3
- request
- 8907520e8dfc6f8a162341f45d17514a52769e404334930fc516cfb3dcc84246
- transaction
- 273b6ca5298e0090fde219e33cfbc2c108ed19189a865d57cf6ff3d8d3636a70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72419
the chainentry 72419
- sealed to the entry before
- a737e97af44c64988e9dbafa1c5e2d31d06393d8b6606e8272a587901f78ec54
- this leaf
- cd5f0fe822ceaa8dfd62e1a79eff4c0ea7c5eea42d621e317b84706561326ff2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h/jghzf0jUse1oC13rm8/kG7IqunSj20uI56URu+PuqIOwffs0SY0zb+bN/v9sbSSqRw0J9szWXHWXnhj2P6Ag==