We are testing refunds for an auto-renewable subscription in the Sandbox environment using Transaction.beginRefundRequest(in:), following "Testing refund requests". Our server receives CONSUMPTION_REQUEST, but a REFUND or REFUND_DECLINED notification never follows.
What we did (4 transactions, Nov 16, 2026)
Purchased a monthly subscription with sandbox renewal rates of 1 hour, 30 minutes and 5 minutes, then turned off auto-renew.
Submitted the refund sheet:
one request with a standard reason;
others with Issue = Other and text GRANT_PRORATED.
We also used a second sandbox account.
For one transaction, we called Send Consumption Information v2 within 5 minutes of the CONSUMPTION_REQUEST. The body was customerConsented: true, deliveryStatus: DELIVERED, sampleContentProvided: false, refundPreference: GRANT_PRORATED. The API returned 202 Accepted.
What we see
CONSUMPTION_REQUEST arrives 1–2 minutes after the refund sheet is submitted. Our server returns HTTP 200, and Get Notification History shows the send attempt as SUCCESS.
No REFUND or REFUND_DECLINED arrived.
Get Refund History v2 is empty, Get Transaction Info shows no revocationDate, and Get Notification History has no refund notification.
All other sandbox notifications are delivered within a second: SUBSCRIBED, DID_CHANGE_RENEWAL_STATUS, EXPIRED.
In production, REFUND, REFUND_DECLINED and REFUND_REVERSED are delivered normally for the same app.
Sandbox transaction IDs
2000001266241009, 2000001266277405, 2000001266288964, 2000001266312137
Feedback: FB25595203
Questions
Is there a known issue with Sandbox not deciding refund requests for auto-renewable subscriptions after CONSUMPTION_REQUEST?
Is there a supported way to receive a real REFUND notification in Sandbox for end-to-end server testing?
Thank you.
Topic:
App & System Services
SubTopic:
StoreKit
0
0
72