Which territory-specific acquirer or sponsor-bank entity and card-network route apply to each merchant and territory?

The facilitator is not the universal direct acquirer.

Which underwriting, reserve, dispute, funding and payout controls belong to each party?

Facilitator and acquirer responsibilities must be separated.

Which facilitator credentials or merchant-specific identifiers are used?

A dedicated MID is not promised for this product.

Which facilitator entity, acquirer or sponsor bank and card-network relationship apply by territory?

The regulated and network roles must match the current agreement.

Which master credentials or merchant-specific identifiers are used, and who owns them?

A dedicated MID is not promised.

Which PCI, privacy, security, incident, audit and termination terms apply across facilitator and acquirer?

Data and operational duties cross contractual parties.

Which contacts, hours and response targets cover submerchant onboarding, gateway, risk, disputes, funding, reserves and payouts?

Facilitator support spans several operational stages.

How are acquiring, card-network and settlement-funding incidents escalated to the acquirer or sponsor bank identified in the applicable agreement or exhibit?

The partner acquirer owns those external functions.

Which PCI, token, credential, encryption, access, incident and audit controls apply?

Gateway security scope must be explicit.

Which underwriting, authorization, dispute, reserve, funds and settlement controls belong to the merchant's Merchant Service Provider, processor and acquiring bank?

Those controls are outside the gateway-only product.

How are processor outages, message retries, duplicate prevention, token portability and termination handled?

Gateway continuity depends on the configured processor route.

Which entity contracts for gateway access, and which processor or acquirer agreement controls the merchant account?

Technology and financial contracts must be separated.

Which regulatory and card-network responsibilities belong to the merchant's Merchant Service Provider, processor and acquiring bank?

The gateway provider is not the financial acquirer on this route.

Which PCI, privacy, residency, token, incident, audit and deletion terms apply?

Gateway and token data duties require explicit allocation.

Which contacts, hours and response targets cover API access, tokenization, transaction messages, processor connectivity and incidents?

Gateway support must distinguish technical and financial issues.

How are authorization, merchant-account, funds and settlement incidents escalated to the merchant's Merchant Service Provider, processor and acquiring bank?

Those issues belong to the external processor or acquirer.

Which fee, split, refund, dispute, balance and payout controls may the platform operate?

Multi-party funds controls require explicit permissions.

Which KYC or KYB, application, agreement, reserve and activation requirements apply to each merchant?

Platform approval does not activate every merchant.

How are buyer support, fulfilment, refunds and Merchant of Record duties divided among the platform and each merchant?

The software-platform buyer is not automatically the seller.

Which entity contracts with the platform and each merchant, and which acquirer applies by territory?

Contracting and acquiring roles can vary by merchant and route.

Which seller, fulfilment, refund, complaint, tax and consumer-law duties remain with each merchant?

The merchant remains Merchant of Record for its own sales.

Which platform, merchant and buyer-data controller, security, retention, incident and audit terms apply?

Embedded workflows cross several data roles.

Which contacts, hours and response targets cover platform integration, merchant applications, processing, splits, balances and payouts?

Embedded support spans platform and merchant workflows.

How are merchant, buyer, acquiring and payout incidents divided among the platform, BlueSnap and the acquirer or sponsor bank for the applicable merchant and transaction?

Each party owns a different operational layer.

Who owns receipts, taxes, refunds, chargebacks, complaints and consumer-law duties for each covered route?

Customer-facing duties are contract-specific.

Which deductions, reserves, payout controls and post-termination rules apply to seller proceeds?

Seller-funds treatment depends on the covered agreement.

How do the agreement and local law allocate tax, receipts, refunds, chargebacks, consumer support and supplier duties?

Merchant of Record status is not a generic transfer of every seller duty.

Which entity is Merchant of Record for each covered transaction, market and payment route?

The role is entity-, agreement- and transaction-specific.

Which privacy, payment-data, security, retention, incident and audit terms apply to covered transactions?

The customer-facing entity must match the data allocation.

Which contacts, hours and response targets cover covered customer payments, receipts, refunds, chargebacks and seller payouts?

Support must follow the Merchant of Record named for that transaction.

How are support issues handled when the transaction is outside the covered Merchant of Record route?

The role does not apply universally.