This guide introduces the complete payment flow in Bamboo, from purchase creation and authorization, to capture and post-authorization operations like cancellation or refund.

Before diving into individual operations, it’s important to understand the two types of flows supported by the platform.

---

Payment Flows

Depending on the payment method, Bamboo supports two types of transaction flows.

---

API Flow

Used for direct card transactions or tokenized flows. The full payment is processed via backend, and the final status is returned in the same response.

1. Buy — The customer initiates the transaction on the merchant site.
2. HTTP POST — The merchant sends a POST /api/Purchase request to Bamboo.
3. Authorize — Bamboo forwards the request to the acquirer for processing.
4. Authorization OK — The acquirer returns the authorization result.
5. Response — Bamboo sends the result (COMPLETED, REJECTED, etc.) to the merchant.
6. OK — The merchant displays the result to the customer.

---

Redirect Flow

Used for payment methods that require the payer to complete the transaction in an external interface (including QR codes, wallets).

1. Buy — The customer initiates the transaction.
2. HTTP POST — The merchant sends the purchase request to Bamboo.
3. Pending for redirection — Bamboo responds with an Action.URL.
4. Redirection URL — The merchant redirects the customer.
5. Redirect — The customer is taken to the payment interface.
6. Payment Page — The page shows transaction details and form.
7. Submit Payment — The customer enters the required data and confirms the payment.
8. Authorization OK — The acquirer authorizes the transaction.
9. Authorization Response — Bamboo sends the result to the merchant.
10. OK — The merchant displays the result to the customer.

---

Payment Operations

The following operations define the full lifecycle of a purchase in Bamboo, from validation to capture.