Testing Your Integration

​

Notch Pay’s Commitment to Security

​

Test Mode vs Production Mode

1. Test Mode: Use this mode for development and testing. Transactions made in test mode don’t involve real money.
2. Production Mode: Use this mode for real transactions. Transactions made in production mode involve real money.

1. Log in to your Notch Pay Business Suite
2. Click on the environment selector in the top navigation bar
3. Select “Sandbox” or “Production Mode”

​

Test API Keys

1. Go to your dashboard in test mode
2. Navigate to Settings > API Keys
3. Copy your test API key

pk_test_123456789

​

Phone Numbers for Mobile Money Testing

• XXX000000: Success
• XXX000001: Insufficient funds
• XXX000002: Failure (other reason)
• XXX000003: Timeout (no response)
• XXX000004: Canceled by user

​

Cameroon (CM)

​

Ivory Coast (CI)

​

Nigeria (NG)

​

Senegal (SN)

​

Gabon (GA)

​

Benin (BJ)

​

Burkina Faso (BF)

​

Uganda (UG)

​

Rwanda (RW)

​

DR Congo (CD)

​

Tanzania (TZ)

​

Kenya (KE)

​

Ghana (GH)

​

Chad (TD)

​

Central African Republic (CF)

​

Congo Brazzaville (CG)

​

Testing Webhooks

• Webhook Setup - Learn how to set up webhook endpoints
• Verifying Webhooks - Learn how to verify webhook signatures

1. Make sure to use your sandbox webhook hash key (prefixed with hsk_test_) for signature verification
2. Check that your code is reading the signature from the x-notch-signature header
3. Use your sandbox private key for webhook management operations
4. Test all relevant Mobile Money event types (payment.complete, payment.failed, etc.)
5. Verify that your application correctly processes each event type
6. Test error handling by intentionally causing webhook verification failures
7. Test with different Mobile Money operators to ensure your webhook handling is robust

​

Testing Different Mobile Money Scenarios

Important: When testing and especially in production, avoid repeatedly using the same phone number for all transactions. Notch Pay’s fraud detection system may flag accounts that consistently process transactions with the same phone number, potentially resulting in blocked transactions or account suspension.

​

Successful Mobile Money Payment

1. Create a payment using your test API key
2. Use a test phone number configured for success (e.g., +237670000000 for MTN Cameroon)
3. Verify that your application handles the successful payment correctly
4. Verify that webhooks and callbacks are processed correctly
5. In your test suite, use different test phone numbers for different test cases

​

Failed Mobile Money Payment (Insufficient Funds)

1. Create a payment using your test API key
2. Use a test phone number configured to fail with “insufficient funds” (e.g., +237670000001 for MTN Cameroon)
3. Verify that your application handles the payment failure correctly
4. Verify that appropriate error messages are displayed to users

​

Failed Mobile Money Payment (Other Reason)

1. Create a payment using your test API key
2. Use a test phone number configured to fail with “other reason” (e.g., +237670000002 for MTN Cameroon)
3. Verify that your application handles the payment failure correctly
4. Verify that generic error messages are displayed to users

​

Mobile Money Payment Timeout

1. Create a payment using your test API key
2. Use a test phone number configured to simulate a timeout (e.g., +237670000003 for MTN Cameroon)
3. Verify that your application handles timeouts correctly
4. Verify that your application allows the user to retry or choose another payment method

​

Mobile Money Payment Canceled by User

1. Create a payment using your test API key
2. Use a test phone number configured to simulate a cancellation by the user (e.g., +237670000004 for MTN Cameroon)
3. Verify that your application handles canceled payments correctly
4. Verify that your application allows the user to retry or choose another payment method

​

Testing Mobile Money Transfers

1. Add funds to your test account (this is simulated in test mode)
2. Create a beneficiary using a test Mobile Money phone number
   • For a successful transfer: +237670000000 (MTN Cameroon)
   • For a failed transfer: +237670000002 (MTN Cameroon)
3. Initiate a transfer to the beneficiary by specifying the appropriate channel (e.g., “cm.mtn” for MTN Cameroon)
4. Verify that your application handles the transfer status correctly
5. Also test transfers to other Mobile Money operators in different countries
6. Use different phone numbers for your test transfers

Important: Notch Pay’s fraud detection system monitors transaction patterns. Consistently sending all transfers to the same phone number may be flagged as suspicious activity, potentially resulting in blocked transactions or account suspension. In production, ensure your transfers are distributed across different recipients.

​

Example of Creating a Mobile Money Transfer

// Example with JavaScript
fetch('https://api.notchpay.co/transfers', {
  method: 'POST',
  headers: {
    'Authorization': 'pk_test_123456789',
    'X-Grant': 'your_private_key',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    amount: 5000,
    currency: 'XAF',
    beneficiary: {
      name: 'John Doe',
      phone: '+237670000000', // Test number for a successful transfer
      email: 'john@example.com'
    },
    channel: 'cm.mtn', // MTN Mobile Money Cameroon channel
    description: 'Test transfer'
  })
})
.then(response => response.json())
.then(data => console.log(data))
.catch(error => console.error('Error:', error));

​

Notch Pay’s Fraud Detection System

Important: For a complete understanding of our fraud detection system, please refer to our Complete Guide to Fraud Detection System.

​

Key Points to Remember During Testing

1. The system is active in sandbox: Our fraud detection system is active even in the test environment, though with less strict parameters
2. Avoid recipient concentration: Don’t direct all your transactions to the same phone number
3. Vary amounts: Avoid consistently using the same transaction amounts
4. Provide complete information: Always include accurate and complete customer information
5. Test rejections: Familiarize yourself with how your application handles rejected transactions

Tip: Use the sandbox environment to understand how our fraud detection system works and how your application should react when transactions are flagged as suspicious.

​

Common Issues During Testing

​

Webhook Verification Failures

• You’re using the correct webhook hash for the test environment
• Your webhook endpoint is accessible from the Internet
• Your server responds with a 2xx status code

​

API Key Confusion

​

Missing Test Data

​

Going to Production

​

Notch Pay’s Rigorous Production Environment

• Strict Transaction Monitoring: All production transactions are rigorously monitored
• Regulatory Compliance: We adhere to financial regulations in all countries we operate
• Zero Tolerance for Fraud: Suspicious activities are promptly investigated
• Account Verification: Merchant accounts undergo thorough verification
• Regular Compliance Checks: We perform ongoing compliance reviews

​

Production Checklist

1. Switch to production mode in your dashboard
2. Update your integration to use your production API keys
3. Update webhook endpoints to your production URLs
4. Perform a final test with a small real payment
5. Ensure your application distributes transactions across different phone numbers
6. Review and comply with our security best practices
7. Understand our fraud detection system and its implications
8. Prepare your team to handle potentially blocked transactions

Critical Production Warning: In production, your application must avoid sending all transactions to the same phone number. Notch Pay’s fraud detection system will flag and may block accounts that consistently process transactions with the same phone number. This is a security measure to prevent fraud and money laundering. Design your application to naturally distribute transactions across different recipients or implement safeguards if your business model requires repeated transactions to the same recipients.

​

Mobile Money Testing Checklist

• Successful Mobile Money payment
• Handling failed Mobile Money payments (insufficient funds)
• Handling failed Mobile Money payments (other reasons)
• Handling Mobile Money timeouts
• Handling Mobile Money payments canceled by the user
• Verification of webhooks for Mobile Money events
• Successful Mobile Money transfers
• Handling failed Mobile Money transfers
• Testing with different Mobile Money operators (MTN, Orange, Moov, Wave, etc.)
• Testing with different countries (Cameroon, Ivory Coast, Senegal, Kenya, etc.)
• Testing specific Mobile Money validation errors (invalid number, etc.)
• Testing Mobile Money refunds
• Testing pagination for Mobile Money transaction lists
• Testing filters and searches for Mobile Money transactions

​

Best Practices for Mobile Money Testing

1. Use a Dedicated Test Environment: Maintain a test environment separate from your production environment.
2. Automate Tests: Create automated tests to regularly verify that your Mobile Money integration works correctly.
3. Test All Scenarios: Don’t just test successful payments, but also the different types of failures specific to Mobile Money.
4. Test with Different Operators: Make sure to test with all Mobile Money operators you plan to support.
5. Test with Different Countries: Mobile Money regulations and behaviors can vary across African countries.
6. Monitor Processing Times: Mobile Money payments can have variable processing times, ensure your application handles these delays correctly.
7. Test Error Messages: Verify that your application displays clear and helpful error messages specific to Mobile Money.
8. Test Amount Limits: Mobile Money operators often have minimum and maximum transaction limits, test these limits.
9. Monitor Logs: Keep an eye on your logs to detect potential issues with Mobile Money transactions.
10. Test Performance: Ensure your application can handle multiple simultaneous Mobile Money transactions.
11. Distribute Transactions: Do not use the same phone number for all transactions, as this may be flagged as suspicious activity.

Important: Notch Pay’s fraud detection system may flag or block accounts that consistently send all transactions to the same phone number. In production, ensure that your integration distributes transactions across different recipients to avoid being flagged for suspicious activity or having your merchant account blocked.

​

Available Mobile Money Channels

​

West Africa

​

Central Africa

​

East Africa

​

Additional Resources

• Mobile Money - Comprehensive guide on integrating Mobile Money payments
• Production Checklist - Make sure you’re ready for production