Payouts
Use the payouts endpoint to review the amounts that are expected to be routed to your pharmacy for paid physical-prescription orders, and the amounts that were actually routed after completed orders. The endpoint only returns payouts where the requested pharmacy is the payment receiver. With a single-pharmacy API key, this is your current pharmacy. With a group-wide API key, this is the pharmacy selected bypharmacy_uid.
List Payouts
orders_read permission.
Required for group-wide API keys. Single-pharmacy API keys are automatically scoped to their pharmacy.
Filter by payout status. Accepted values are
projected and routed.Search term. Matches
pharmacy_order_uid, pharmacy_order_name, routed payout provider_route_id, and routing_description.Unix timestamp for the start of the date range. For
routed rows, this filters by routing_created_at. For projected rows, this filters by pharmacy_order_created_at.Unix timestamp for the end of the date range. For
routed rows, this filters by routing_created_at. For projected rows, this filters by pharmacy_order_created_at.Field used for sorting. Accepted values are
pharmacy_order_created_at, routing_created_at, and amount.Sort direction. Accepted values are
asc and desc.Page number (0-indexed).
Number of items per page.
Statuses
| Status | Description |
|---|---|
projected | Indicative preview for a paid physical-prescription order based on current order values and routing configuration. This can change before the order is completed. |
routed | Persisted split-payment route created after pharmacy order completion. These values represent the routed amount recorded by RxScale. |
Example Request
Response
Response Fields
Payout rows for the requested page.
projected for indicative payouts on paid physical-prescription orders, or routed for persisted routes created after order completion.Payout amount in cents, for example
1299 for EUR 12.99.ISO 4217 currency code, for example
EUR.The payout component, such as
item_rest, item_markup, or shipping.Human-readable description of the routed or projected component.
Payment provider route identifier. This is populated for routed payouts when the provider returned an identifier, and
null for projected payouts.UID of the related pharmacy order.
Human-readable pharmacy order name, for example
#1001.Unix timestamp when the pharmacy order was created.
Unix timestamp when the split-payment route was created. This is
null for projected payouts and populated for routed payouts.Total number of payout rows matching the filters.
Total number of pages available for the current
limit.