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
- 6cc1fbf115a66cff1aa04790de2b0a4da2bb2fa28f51f65faeb374900e32db72
- request
- 3117be439786261f28d6fafdb40a5d4fb05aab68d87f7f0b73dec676f6290cdf
- transaction
- e5652d8944791a6cf185467238a4831d0260cfb0d1b99de419e01b236b57dec1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25191
the chainentry 25191
- sealed to the entry before
- bc51a8c60a5b1cb7feefaa85c77e753511aabefbf33c2e72899a5a4b0b500493
- this leaf
- bb688e4ebff376fb08fab65f2ffdd12c0a7428586502b253ddf0c1e5d761f3d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 90Lkcb+CJue0HOhja41MjIRroEs1glW5TNgKgarxlIAqNoYAwhmEcQBJBCh8kiT5HkP+9ngIRALZoXewUlLcCA==