Payments & Fulfillment

Your checkout selects products and collects customer confirmation. Pine Labs collects payment, fulfills the order, and refunds failed units.

Account activation

Contact Pine Labs to enable payments for your account. Card integrations must meet the applicable PCI-DSS requirements.

Resource	Contains
Order	Items, frozen sale prices, fulfillment results, and refunds.
Payment	One collection attempt: payer, payment method, fees, and return destination.

What Pine Labs handles

• Available payment methods and fee calculation.
• Payment collection and checkout or 3DS authentication when needed.
• Top-up and bill fulfillment for each unit in the order.
• Checking delayed payment outcomes with the payment provider.
• Supported CARD refunds for failed fulfillment or duplicate collections.
• Payment, fulfillment, and refund status updates.

What you need to build

• Checkout: let customers select products and payment options, then confirm the total.
• Backend integration: sign API requests, create orders and payments, and authorize customer access.
• Payment UI: collect new card details securely or let the customer select a saved method. Open the returned payment/authentication URL when present.
• Results: receive and verify webhooks, use API reads when needed, and display payment, fulfillment, and refund progress.

Integration flow

1. Get payment methods for your customer.
2. Calculate the order and confirm the total.
3. Create the order to freeze its item prices.
4. Create a payment with a new or saved card.
5. Receive webhooks for collection, fulfillment, and refunds.

Call all APIs from your backend with API Key + HMAC. Your backend authorizes customer access to orders and saved payment methods; identifiers alone grant no access.

Reading this reference

• Amounts use MYR. Item amount accepts a string or number, as in Make Payment. Other monetary request fields use two-place decimal strings.
• Request tables mark Required fields. Response and webhook fields are returned unless their description states a condition; nullable values are shown in the type.
• created_at is resource creation time; updated_at is its latest public change. All timestamps are UTC in yyyy-MM-ddTHH:mm:ss.fffZ form. Examples use illustrative IDs.

See Calculate Order for fees, Refunds for repayment rules, and Complete Flow for retries.