PayMaya will send the customer an OTP via SMS, and will ask for it in the form above. PayMaya presents the login screen, and the customer needs to enter the email or mobile number and the correct password. The difference is that the customer selects the button beside the star. It looks like this:Īs per usual, the payment flow starts from the screen above. The PayMaya mobile app will display a success page if there is enough balance in the account.Īt that point the web page will redirect to the appropriate URL (success or fail), which will be the values from the source created.Īside from Scan to Pay, PayMaya also offers another way to authorize the payment. The customer sees this on his mobile app after clicking "Scan to Pay" in PayMaya's menu.Īs soon as PayMaya detects the scan, the page where the QR code was displayed turns into a processing status page. Let's assume the customer opens his PayMaya app and chooses to scan the QR code being presented in his computer screen. This would be the screens of how it may look: The page looks like this:Īt this point, the merchant will not be involved in the process, and it will be up to PayMaya to obtain authorization from their member for the payment request. Take the value from checkout_url, and render it (or redirect) in your app. Take note of the checkout_url value, the merchant/user is expected to redirect or render a web page using that URL. You need to pass your public_token for this endpoint. To create a source token, you need to call POST request to. After successful or unsuccessful payment, Magpie will initiate a call to the redirect url provided in step 1.Each e-wallet provider will have their own way of handling payment authorization. Your customer will be taken to the particular e-wallet's authentication and authorization page.Render or redirect the request to the provided checkout_url.Most of the time, the url points to the wallet sources payment page. The response for the charge call will include a checkout_url field.Given the token from step #1, call the create charge endpoint and pass the source token ( src_).Create a source token containing details about the user's transaction.If you have encountered or integrated card payments with 3D Secure flow, you will be quite familiar with the sources flow. Our recommendation is to make small P1 payments after your integration. To test payments from the e-wallets, you will need an account for each e-wallet. As always, you will use your developer keys to sign the transactions you send to the API. There are no other special configurations to do. To sign up for a Magpie acccount, go here. You can also use this API for bank payments: With sources, Magpie merchants can now accept payments from the following e-wallets:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |