跳到主要内容

AI-处理信用卡 n8n

AI处理信用卡 是一个 PDF4me 节点操作 n8n 读取信用卡图像或 PDF 并以结构化方式返回卡片详细信息。 JSON 字段。使用此功能可从扫描件或照片中获取持卡人姓名、卡号、有效期和发卡行信息,而无需手动重新输入到表单中。

此节点的功能

PDF4meAI处理信用卡 从二进制数据中获取卡片文件 Base64 String或者 URL 并运用视觉 AI 返回 信用卡数据 包含各个卡片字段的对象。它接受 PDFPNGJPG, 和 JPEG因为它返回的是离散值而不是一大段文本,所以下一步工作流可以对单个字段进行操作,您可以有目的地选择哪些值值得保留。

相关博客文章
目前尚无关于此功能的博客文章——敬请期待。
在此期间,您可以浏览 PDF4me 博客,查看适用于各平台的教程和工作流程。
访问博客

验证您的身份 API 要求

每一个 PDF4me 节点 n8n 需要有效 用于连接的凭证创建或选择一个可以容纳您的 PDF4me API 关键在于确保工作流程能够安全地验证提取请求。

您不容错过的重要事实

提取与存储并不相同。
卡号和安全码属于受监管数据。应逐字段确定工作流程中需要保留的数据,并在任何数据到达存储或日志之前删除其余数据。
空字符串,而非缺失的键
模型无法读取的字段返回为 "" 与其检查键是否存在,不如检查值是否为空。
图像质量决定精度
眩光、角度和凸起的数字都会降低清晰度。 OCR 可靠性。使用 警告 数组和 备用方案 将可疑结果送交复核。
PDF4me AI-Process 信用卡节点(n8n 中),读取信用卡文件并返回结构化卡片字段

PDF4me AI-处理信用卡交易 n8n

卡片 OCR 与通用文档解析器相比

PDF4me 它同时包含卡牌专用操作和通用解析器。卡牌操作知道卡牌的外观;通用解析器则被告知要查找的内容。

方面AI处理信用卡AI 文档解析器
Field setA fixed card schema returned as creditCardDataWhatever fields you define for the document
Setup effortNone, the card fields are already knownYou describe the fields you want extracted
Best fitPayment cards specificallyAny document shape the card action does not cover
Extending itCustom Field Keys for extras beyond the card schemaFully defined by you from the start

哪些参数 AI-需要处理信用卡吗?

必需的: 操作、输入数据类型、与该输入类型匹配的字段以及信用卡名称。自定义字段键为可选。

范围必需的它的作用例子
ActionRequiredSelects the PDF4me node action to run. Choose AI-Process Credit Card.AI-Process Credit Card
Input Data TypeRequiredFormat of the source card input. Choose Binary Data (from a previous node), Base64 String, or URL.Binary Data
Input Binary FieldConditionalName of the binary property on the incoming n8n item that holds the card file. Required when Input Data Type is Binary Data. Defaults to data.data
Base64 Credit Card ContentConditionalBase64-encoded content of the card file. Required when Input Data Type is Base64 String.JVBERi0xLjQKJ...
Credit Card URLConditionalPublicly reachable HTTPS URL to the card file. Required when Input Data Type is URL.https://example.com/card.jpg
Credit Card NameRequiredFilename of the input file, used for format detection. Accepts .pdf, .png, .jpg, and .jpeg extensions, so give it the extension the file actually is.card.jpg
Custom Field KeysOptionalList of extra field keys to pull beyond the standard card schema. Leave empty unless the source carries values the built-in fields do not cover.["loyaltyId", "branchCode"]

输出字段

节点返回 JSON 而不是一个文件。卡片值存储在卡片内部。 creditCardData 目的。

场地类型它包含什么
creditCardDataObjectThe extracted card fields. See the field breakdown below.
jobIdStringIdentifier for the AI processing job, useful when reporting an extraction problem.
jobIdExtStringExternal job identifier for third-party integration, null when unused.
successBooleanTrue when extraction completed. Use it to branch error handling.
messageStringHuman-readable status message, carrying success confirmation or error detail.

信用卡数据内部字段

模型无法读取给定图像中的任何字段都将返回空字符串。

场地类型它包含什么
cardholderNameStringName as it appears on the card.
cardNumberStringThe primary account number. Regulated data, so handle deliberately.
expiryDateStringExpiry date, typically MM/YY.
validFromStringValid-from date where the card shows one.
validThruStringValid-through date, often the same as expiryDate.
cvvStringCard security code. The PCI DSS standard prohibits retaining this after authorisation.
cardTypeStringCard type where detected, such as credit or debit.
cardBrandStringCard brand where detected, such as Visa or MasterCard.
bankNameStringBank name printed on the card.
issuingBankStringIssuing bank where it can be determined separately from bankName.
accountNumberStringAssociated account number when the source is a statement rather than a card face.
warningsArrayMessages about data quality or extraction difficulty on this file.
fallbackUsedBooleanWhether an alternative extraction path was used. A useful low-confidence signal.

我该如何设置? AI-处理信用卡 n8n

  1. 添加 PDF4me 致你 n8n 工作流程并选择 AI处理信用卡 行动。
  2. 用于连接的凭证请选择您的 PDF4me 凭证或点击 创建新凭证 并粘贴你的 API 钥匙。
  3. 输入数据类型二进制数据 (默认), Base64 String, 或者 URL 并提供匹配的卡片文件字段。
  4. 信用卡名称 例如,使用正确的扩展名。 card.jpg 或者 statement.pdf
  5. (可选) 自定义字段键 用于超出标准卡片架构的值。
  6. 执行节点并读取 creditCardData 从响应中获取对象。
  7. 在存储任何内容之前,请先选择您实际需要的字段,删除其余字段。

典型配置

工作流程示例Common n8n workflow patterns using AI-Process Credit Card.
无需重新输入即可完成入职
  1. 顾客在注册时上传银行卡照片。
  2. AI-处理信用卡时,读取持卡人姓名和到期日。
  3. 仅使用非敏感字段预填表单以供确认。
低置信度路线读作人类
  1. 该节点处理上传的卡片图像。
  2. IF 节点检查 warnings 数组和 fallbackUsed 标志。
  3. 任何存疑的项目都会进入审核队列,而不是直接通过。
已存档的到期监控
  1. 卡片图像在采集时仅处理一次。
  2. 仅保留到期日期和持卡人姓名。
  3. 预先设定的工作流程会标记即将到期的信用卡,以便进行续费提醒。
将报表与账户匹配
  1. 信用卡账单 PDF 发送到共享邮箱。
  2. 该节点提取银行名称和账号。
  3. 该声明将与相应的账户记录一起存档。

实用技巧

Drop what you do not need immediately
Select the handful of fields the workflow actually uses in the very next node, so the full card payload never reaches storage, logs, or an error notification.
Give the filename its real extension
Credit Card Name drives format detection. Calling a JPEG card.pdf invites a failed or degraded read.
Check warnings before trusting a value
The warnings array and fallbackUsed are the cheapest confidence signal available. Branch on them rather than assuming a clean read.
Test for empty strings, not missing keys
Unread fields return as empty strings, so a key-existence check will pass on a field that holds nothing.
Improve the input before blaming the model
A flat, evenly lit, high resolution capture beats any amount of downstream correction, especially on embossed digits.
Use Custom Field Keys sparingly
The standard schema covers the card face. Reach for custom keys only when the source genuinely carries something extra.

速查表

场地价值
ActionAI-Process Credit Card
Input Data TypeBinary Data
Input Binary Fielddata
Credit Card Namecard.jpg
Custom Field Keys(empty)
Accepted formatsPDF, PNG, JPG, JPEG
ReturnsJSON with a creditCardData object
CredentialsPDF4me API credential

常见问题

What file formats can the node read a credit card from?+
PDF, PNG, JPG, and JPEG. Set Credit Card Name with the matching extension so the format is detected correctly, for example card.jpg for a photo or statement.pdf for a document.
Which fields come back, and why are some empty?+
The creditCardData object carries fields such as cardholderName, cardNumber, expiryDate, validThru, bankName, and cvv. Fields the model cannot read on a given image come back as empty strings rather than being omitted, so check for empty values instead of assuming every key is populated.
Should I store the extracted card number and CVV?+
Treat that decision carefully. A primary account number and security code are exactly the data the PCI Security Standards Council governs through PCI DSS, and the standard prohibits retaining the card verification code after authorisation. Extracting a field in a workflow does not mean you should persist it, so drop what you do not need before writing anything to storage or logs, and confirm your own obligations against the current standard.
What are the warnings and fallbackUsed fields for?+
warnings is an array of messages about data quality or extraction difficulty on that file, and fallbackUsed indicates whether an alternative extraction path was taken. Both are useful signals for routing low-confidence results to a human review branch in your n8n flow logic instead of straight through.
How accurate is OCR on a photographed card?+
Accuracy depends heavily on the source image. Embossed numbers at an angle, glare, and low resolution all reduce it. Check the success flag and the warnings array, and route anything doubtful to manual review rather than trusting a single pass on a photograph.

相关操作

在其他平台上执行相同任务

获取帮助