Skip to content

Commit 6d7c0c8

Browse files
committed
Update code blocks language syntax to match file type
1 parent 5a5890e commit 6d7c0c8

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ For [Paystack](https://paystack.com), ensure to set `paystack_secret_key` key in
7070

7171
> **Warning** <br />
7272
> Ensure you have [TailwindCSS installed](https://tailwindcss.com/docs/installation), then add this package's views to the `content` key of your `tailwind.config.js` configuration file, like below:
73-
```
73+
```js
7474
content: [
7575
...,
7676
'./vendor/damms005/laravel-multipay/views/**/*.blade.php',
@@ -82,21 +82,21 @@ For [Paystack](https://paystack.com), ensure to set `paystack_secret_key` key in
8282

8383
- Flutterwave: If you want to use Flutterwave, ensure to get your API details [from the dashboard](https://dashboard.flutterwave.com/dashboard/settings/apis), and use it to set the following variables in your `.env` file:
8484

85-
```
85+
```env
8686
FLW_PUBLIC_KEY=FLWPUBK-xxxxxxxxxxxxxxxxxxxxx-X
8787
FLW_SECRET_KEY=FLWSECK-xxxxxxxxxxxxxxxxxxxxx-X
88-
FLW_SECRET_HASH='My_lovelysite123'
88+
FLW_SECRET_HASH=hash-123xxxxxxxxxxxxxxxxxxx-X
8989
```
9090

9191
- Paystack: Paystack requires a secret key. Go to [the Paystack dashboard](https://dashboard.paystack.co/#/settings/developer) to obtain one, and use it to set the following variable:
9292

93-
```
93+
```env
9494
PAYSTACK_SECRET_KEY=sk_test_xxxxxxxxxxxxxxxxxxxxx
9595
```
9696

9797
- Remita: Ensure to set the following environment variables:
9898

99-
```
99+
```env
100100
REMITA_MERCHANT_ID=xxxxxxxxxxxxxxxxxxxxx
101101
REMITA_API_KEY=xxxxxxxxxxxxxxxxxxxxx
102102
```
@@ -152,9 +152,9 @@ The metadata should be a valid JSON string containing key-value pairs that modif
152152

153153
If for any reason, your user/customer claims that the payment they made was successful but that your platform did not reflect such successful payment, this PCR feature enables you to resolve such claims by simply calling:
154154

155-
```
155+
```php
156156
/**
157-
* @var bool //true if payment was successful, false otherwise
157+
* @var bool $outcome // --> true if payment was successful, false otherwise
158158
**/
159159
$outcome = LaravelMultipay::reQueryUnsuccessfulPayment($payment)
160160
```

0 commit comments

Comments
 (0)