How it works

sequenceDiagram
    autonumber
    participant C as Buyer
    participant T as Magento store
    participant P as Platform
    participant A as Phone app
    C->>T: Confirms the order (Yape method)
    T->>P: Publishes the open order (unique amount)
    C->>C: Pays the exact amount in Yape
    A->>A: Detects the Yape notification
    A->>P: Sends the event (signed, idempotent)
    P->>P: Reconciles event ↔ order
    T->>P: Polls for matches (outbound)
    T->>T: Applies per its policy (annotate / approve)

The steps

1. The buyer picks “Pay with Yape” at checkout. The order gets a unique amount (adjusted by 0 to 99 cents) to tell it apart from others.
2. The connector publishes the open order to the platform, without the buyer’s personal data.
3. The buyer pays in Yape to your number.
4. The app detects the notification and stores it locally before sending. It only marks it “sent” once the platform confirms.
5. The platform reconciles: it looks for an open order with the same shop, environment and amount within the deadline (15 min by default).
6. Magento collects the match and acts on the policy you chose: nothing (shadow), annotate, approve with one click, or approve automatically.

Principles worth remembering

• The phone detects and transports; the platform reconciles; Magento decides.
• Nothing is lost or duplicated: every event has an event_id, and resending is harmless.
• Everything is separated per customer and environment (test / live). A test event never touches production data.
• Heartbeat: phone and connector report they are alive; if they stop, an alert fires.