You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(pos-app): migrate transactions API to unified Pay API
Migrate from old Merchant API (`/merchants/{id}/payments` with separate
`MERCHANT_PORTAL_API_KEY`) to unified Pay API (`/v1/merchants/payments`
with shared `getApiHeaders()`). Update response types from flat
snake_case to nested camelCase DTOs. Replace CAIP-19 token parsing with
server-provided display values. Remove `utils/tokens.ts` and merchant
API env vars.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Date range filter preference (for Activity screen)
82
83
83
84
2.**`useLogsStore`** (`store/useLogsStore.ts`)
84
85
- Debug logs for troubleshooting
@@ -220,20 +221,19 @@ All Payment API requests include:
220
221
221
222
### Transactions Service (`services/transactions.ts`)
222
223
223
-
> **Note:** The Merchants API currently has its own auth layer separate from the Payment API. Both share the same base URL (`EXPO_PUBLIC_API_URL`), but merchant endpoints authenticate via `EXPO_PUBLIC_MERCHANT_PORTAL_API_KEY` (sent as `x-api-key` header) rather than the partner API key used by payment endpoints. This will be unified in the future.
0 commit comments