Accept local payment methods¶
Stone Project uses your shop's Stripe account for invoice and deposit payments. Available methods depend on your Stripe account's country, enabled methods, invoice currency, amount and customer eligibility.
Turn on local methods¶
- Open Settings > Payment Gateways in Stone Project and configure Stripe with your own publishable key, secret key and webhook signing secret. Use keys from the same Stripe account and environment.
- In the Stripe Dashboard payment method settings, enable the methods your customers use. Complete any activation or mandate requirements Stripe shows.
- In Stripe Workbench, send these events to
https://api.remnantfinderapp.com/api/v1/webhooks/stripe:payment_intent.succeeded,payment_intent.payment_failed,payment_intent.processing,payment_intent.requires_action,payment_intent.canceled,charge.refunded, andcharge.dispute.created. Copy that endpoint's signing secret into Stone Project. Configure test and live environments separately. - Send the existing invoice or deposit payment link. The payment form automatically offers eligible methods. A method enabled in Stripe may still be unavailable for a particular currency or amount.
Do not enable a new method in production until you have checked a complete test payment and its final status in both systems. Fees and activation terms are your agreement with Stripe; enabling a method does not make it free.
What customers see¶
| Payment behavior | Examples | What happens |
|---|---|---|
| Approval in another app or page | Bancontact, iDEAL, EPS, Satispay, MB WAY, Pay by Bank | The customer approves with the provider and returns to the payment link. Stone Project checks the payment with Stripe. Closing the browser does not prevent the webhook from recording the payment. |
| Voucher or transfer instructions | OXXO, Multibanco, SPEI | The payment remains pending. Customers can reopen the original link to recover the same voucher, reference or transfer instructions. You can resend that payment link through the existing invoice/deposit sharing action. |
| Delayed bank debit | SEPA, Bacs, ACSS, BECS, PayTo | Submission is shown as awaiting confirmation. It is not a receipt and does not reduce the invoice balance until Stripe confirms receipt. Do not ask the customer to start another payment while it is pending. |
Your Payments list shows the pending payment and its full amount. Confirmation changes it to completed and updates the invoice or deposit. A failed payment remains unpaid, and the customer receives a failure notice when a previously pending payment fails. Reopening the payment link shows the current recorded status. A duplicate webhook does not create a second payment.
Mexico: OXXO, SPEI and meses sin intereses¶
- Use MXN documents and a Stripe account eligible for Mexican payment methods. SPEI requires a Stripe Customer: Stone Project creates or reuses one per customer inside your shop's Stripe account, including customers who have never saved a card. Instructions include the banking reference; partial funding remains pending until the full payment is confirmed. Stripe SPEI guide.
- Enable meses sin intereses (MSI) and choose the plans and amount limits in Stripe's payment settings. Eligible Mexican credit cards then show installment choices in the payment form. These bank installments are separate from the invoice installment schedule in Stone Project. MSI carries additional merchant fees. Stone Project does not turn it on or add a surcharge automatically. Stripe MSI setup.
- An OXXO voucher is not a completed payment. Stripe normally confirms a paid voucher on the following business day. An expired voucher can remain in processing while Stripe checks for a payment made before expiry. Stripe OXXO guide.
Limits and timing¶
Payment confirmation and payout to your bank are different events. The portal waits for confirmation; Stripe's payout schedule determines when money reaches your shop's bank.
| Method | Practical limit or timing |
|---|---|
| MB WAY | €0.50–€5,000 per payment. The customer's default daily limit is €1,000 and can be changed in their app. Use another enabled method when a balance exceeds their limit. Stripe |
| Bizum | €0.50–€5,000 per payment; the customer's bank may apply additional limits. Stripe |
| SPEI | Usually confirmed within 30 minutes on business days; weekends, holidays or maintenance can extend this. Stripe |
| OXXO | Normally confirmed on the next business day after the voucher is paid. See the voucher's expiry date. |
| Multibanco | Follow the voucher's expiry date. Bank reporting can arrive later; an expired voucher may remain processing during the provider's reconciliation period. Stripe |
| SEPA, Bacs, ACSS and BECS | Allow several business days; timing depends on method, mandate verification and bank calendars. The portal does not promise a single ACH deadline for all countries. SEPA, Bacs, ACSS, BECS |
Canada's Interac e-Transfer is not offered through this portal integration. Do not confuse in-person Interac Debit availability with an online e-Transfer API.
Yappy in Panama¶
Yappy appears in Payment Gateways only for shops whose company country is Panama. It uses Botón de Pago Yappy V2 and USD invoices or deposits.
- In Yappy Comercial, create a V2 payment button for your shop's exact portal website URL.
- In Stone Project, enter the Merchant ID, Secret key and Registered website URL. Select the matching environment, test the connection, then activate the gateway.
- The customer opens the normal payment link, enters their Panamanian Yappy mobile number and uses the Yappy button to approve in their app.
- The payment stays pending until Yappy's signed notification arrives. Cancelled, rejected or expired orders are not recorded as money received. Browser success messages alone cannot mark an invoice paid.
The notification address is sent automatically when Stone Project creates the order. Yappy does not publish a refund API for this button; arrange refunds in Yappy with the shop. Official V2 setup.
Testing: Yappy requires a registered test merchant and approved test app user. Stripe's US test account can simulate methods that the same account cannot accept live: our Bancontact, Multibanco, OXXO and SEPA tests do not establish live eligibility for a Mexican or European merchant. SPEI/MSI and each merchant's activated method list must be checked with that merchant's eligible account. No test credentials from a customer are assumed or requested automatically.