OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
The Payer API returns structured invoice data for specified references.
GetPayeeInvoicesListDetails ↗
Function: GetPayeeInvoicesListDetails; Response parameters · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Invoice-reference arrays support batched retrieval; no complete invoice discovery contract is inferred.
GetPayeeInvoicesListDetails ↗
SOAP 1.2: Request; invoicesRefCodes · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Payment-order discovery is filtered by a starting update timestamp; invoice detail retrieval uses known references.
GetUpdatedPayments ↗
Request parameters > changedSince · Checked 2026-10-16
Access cost barrier -
-
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Configure security features ↗
Required user role Technical; API keys; Read-only key; Allowed IPs · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
Configure security features ↗
Required user role Technical; API keys; Read-only key; Allowed IPs · Checked 2026-10-16
Downstream permission -
-
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Configure security features ↗
Required user role Technical; API keys; Read-only key; Allowed IPs · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Create and update invoices, subject to bill-state and field-specific validation.
CreateOrUpdateInvoices ↗
Function: CreateOrUpdateInvoices; Request parameters · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
The customer can configure a payer API integration; chosen-third-party distribution rights remain unverified.
Configure security features ↗
API keys; Allowed IPs · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Payment-order references changed since a Unix timestamp are discoverable; invoice update coverage is not assumed.
GetUpdatedPayments ↗
Function: GetUpdatedPayments; Request parameters > changedSince · Checked 2026-10-16
Limit visibility 7.5/10
Numeric usage or polling guidance
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
The Payer guide states a maximum 250 records per API call and a ten-minute timeout; invoice mutation guidance is 200 bills.
Payer API ↗
Payer API introduction · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Updated payment-order identities are documented; complete deletion identities are not.
GetUpdatedPayments ↗
ChangedPaymentOrdersRefCode; changedSince · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Reissue overlapping changedSince payment-order queries. Retention, complete invoice enumeration and recovery of deleted payloads remain unestablished.
GetUpdatedPayments ↗
Request parameters > changedSince · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Returned invoice records can be retained externally.
GetPayeeInvoicesListDetails ↗
SOAP 1.2: Response; Invoices · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
A customer cancellation retrieval window and any exit charges have not been established.
Configure security features ↗
Required user role Technical; API keys; Read-only key; Allowed IPs · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Structured invoices and lines are returned, with complete discovery and file-byte coverage unresolved.
GetPayeeInvoicesListDetails ↗
Response parameters > Invoices · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
External SOAP client logic is supported; native workflow definition portability is unresolved.
Authentication: Using encryption key ↗
Authentication: Using encryption key; signature calculation · Checked 2026-10-16
Rights to custom logic -
-
Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Configure security features ↗
Required user role Technical; API keys; Read-only key; Allowed IPs · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A Technical user manages master, read-only and dynamic API keys and an allowed-IP list. SOAP authentication signs payer-specific request information with HMAC-SHA256; a payer key is distinct from a payee login or permission to act for unrelated customers.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
GetPayeeInvoicesListDetails accepts invoice reference codes and returns structured invoice data. GetUpdatedPayments discovers payment-order reference codes changed since a Unix timestamp; this payment-specific discovery function is not a complete invoice enumeration.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Tipalti customer API | API key | Customer | Not confirmed | Customer-supplied credentials | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
CreateOrUpdateInvoices creates or updates invoices and may create a payee when an unknown payee ID is submitted. Financial fields update only in eligible bill states, and a successful response may still leave disallowed fields unchanged; requests should contain no more than 200 bills.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
GetUpdatedPayments supports a changedSince watermark for payment-order identities. This supports overlap-based recovery for that resource, but a full invoice baseline, hard-delete capture and retained historical versions are not established by these pages.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Updated payment-order identities are documented; complete deletion identities are not. | GetUpdatedPayments ↗ChangedPaymentOrdersRefCode; changedSinceChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Reissue overlapping changedSince payment-order queries. Retention, complete invoice enumeration and recovery of deleted payloads remain unestablished. | GetUpdatedPayments ↗Request parameters > changedSinceChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Structured invoice responses can be copied outside Tipalti, including selected line and status data. Known reference-code retrieval does not prove that every invoice, file or historical payment state can be recovered after a missed discovery period.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External SOAP client code can apply payer-defined rules (with invoice validation and payment permissions enforced by Tipalti). Native approval artifacts, their ownership and independent execution remain unresolved.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. The Payer API returns structured invoice data for specified references. | GetPayeeInvoicesListDetails ↗Function: GetPayeeInvoicesListDetails; Response parametersChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Invoice-reference arrays support batched retrieval; no complete invoice discovery contract is inferred. | GetPayeeInvoicesListDetails ↗SOAP 1.2: Request; invoicesRefCodesChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Payment-order discovery is filtered by a starting update timestamp; invoice detail retrieval uses known references. | GetUpdatedPayments ↗Request parameters > changedSinceChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | Configure security features ↗Required user role Technical; API keys; Read-only key; Allowed IPsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Configure security features ↗Required user role Technical; API keys; Read-only key; Allowed IPsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Configure security features ↗Required user role Technical; API keys; Read-only key; Allowed IPsChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Create and update invoices, subject to bill-state and field-specific validation. | CreateOrUpdateInvoices ↗Function: CreateOrUpdateInvoices; Request parametersChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. The customer can configure a payer API integration; chosen-third-party distribution rights remain unverified. | Configure security features ↗API keys; Allowed IPsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Payment-order references changed since a Unix timestamp are discoverable; invoice update coverage is not assumed. | GetUpdatedPayments ↗Function: GetUpdatedPayments; Request parameters > changedSinceChecked 2026-10-16 |
| How are integration limits disclosed? | Numeric usage or polling guidanceTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. The Payer guide states a maximum 250 records per API call and a ten-minute timeout; invoice mutation guidance is 200 bills. | Payer API ↗Payer API introductionChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Returned invoice records can be retained externally. | GetPayeeInvoicesListDetails ↗SOAP 1.2: Response; InvoicesChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. A customer cancellation retrieval window and any exit charges have not been established. | Configure security features ↗Required user role Technical; API keys; Read-only key; Allowed IPsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. External SOAP client logic is supported; native workflow definition portability is unresolved. | Authentication: Using encryption key ↗Authentication: Using encryption key; signature calculationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Tipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Configure security features ↗Required user role Technical; API keys; Read-only key; Allowed IPsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedTipalti SOAP Payer API v15 selected invoice details/create-update and changed payment-order reference codes, using payer-controlled credentials; REST and partner distribution are not assumed equivalent. Structured invoices and lines are returned, with complete discovery and file-byte coverage unresolved. | GetPayeeInvoicesListDetails ↗Response parameters > InvoicesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.