Order Status
Query Transaction/Order Status
Retrieve transaction details using payment intent ID, order reference, or transaction reference
GET
Overview
Retrieve detailed information about a specific transaction using one of three identifiers: the payment intent ID, your merchant order reference, or the Waypay transaction reference. This flexibility allows you to query transactions using whichever identifier is most convenient for your system.Path Parameters
Transaction identifier - can be one of three types:You can provide any of the following:
- Payment Intent ID - The UUID returned when creating a payment (e.g.,
550e8400-e29b-41d4-a716-446655440000) - Merchant Order Reference - Your
orderRefprovided when creating the transaction (e.g.,ORD123456) - Transaction Reference - The
txnRefreturned by Waypay (e.g.,WP20251212123456)
API version (e.g., “1”)
Response
Unique transaction identifier
Transaction amount
Currency code (e.g., “PKR”, “USD”)
Transaction processing fee
Net amount after fees
Transaction type:
0- CardDeposit (Deposit)1- WalletDeposit2- Transfer3- Withdrawal4- WalletWithdrawal5- Fee6- Reversal (Reversed)7- Settlement8- Refund
Transaction type description (e.g., “Deposit”, “WalletDeposit”, “Withdrawal”)
Transaction description
Additional transaction notes
Payment provider used
Transaction reference number
Transaction status:
1- Pending2- Completed3- Failed4- Cancelled5- RefundRequested6- RefundFailed7- Refunded8- InProgress9- OnHold10- Reversed11- Disputed12- Settled
Human-readable status description (e.g., “Pending”, “Completed”, “Failed”)
Transaction creation timestamp (UTC)
Whether this is a live or test transaction
Transaction mode (e.g., “Live”, “Test”)
Your merchant order reference (the orderRef you provided)
Payment intent identifier
Name of the fee rule applied to this transaction
Detailed breakdown of how the fee was calculated
Query by Payment Intent ID, Order Reference, or Transaction Reference
This endpoint supports querying transactions using three types of identifiers, giving you maximum flexibility:Payment Intent ID (paymentIntentId)
- What it is: A UUID generated by Waypay when you create any payment, deposit, or withdrawal order
- Format: UUID (e.g.,
550e8400-e29b-41d4-a716-446655440000) - Where to get it: Returned immediately in the API response when creating a transaction
- Use case: Query transactions right after creation using the payment intent ID you just received
Merchant Order Reference (orderRef)
- What it is: Your own order reference that you provided when creating the transaction
- Format: Your custom format (e.g.,
ORD123456,ORDER-2025-001,INV-2025-12345) - Where to get it: From your own system/database
- Use case: Query transactions using your internal order tracking system without storing Waypay IDs
Transaction Reference (txnRef)
- What it is: A unique reference generated by Waypay after the transaction is processed
- Format: Waypay’s format (e.g.,
WP20251212123456) - Where to get it: Returned in webhook notifications and transaction details
- Use case: Query transactions when you have the Waypay transaction reference from webhooks or receipts
Recommended Approach: Use your merchant order reference (orderRef) for the easiest integration. This allows you to query transactions without storing any Waypay-generated identifiers.
Which Identifier Should You Use?
| Identifier | Best For | Availability | Format |
|---|---|---|---|
| Payment Intent ID | Immediate status checks after creating a transaction | Available instantly in API response | UUID |
| Order Reference | Integration with existing order management systems | Always available (you provide it) | Your custom format |
| Transaction Reference | Webhook processing and customer receipts | Available after transaction processing | Waypay format |
Response Fields Explained
Transaction Types (txType)
ThetxType field indicates what type of transaction this is:
| Value | Type | Description |
|---|---|---|
| 0 | CardDeposit | Customer payment via card (displays as “Deposit”) |
| 1 | WalletDeposit | Payment via mobile wallet |
| 2 | Transfer | Internal transfer between accounts |
| 3 | Withdrawal | Bank withdrawal/disbursement |
| 4 | WalletWithdrawal | Mobile wallet withdrawal |
| 5 | Fee | Transaction processing fee |
| 6 | Reversal | Transaction reversal (displays as “Reversed”) |
| 7 | Settlement | Merchant settlement payout |
| 8 | Refund | Money returned to customer |
Transaction Status (status)
Thestatus field shows the current state of the transaction:
| Value | Status | Description |
|---|---|---|
| 1 | Pending | Transaction initiated, awaiting processing |
| 2 | Completed | Transaction completed successfully |
| 3 | Failed | Transaction failed |
| 4 | Cancelled | Transaction cancelled by user or system |
| 5 | RefundRequested | Refund has been requested |
| 6 | RefundFailed | Refund attempt failed |
| 7 | Refunded | Transaction has been refunded |
| 8 | InProgress | Transaction is currently being processed |
| 9 | OnHold | Transaction temporarily on hold |
| 10 | Reversed | Transaction has been reversed |
| 11 | Disputed | Transaction is under dispute |
| 12 | Settled | Transaction has been settled to merchant account |
Best Practices
- Use Order Reference: Query by your
orderReffor the easiest integration - no need to store Waypay identifiers - Store Payment Intent ID: If you need immediate status checks, save the
paymentIntentIdreturned from transaction creation - Poll Wisely: Don’t poll too frequently. Use webhooks for real-time updates instead
- Handle 404s: A 404 response means the identifier doesn’t exist or you don’t have access to it
- Store Transaction IDs: Save the
idfield from responses for your records and reconciliation - Check Status: Always verify the
statusfield before processing the transaction - Fee Transparency: Use
feeCalculationBreakdownto understand fee calculations - Reconciliation: Use
merchantOrderRefto match transactions with your orders - Live vs Test: Check
isLiveto distinguish between production and test transactions - Choose the Right Identifier: Use payment intent ID for immediate checks, order reference for long-term tracking
Use Cases
Immediate Status Check After Payment Creation
Immediate Status Check After Payment Creation
Check transaction status immediately after creating a payment using the payment intent ID.
Order Status Page
Order Status Page
Display transaction status to customers on your order status page by querying with your order reference.
Webhook Verification
Webhook Verification
Verify webhook notifications by querying the transaction using the txnRef from the webhook payload.
Reconciliation
Reconciliation
Match transactions with your internal orders for accounting and reconciliation.
Customer Support
Customer Support
Look up transaction details when customers contact support with their order number.
Payment Receipt Generation
Payment Receipt Generation
Generate detailed payment receipts using the payment intent ID or transaction reference.
Common Error Scenarios
| Error | Cause | Solution |
|---|---|---|
| 404 Not Found | Identifier doesn’t exist or access denied | Verify the identifier is correct and belongs to your merchant account |
| 400 Bad Request | Invalid identifier format | Ensure the identifier string is properly formatted (UUID for payment intent, your format for order ref) |
| 401 Unauthorized | Invalid or missing API key | Check your API key is correct and has not expired |
Security Considerations
- Keep API keys secure and never expose them in client-side code
- Use HTTPS for all API communications
- Implement proper error handling for failed queries
- Log all transaction queries for audit purposes
- Rate limit your queries to avoid overwhelming the API
- Validate transaction data before using it in your system
Next Steps
Setup Webhooks
Get real-time transaction updates
Transaction Status Guide
Understand transaction lifecycle
Create Refund
Process refunds for transactions
Payment Endpoints
Create new payment transactions