Payment Gateway Configuration

to accept online payments, you need to connect a payment gateway to your club remmu currently supports commercepay for online card and fpx payments 🔗 supported gateways gateway type status commercepay online card & fpx available razorpay online card coming soon stripe international card coming soon note bank transfer (manual proof upload) does not require a gateway — it works out of the box ⚙️ setting up commercepay step 1 get your commercepay credentials you need a commercepay merchant account if you don't have one, contact commercepay to sign up once approved, you'll receive merchant id api key secret key step 2 enter credentials in remmu go to settings → payments → gateway configuration and select commercepay enter merchant id api key secret key click save step 3 test the connection click test connection to verify your credentials are correct remmu will make a test call to commercepay and confirm the connection is live step 4 enable commercepay once the test passes, toggle commercepay to enabled under settings → payments → payment methods members can now choose online payment at checkout 💰 processing fees you can choose whether gateway processing fees are absorbed by your club or passed on to the member at checkout go to settings → payments → gateway configuration → processing fee who pays the fee option what happens club absorbs fee member pays the exact invoice amount; the gateway fee comes out of your revenue pass to member a processing fee line is added to the member's checkout total fee type choose how the fee is calculated type example percentage 2 5% of the payment amount fixed rm 1 50 flat fee per transaction enter the value and fee type, then click save the fee is applied automatically at checkout for all online payments through this gateway member checkout preview when the processing fee is passed to the member, the checkout screen shows a breakdown class fee rm 150 00 processing fee rm 3 75 (2 5%) ───────────────────────────── total rm 153 75 note bank transfer payments are not affected — processing fees only apply to online gateway payments 🎛️ per channel fee configuration commercepay supports several payment channels (fpx, duitnow qr, credit cards, e wallets, apple pay, etc ) each channel can have its own processing fee — useful when commercepay's costs vary by channel and you want to charge members the actual cost of each rail configure per channel fees in the per channel fees card under gateway configuration the list automatically shows only the channels your commercepay merchant account supports for each channel, choose fee mode behaviour inherit use the default processing fee set above none no fee on this channel — useful for absorbing the cost on cheap rails (e g duitnow qr) fixed flat rm amount per transaction percentage % of the transaction amount you can also enable or disable individual channels with a toggle — disabled channels won't appear at checkout amount limits per channel category you can set a minimum and maximum transaction amount per channel category — cards , fpx , e wallets , and qr codes channels are filtered out at checkout if the invoice amount falls outside their range common uses cards rm 1,000 minimum — discourage card use for small invoices where the processing fee outweighs the convenience fpx rm 30,000 maximum — match the bank's fpx limit so members aren't shown a method that will fail e wallets capped at rm 500 — keep low value impulse payments on wallets remmu also displays the gateway's own limits (from commercepay) as a read only reference below your custom limits, so you don't accidentally set a max higher than the gateway allows example use case duitnow qr none (absorb the small fee, encourage cheapest method) fpx inherit (your default 1 5%) credit card 3 0% (higher than default to cover visa / mastercard fees) apple pay disabled (don't offer this channel yet) the available channels are detected automatically from your commercepay merchant account if a new channel is added by commercepay, it will appear here on the next refresh 🔧 testing payments before going live, test the payment flow end to end ensure you're in test mode (toggle in gateway configuration) create a test payment for a student go through the checkout as a member use commercepay's test card numbers to simulate a payment confirm the payment status updates to paid in remmu switch back to live mode when satisfied 🔗 webhook configuration remmu automatically registers its webhook url with commercepay when you save your credentials this allows commercepay to notify remmu when a payment is completed, even if the member closes the browser no manual webhook setup is required ⚠️ troubleshooting payment stuck in "processing" the webhook may not have fired wait a few minutes, then check the payment status again admins can manually check the payment status from the payment record → check status test connection failing double check your credentials — copy paste directly from commercepay dashboard ensure your commercepay account is active (not pending approval) contact commercepay support if credentials look correct but still fail