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
- c6cc8eae4265bba2ed7ef073cd3a215c555fd7d508937958d493018367fd91a7
- request
- 4ee9a3bffa66e7b86875870e2f9630172a0a8359f7ad4a62f77234a35ce33937
- transaction
- bd9e87beecac094ccee2eff61985fec27bded50210f4f4a56f766141ac09f166computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39439
the chainentry 39439
- sealed to the entry before
- def2f5e2d1f2f29da81c2d022d1949bbd2e6bb0d48ddc49e0980a22fa30a9926
- this leaf
- 9ac405502188a5114044d8a8b89fe38b1b47867f342370a52f667f03dc46634d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5yeV29myzMrsA/HBKtKT1YKqvjnBLVTtpZEQEYkosBhuIuzxxrhrPgMSMriDS5edYhkvXaaNIYdFiLgNLlDLBw==