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
- abdc2551b7eec300ad2259f91d0fb0339f99f077c352f77b30ccc5d66c672e46
- request
- c3de9b273dbf0148cb12a6e8a91d5d74e30551f7263d0433bbcad06da1ff14cd
- transaction
- 75db637b28f5a8272d88c9d79346bd549ae537eed3142e7a27a7d42ac8b2fc1ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29606
the chainentry 29606
- sealed to the entry before
- 660d4cf8047954c685c0e3a5019fc214a85817d0061d5ef015eef2ac58ec7bad
- this leaf
- 31432a45309711b8ade80737c426766c6545f4b0c321bea5ea4bcdf75d13c1c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 533ldW6dmTkMfBolWNc/Xi4Y5hPOtsdFCgAe+/F+PA1OQZ5r65Pp8cinY6hfJnYh4dG+tx13JK5xL3j4ZB26AQ==