After a checkout transaction is initiated, iLeben creates aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/scooller/Leben-site/llms.txt
Use this file to discover all available pages before exploring further.
Payment record that tracks the transaction lifecycle from pending through to completed, failed, or one of the other statuses defined in the PaymentStatus enum. The endpoints below let authenticated users retrieve their payment history and upload transfer proof for manual payments. A separate public-status endpoint allows result pages to display payment state without requiring the buyer to be logged in.
Authentication
Most endpoints require bothauth:sanctum and token.origin middleware:
- Header:
Authorization: Bearer <token> - Header:
Origin: <your-authorized-origin>(orReferer/X-Authorized-Url)
GET /api/v1/payments/public-status/{id}) is unauthenticated and uses a token query parameter instead.
GET /api/v1/payments
List all payments for the authenticated user. Returns a paginated collection of payment records belonging to the current session’s user.GET /api/v1/payments/
Retrieve the full payment record for a single transaction.Path parameters
The internal iLeben payment ID returned at checkout.
POST /api/v1/payments//manual-proof
Upload a proof-of-payment file for a manual bank transfer. After the file is uploaded, an admin reviews and approves or rejects the payment from the Filament admin panel.Path parameters
The internal iLeben payment ID for the manual payment being confirmed.
Request
Content-Type:multipart/form-data
Proof-of-payment image or document. Accepted formats:
jpg, jpeg, png, pdf, heic, heif. Maximum size: 5 MB.Optional notes from the buyer to accompany the proof, e.g. transfer date or bank reference number. Maximum 1000 characters.
After upload
Admin reviews in Filament
The uploaded file appears in the Filament admin panel under the payment record. An admin inspects the proof against bank records.
GET /api/v1/payments/public-status/
Retrieve the current status of a payment without authentication. This endpoint is designed for the post-checkout result page shown to buyers after a redirect-based payment flow.Authentication
None. This endpoint is public. Access is controlled by thetoken query parameter, which must match the public_status_token (also returned at checkout as payment_status_token for Transbank) associated with the payment.
Path parameters
The internal iLeben payment ID.
Query parameters
The
public_status_token (UUID) returned in the checkout response. This token acts as a bearer credential for this single public endpoint.Responses
| Code | Meaning |
|---|---|
200 | Payment found and status returned successfully. |
422 | The token query parameter is missing from the request. |
404 | The token is invalid or does not match the payment ID. |
Payment status values
ThePaymentStatus enum defines all possible states a payment record can hold:
| Value | Description |
|---|---|
pending | Transaction initiated; awaiting gateway confirmation. |
processing | Gateway is processing the payment asynchronously. |
authorized | Funds authorized but not yet captured (marks the plant as unavailable). |
completed | Payment confirmed and accepted. |
failed | Payment rejected or errored. |
cancelled | Payment was cancelled before completion. |
refunded | Payment was fully refunded. |
partially_refunded | Payment was partially refunded. |
expired | Payment window lapsed before the transaction was completed. |
pending_approval | Manual payment awaiting admin review after proof upload. |
Web routes for payment results
After gateway redirects, buyers land on result pages served by web routes defined outside/api/v1:
Payment model and display the appropriate outcome screen to the buyer.