Atrato Pago's merchant integration profile explains partner keys, token retrieval, payment initiation and webhook notifications in Mexico. Sandbox and production settings, WooCommerce credentials and order-status mapping connect checkout integration with the merchant's workflow.
TL;DR:
- Atrato's merchant integration documents authentication, orders and notifications.
- Partner credentials and a branch key are used to obtain an integration token.
- Sandbox, production and payment-state handling require separate configuration.
Summary
Merchant Integration Scope
Atrato Pago's public integration documentation describes how a merchant or partner in Mexico connects its checkout and back office to the financing service. The documentation includes custom-code and commerce-platform paths, order operations and notifications. It is a proprietary integration profile. The documentation site's v1.0 label is distinct from the version segments embedded in individual API endpoints.
Authentication And Environments
The token endpoint shown for e-commerce integration uses a partner key identifying the branch and the partner-dashboard username and password. Its published sandbox address contains an api/v4 path. Partners must use credentials and configuration for the intended environment; a sandbox login or order does not establish a live transaction. Authentication details should be handled as integration credentials rather than customer checkout data.
Commerce Workflow
The documentation navigation and WooCommerce guide distinguish obtaining access, generating and consulting an order, registering delivery, requesting cancellation and checking disbursements. WooCommerce setup requires the store's REST API credentials and corresponding Atrato partner configuration. These steps connect order administration with the financing workflow, but a plugin's use of another platform's API does not establish Atrato conformance to an unrelated protocol or certification.
Notifications And State
Atrato's webhook guide describes POST notifications when payment state changes, including pending reconciliation, success and cancellation. It recommends validating the configured authentication, responding successfully after processing and preventing duplicate handling using payment identity and status. This particular payment-notification guide concerns its documented payment event; implementers must match the webhook family and payload to their integration rather than treating all order and cash-in events as identical.
Keywords
- Partner Authentication
- Access Token
- Branch Key
- Order Creation
- Webhooks
- Sandbox
- WooCommerce
- Payment Status
- Reconciliation
- Mexico