In the text notification received by user? In the full sms received by user: Paid 2,000.00 Tsh to PawaPay Limited.Charges Tsh 170.00. New Balance 24,724.00 Tsh. Txn Id:MP240412.1711.Q26145Can we replace PawaPay Limited with our own company name?
For that to happen, you would need to have a dedicated wallet for that specific MNO. We can assist you with setting that up.
The following are the requirements:
Upgrading to our premium plan and having a local business license within that country.
Does this have support for crypto stablecoins where we can send USDC etc and for a user to cash this out in MoMo?
Hi, we dont support transfers from Crypto to Mobile Money - the coins would need to be exchanged for fiat currency and then transferred into our mechant account
Hi. I would like to know how to transfer wallet funds from one country to another in order to consolidate all payments into one for withdrawal. This is because We may have customers making payments from multiple countries and wishing to withdraw these funds or send them back to merchants in other countries. We are setting up a marketplace.
We do not have an automated mechanism for transfer of funds x-border from your pawapay account in country x to coutnry y. You would need to have a pawapay wallet in each target country, and request settlement to your bank in country x - then execute your transfer to your bank in country y, and then top up into the pawapay wallet in that country - at that point you can utilise the pawapay merchant api to transfer value to your merchants in that country
In addition, you can send us fund in USD for top-up of your pawaPay wallet, it will be converted to local currencies and credited into your wallet(s) either in one or multiple countries.
Hi, how can I set a local callback url? I keep getting returnUrl is invalid:
This works
```{
depositId: deposit_id,
amount: price,
returnUrl: 'https://www.test.com/payment/success',
country: pricedMusic.basePaymentCountryIso,
reason: `Buy something`
},
```
This fails
```{
depositId: deposit_id,
amount: price,
returnUrl: 'http://localhost:4000/payment/success',
country: pricedMusic.basePaymentCountryIso,
reason: `Buy something`
},
```
Hey. As pawaPay does not run on the same server as the application you are developing, it is not possible to use "localhost" as a callback URL. You need to use a domain or IP address that is accessible to the internet, not only your local network.
Regarding the low balance, we are trying this on staging. How do we top up our staging account?
To top up your sandbox account, you will need to initiate a deposit request and specify the amount you would like to add to your wallet. For example, to top up your Cameroon wallet, you will initiate the request and specify the Mobile Network Operator (MNO) within Cameroon.
What do i need to do to settle on pawaPay?
To settle your wallet on pawaPay, you can choose from two options during your initial account setup: on-demand settlement or scheduled settlement. Here's how each option works:
If your settlement involves a foreign currency, the pawaPay treasury team will contact you via email with the exchange rates. Once agreed, you will be settled to the bank account you specified during your initial account setup.
Additionally, here is documentation that can help you settle: https://pawapay.document360.io/docs/settling-your-wallets?highlight=sett
Are the minimum and maximum amounts in the sandbox environment the same as in production
Our sandbox is a replicate of the production in look, feel, functionalities and behaviour hence, same limit on production applies on the sandbox.
Would all MNO follow this structure of returning multiple ids? From the example below, which of the fields represents the actual proof-of-payment
The given example includes a JSON structure with a field named "correspondentIds", containing two different IDs: "MTN_INIT": "ABC123" and "MTN_FINAL": "DEF456". The structure seems designed to hold multiple identifiers related to a transaction or operation, presumably with different purposes indicated by their suffixes (INIT and FINAL).Regarding the query:1. **Following the Structure Across MNOs**: If all Mobile Network Operators (MNOs) would follow this structure (using correspondentIds to return multiple IDs like MTN_INIT and MTN_FINAL), it depends on the standard protocols or agreements in place between the MNOs and the service/system interacting with them. Without explicit documentation or agreements stating that all MNOs use a similar structuring for transaction identifiers, it cannot be conclusively stated that all MNOs follow this specific structure.2. **Which Field Represents the Actual Proof-of-Payment**: Among the fields presented, the one that represents the actual proof-of-payment is not explicitly clear without additional context. Typically, "proof-of-payment" refers to a confirmation or evidence that a payment has been made and accepted. Both MTN_INIT and MTN_FINAL could serve different roles in this process: - MTN_INIT could represent an initial transaction ID or a pre-authorization identifier given at the beginning of the payment process. - MTN_FINAL could represent the final confirmation ID, assigned after the payment process has been completed and confirmed.Given the typical usage of "proof-of-payment" in financial transactions, **MTN_FINAL** is more likely to represent the actual proof-of-payment because it suggests a final confirmation of the transaction. However, without further documentation or context specifying the meaning and use of these identifiers, this interpretation is speculative.For a definitive answer or if exceptions exist, refer to the official documentation or specifications related to the system or protocol you are interacting with.