Why payments are per storefront
WPLinker lets you configure payment methods per storefront because each storefront can represent a different brand, company, or legal entity. This means one storefront can use one Stripe account while another storefront uses bank transfer or another payment account.
This setup keeps invoices, payment accounts, and company details aligned. It is especially important when you manage multiple companies or sell publishing services for different brands.
Stripe setup
Enable Stripe only when you have the publishable key, secret key, and webhook signing secret ready. Stripe is used for payment processing; WPLinker still manages the subscription or order logic inside the platform.
Create a Stripe webhook endpoint using the webhook URL shown inside the Stripe credentials section. Select the required event checkout.session.completed and the recommended failure/refund events so WPLinker can update orders correctly.
- Required: checkout.session.completed
- Recommended: checkout.session.async_payment_failed
- Recommended: payment_intent.payment_failed
- Recommended: charge.refunded
Bank transfer setup
Bank transfer works independently from Stripe. You can use it as the only payment method on a storefront. Add the bank name, account holder, IBAN, BIC, bank address, and payment instructions.
When a buyer chooses bank transfer, the success page and invoice should show the payment instructions clearly. The seller can later mark the order as paid from the Orders page after receiving the payment.
PayPal and custom methods
PayPal can be configured separately from Stripe. If your business needs a local payment method that is not available yet, submit a feature request. WPLinker can evaluate and develop custom payment integrations for serious business cases.
Testing payments safely
Before going live, place one test order for each enabled payment method. Confirm that the order status, payment status, invoice, transaction record, and buyer confirmation email all match the expected flow.