Redeems cashback for a checkout
This endpoint allows you to apply cashback discount to a checkout/cart.
Input Parameters
CustomerId(required): The customer identifier (email or document/CPF)CheckoutId(required): The checkout/cart ID from the e-commerce platformCashbackValue(optional): The specific amount of cashback to apply. If not provided, the maximum available cashback will be used.Total(optional): The checkout total value. Used for validation.OriginalKey(optional): A unique key to identify this redemption (for idempotency)RedeemOrigin(optional): The origin of the redeem request
Response
On success, returns the reward information including:
RewardId: The unique ID for this rewardExternalCode: Code to be used when sending orders to BonifiQOriginalKey: The key identifying this redemptionPoint: Information about the points usedCoupon: The coupon information (if generated)
Important Notes
- If the customer already has cashback applied in another checkout (without an order), it will be automatically refunded.
- The cashback value cannot exceed the checkout total or the customer’s available cashback balance.
Authorizations
Use API Basic Auth Keys
Body
The redeem request
Request to redeem cashback in a checkout
Customer identifier (email or document/CPF)
The checkout/cart ID from the e-commerce platform
Optional: The specific amount of cashback to apply. If not provided, the maximum available cashback will be used.
Optional: The checkout total value. Used for validation.
Optional: Platform-specific token for the checkout
Optional: A unique key to identify this redemption (for idempotency)
Optional: The origin of the redeem request
0, 1, 2, 3, 4, 5 Optional: List of order items for cashback eligibility validation. If provided, only eligible items will be considered for cashback calculation. If not provided, the full order total will be used (backward compatible behavior).
Response
The reward information
Standard response envelope used by the External API.
Error message returned when the request fails validation or processing.
For warnings and successful responses, consumers should usually inspect Result, Code and Severity first.
Legacy numeric error code derived from internal API errors when available.
This field is relevant only for error flows that use ApiResponseErrorDescription.
Business payload returned by the endpoint.
Endpoint-specific business code formatted as a two-digit string, such as 03 or 07.
This field is available for success, warning and error outcomes.
Symbolic enum name associated with Code, such as CheckoutNotFound.
Final severity of the response.
Success means the action completed as expected, Warning means the request was valid but the business outcome is informational or non-ideal, and Error means the request should be treated as a failure.
0, 1, 2 Convenience flag that is true when Severity is Warning.
Warnings are valid 200 OK business outcomes and should not be handled as transport or validation errors.
Indicates whether the request failed and should be handled as an error response.
This flag is reserved for real API errors; warnings must keep this property as false.