RatesNegotiator API

Merchant statement analysis, built into your workflow.

Turn merchant processing statements into reconciled findings and finished reports. Built for payment teams, software platforms, and partners who need analysis inside their own tools.

Request API access · Read the documentation

One integration. Six report types.

Start with a single statement, compare proposed pricing, or review a portfolio. Choose the report that fits your workflow.

Statement analysis

statement_analysis · 1 statement · PDF report

Understand effective rates, pass-through costs, processor charges, and fee issues without adding a pricing proposal.

The default report type when none is specified.

Pricing proposal

pricing_proposal · 1 statement + proposed rates · PDF report

Compare current processing costs with the proposed rates you supply, with measured costs and modeled savings kept separate.

Includes a rep-only page that must be removed before sharing with the merchant.

Level 2 / Level 3 optimization

l23_optimization · 1 statement · PDF report

Evaluate modeled commercial-card interchange reductions from enhanced transaction data.

An estimate of opportunity, not a guarantee of qualification or savings.

Multi-month analysis

multi_month_analysis · 2–12 monthly statements · PDF report

Review monthly trends, weighted effective rates, fee changes, and gaps across statements from the same merchant.

All months must clear verification before a consolidated report is released.

Portfolio screening

portfolio_screen · 2–100 statements · PDF + editable spreadsheet

Compare unrelated merchants and rank estimated opportunities to help prioritize follow-up.

Includes an .xlsx workbook for your team's review.

Program performance

program_performance · 2–100 statements · PDF report

Compare surcharge-program locations under one owner and evaluate off-program locations against a program net rate.

A benchmark net rate is required when no location shows surcharge credits.

Modeled savings are estimates, not quotes or guarantees. Actual results depend on the merchant, processing activity, and agreed pricing.

From statement to report.

Submit a PDF, receive a job ID, and collect the result when processing finishes. Your application stays in control.

Submit the statement
Upload a PDF with the merchant name and report type. The API returns a job ID immediately so your application can continue.
POST /v1/reports
Track the analysis
Receive signed webhook events, or poll the job no more than once every 15 seconds. Typical processing is 1–5 minutes per statement; batches can take longer.
queued → processing
Collect the result
Read the summary and download the finished PDF with the same API key. Unresolved verification issues move to needs_review instead of releasing an unverified report.
GET /v1/reports/{job_id}

Your first report starts here.

Send a statement from your server using an issued API key. This example submits a statement analysis; it does not run a live request.

Example request

curl --request POST "https://api.ratesnegotiator.com/v1/reports" \
  --header "Authorization: Bearer $RN_API_KEY" \
  --form "statement=@statement.pdf" \
  --form "merchant_name=Your Merchant" \
  --form "report_type=statement_analysis"

Set RN_API_KEY in your server environment and replace the file path and merchant name. Never put an API key in browser code.

API reference · Interactive API explorer · Live test console

Designed for financial workflows.

Reconciliation before release

Verification checks the extracted figures before a report is released. Statements that cannot be reconciled are held for analyst review.

Authenticated delivery

Use server-side Bearer authentication over HTTPS. Report downloads require the submitting API key; webhook events carry HMAC-SHA256 signatures.

Clear outcomes

Handle complete, needs_review, and failed states explicitly. Measured statement costs remain distinct from modeled savings.

Before you integrate.

How do I get an API key?

Request access from the RatesNegotiator team with your use case and expected statement volume. Keys are issued per environment. Access and pricing are discussed directly; this website does not issue API keys.

What can I upload?

The API accepts PDF statements up to 25 MB per file. Single-statement reports take one file, multi-month analysis takes 2–12 monthly files for one merchant, and portfolio reports take 2–100 files. See the reference for required fields for each report type.

What happens if a statement needs review?

The job moves to needs_review and its report is held for analyst verification. A further webhook event is sent after release. Analyst review normally completes within one business day, but this is not a guaranteed turnaround.

Can I test the API before building an integration?

Yes. The documentation includes a live test console and an interactive API explorer. You need an issued API key to submit requests. Keep that key on your server when building your own integration.

How are documents retained and branded?

The API reference specifies a 12-month file-retention period. Reports use RatesNegotiator branding; co-branding is available by request. Review the API reference and data-handling policy before submitting merchant documents.

Data-handling policy

Bring statement analysis into your product.

Tell us about your use case, the reports you need, and your expected statement volume. We’ll discuss access and pricing with you.

API keys are issued by the RatesNegotiator team. Request access by email, or book a call to discuss your integration.