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
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
The gateway API returns structured transaction records.
Transaction Search ↗
Transaction Search; Examples · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Search exposes iterable transaction results; permissions and chosen filters constrain the collection.
Transaction Search ↗
Search; gateway.transaction.search; response.each · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Customer, merchant account, timestamps and transaction-state search fields are documented.
Transaction Search ↗
Search Fields; Examples; Merchant account · Checked 2026-10-16
Access cost barrier -
-
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Important gateway credentials ↗
API credentials; API keys; Merchant account ID versus merchant ID · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
Important gateway credentials ↗
API credentials; API keys; Merchant account ID versus merchant ID · Checked 2026-10-16
Downstream permission -
-
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Important gateway credentials ↗
API credentials; API keys; Merchant account ID versus merchant ID · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Named full/partial refunds are documented; generic record create/update is not established by that operation.
Transaction Refund ↗
Transaction Refund; amount · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Customer integrations use a dedicated API user; third-party distribution rights remain a separate unresolved question.
Go Live ↗
Create an API user · 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
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Signed notifications can trigger re-reads; event coverage is resource-specific and ordering is not guaranteed.
Parse webhook notifications ↗
Parse; WebhookNotification; Retries · Checked 2026-10-16
Limit visibility -
-
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Numeric request quotas and recovery instructions have not been established.
Important gateway credentials ↗
API credentials; API keys; Merchant account ID versus merchant ID · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Repeat selected transaction searches for customer reconciliation; the reviewed route does not establish a complete updated-time or hard-delete identity feed.
Transaction Search ↗
Search; gateway.transaction.search; response.each · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Production webhook redelivery retries hourly up to 24 hours; this is bounded retry, not a retained event log. Transaction search separately supports selected current-state rebuilding.
Parse webhook notifications ↗
Retries · 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
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Structured returned transactions can be retained by the caller.
Transaction Search ↗
Search; Examples · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
A customer cancellation retrieval window and any exit charges have not been established.
Important gateway credentials ↗
API credentials; API keys; Merchant account ID versus merchant ID · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Portable selected transaction records are supported; vault secrets, full history and configuration remain unverified.
Transaction Search ↗
Search; Examples · 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
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
The server SDK supports external integration logic, not native workflow export.
Transaction Search ↗
Search; Examples · Checked 2026-10-16
Rights to custom logic -
-
Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Important gateway credentials ↗
API credentials; API keys; Merchant account ID versus merchant ID · 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
Each gateway user has a public/private key pair; the integration also selects environment and gateway merchant ID. Sandbox and production credentials are separate, and Braintree recommends a dedicated production API user rather than tying an integration to an employee account.
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
Transaction search returns iterable results with customer, merchant-account, created/settled date and status predicates. Merchant ID identifies the gateway, while merchant account ID identifies a business/currency account inside that gateway; keep both scopes explicit.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Braintree customer API | HTTP Basic | 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
The transaction refund operation applies to a transaction eligible for refund and may take an amount for a partial refund. It is a financial action, not a correction of reporting rows; a refund request requires exact target and amount approval.
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
Signed Braintree notifications include a timestamp and resource snapshot, can arrive out of order, and retry hourly for up to 24 hours in production. Search can rebuild selected current transactions, but webhook coverage is event-specific and does not establish all transaction updates or hard deletes.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Repeat selected transaction searches for customer reconciliation; the reviewed route does not establish a complete updated-time or hard-delete identity feed. | Transaction Search ↗Search; gateway.transaction.search; response.eachChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Production webhook redelivery retries hourly up to 24 hours; this is bounded retry, not a retained event log. Transaction search separately supports selected current-state rebuilding. | Parse webhook notifications ↗RetriesChecked 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
Search returns structured transaction records that can be retained outside the gateway. A transaction record is not an export of payment-method secrets, all dispute material, complete historical versions or a restorable Braintree configuration.
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
The official server SDK supports customer-authored transaction queries and actions (with credentials and business validation enforced by Braintree). Native workflow ownership and independent execution remain unestablished.
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 scopeBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. The gateway API returns structured transaction records. | Transaction Search ↗Transaction Search; ExamplesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Search exposes iterable transaction results; permissions and chosen filters constrain the collection. | Transaction Search ↗Search; gateway.transaction.search; response.eachChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Customer, merchant account, timestamps and transaction-state search fields are documented. | Transaction Search ↗Search Fields; Examples; Merchant accountChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | Important gateway credentials ↗API credentials; API keys; Merchant account ID versus merchant IDChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Important gateway credentials ↗API credentials; API keys; Merchant account ID versus merchant IDChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Important gateway credentials ↗API credentials; API keys; Merchant account ID versus merchant IDChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Named full/partial refunds are documented; generic record create/update is not established by that operation. | Transaction Refund ↗Transaction Refund; amountChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Customer integrations use a dedicated API user; third-party distribution rights remain a separate unresolved question. | Go Live ↗Create an API userChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Signed notifications can trigger re-reads; event coverage is resource-specific and ordering is not guaranteed. | Parse webhook notifications ↗Parse; WebhookNotification; RetriesChecked 2026-10-16 |
| How are integration limits disclosed? | -Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Numeric request quotas and recovery instructions have not been established. | Important gateway credentials ↗API credentials; API keys; Merchant account ID versus merchant IDChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Structured returned transactions can be retained by the caller. | Transaction Search ↗Search; ExamplesChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. A customer cancellation retrieval window and any exit charges have not been established. | Important gateway credentials ↗API credentials; API keys; Merchant account ID versus merchant IDChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. The server SDK supports external integration logic, not native workflow export. | Transaction Search ↗Search; ExamplesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Braintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Important gateway credentials ↗API credentials; API keys; Merchant account ID versus merchant IDChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedBraintree gateway server API transaction search and captured-transaction refund, plus selected Braintree webhooks; PayPal REST and PayPal Orchestration are separate product routes. Portable selected transaction records are supported; vault secrets, full history and configuration remain unverified. | Transaction Search ↗Search; ExamplesChecked 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.
- Numeric request quotas and recovery instructions have not been established.
- 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.