Processor versus merchant
Model input
Statement: PAYPROC*CEDARCOFFEE. Receipt identifies Cedar Coffee as seller.
Normalize transaction merchant names using identifying evidence.
Step 01
Upload sample data, define your output schema, and provide feedback on the hardest cases.
The underlying seller’s normalized name, excluding payment processors.
Whether the compared records identify the same business.
Evidence used to normalize or compare the merchants.
Normalize transaction merchant names using identifying evidence.
Statement: PAYPROC*CEDARCOFFEE. Receipt identifies Cedar Coffee as seller.
Sutro can now generalize the rules based on your feedback.
Step 02
Compare quality and cost on your examples, then choose a model or use Sutro’s default.
Compare models on expert agreement and cost. The interactive chart uses illustrative measurements.
Illustrative sweep · select Value or Best to use that model in your function.
Step 03
Call Sutro Functions like any other software. Swap the model as soon as something more performant is released.
import sutro as so
input_data = {
"text": "Statement: PAYPROC*CEDARCOFFEE. Receipt identifies Cedar Coffee as seller."
}
result = so.run_function(
"merchant-normalization-matching",
input_data,
)curl --fail-with-body -X POST "${SUTRO_API_URL%/}/v1/functions/merchant-normalization-matching/run" \
-H "Authorization: Key $SUTRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": {
"text": "Statement: PAYPROC*CEDARCOFFEE. Receipt identifies Cedar Coffee as seller."
}
}'import sutro as so
job_id = so.batch_run_function(
name="merchant-normalization-matching",
data="merchant_normalization_matching.csv",
)
results = so.await_job_completion(job_id)curl --fail-with-body -X POST "${SUTRO_API_URL%/}/v1/batch-inference" \
-H "Authorization: Key $SUTRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "merchant-normalization-matching",
"inputs": [
{
"text": "Statement: PAYPROC*CEDARCOFFEE. Receipt identifies Cedar Coffee as seller."
}
]
}'