When Should I Start Building On My Own

Transaction Verification on Flutterwave

I would like to thank hotels.ng who grant some one like me the privilege to work with flutterwave . So i decided to put this together it could be of help to some who has no or little knowledge on payment verification with Rave before giving value to your customer on your website.

flutterwave

After integrating Rave and a user has successfully paid, you need to verify that the payment was successful with Rave before giving value to your customer on your website.

Below are the important things to check for when validating the payment: First,

Verify the transaction reference.

Verify the status of the transaction to be a success.

Verify that a charge response chargeResponse found in response.data.flwMeta has the value 00 or 0.

Verify that the currency is the expected currency to accept payments in.

Then you are good to go..

Note this when performing a status check with your unique reference

On Rave i will advised you complete a status check for every transaction using the unique transaction reference (flwRef) generated by the gateway. But if it is absolutely necessary you use your own unique transaction reference to perform a status check, you must strictly adhere to the following measure:

1. Ensure your transaction reference is unique for every transaction.
2. If using the Rave inline function, ensure you split payment methods i.e. separate card payments on the modal from account payments.

• Pass your unique transaction ref to the status check endpoint as tx_ref in place of passing the gateway's unique transaction reference (flw_ref).                                           https://medium.com/@opinerdan/transaction-verification-on-flutterwave-e5ed3bf34fce

• Payments
• Mark Essien