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
- b81b3ca178f080ff264e4461b2ee89484727a573cd9523c90b5b5b9267da9169
- request
- 3fb440a3cfdd755642eb4772f91da70f0b4b18ae9acdc88ba523e18c8647e8c1
- transaction
- e1b7a903d2819eec8d519c63fba21ddff19db47991df58d70c99ff5eff6b5385computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5332
the chainentry 5332
- sealed to the entry before
- fa76410630ddb8f2dc01da25aaca72c82dc077a5de1571f033c6022e564c8019
- this leaf
- 0f9407a9de6c631ae0a83d5b0ebf82b09e853aa371a220a040e675d79f505e73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- haP2ba2auYp3eFNpqR7tCsS+1lSNeHHbFs4cVOmapsfJBA+mSUKczVa0l959JaYxB+FUu9bwp2Xwq5zmbpZHDw==