PayID Testing

The PayID sandbox environment uses specific payment amounts to simulate different scenarios. By entering these amounts when creating or processing payments, you can test how your integration handles both successful and failed transactions.

Successful Payment Scenarios

Standard Successful Payments

• Amount: $1.00 – $4,000.00
• Behaviour: Payment is processed successfully with immediate completion
• Use case: Test normal payment flows and successful transactions

Manual Payment Processing

• Amount: $5,000.01 – $99,999.00
• Behaviour: Payment requires manual approval before completion
• Use case: Test delayed or manual processing workflows To complete manual payments, use the dedicated testing URL provided in your sandbox environment.

Payment Failure Scenarios

PayID Expiry

• Amount: $4,055.00
• Behaviour: PayID expires after 5 seconds
• Use case: Test how your system handles expired PayIDs

Incorrect Payment Amounts

• Overpayment – $4,104.00
• Simulates a customer paying more than the requested amount
• → Use to test overpayment handling
• Underpayment – $4,006.00
• Simulates a customer paying less than the requested amount
• → Use to test underpayment handling

PayID Creation Failure

• Amount: $4,052.00
• Behaviour: PayID creation fails validation
• Use case: Test error handling during PayID creation

Refund Testing Scenarios

Refund Validation Error

• Amount: $4,303.00
• Behaviour: Refund fails due to invalid payment status
• Error message: Refunds can only be processed on COMPLETE, RETURN_COMPLETE or RETURN_FAILED payments
• Use case: Test how your system handles refund errors

Example Testing Workflows

Successful End-to-End Flow

• Create a PayID with an amount of $100.00
• Complete the payment (should succeed instantly)
• Process a full refund (should succeed)

Expired PayID Scenario

• Create a PayID with an amount of $4,055.00
• Wait at least 5 seconds
• Attempt payment (should fail due to expiry)

Refund Error Scenario

• Create a PayID with an amount of $4,307.00
• Complete the payment successfully
• Attempt a refund (should fail with an error)

Notes

• Always use the specified amounts exactly to trigger each scenario
• These behaviours are specific to the sandbox environment only and will not occur in live transactions
• Use these scenarios to ensure your integration handles both success and error cases correctly