Relqor — Gateway for Up2pay e-Transactions
by relqor 0 (0 reviews)

Relqor — Gateway for Up2pay e-Transactions

Accept card payments in WooCommerce through the Up2pay e-Transactions hosted payment page (Paybox System protocol).

Relqor ranks #53,662 among WordPress.org plugins with 0+ active installations, is #10,130 of 14,124 in the E-commerce category, and was last updated Oct 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v0.1.0 Current Version v0.1.0
Updated 4 days ago Last Update on 28 Oct, 2026
Refreshed 2 days ago Last Refreshed on
#10,130 of 14,124 in E-commerce Actively maintained
View on WordPress.org
Rank
#53,662
— No change
Active Installs
0+
— No change
KW Avg Position
19.3
0.4 better
Downloads
68
+3 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 40%
0+ 10+
26,094
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 6 more installs to reach 10+

Rank Changes

48,688 50,956 53,225 55,493 57,761 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
48,688 50,956 53,225 55,493 57,761 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Current #53,662
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 40 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
0 10 20 30 40 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Relqor — Gateway for Up2pay e-Transactions

No. Relqor is an independent plugin and is not affiliated with Verifone, Up2pay or Crédit Agricole.
New installations start in Test mode, on the test server recette-tpeweb.e-transactions.fr. Tick Enable and fill in "Test credentials (sandbox)"; if you have no test account, Crédit Agricole's guide "Up2pay e-Transactions – Réalisation des tests d'intégration" publishes a shared one with its HMAC key. Place your test order while logged in: in Test mode, only administrators and shop managers see the payment method. Pay with a test card from Verifone's DSP2 integration manual, such as 4000000000001000 (accepted without a 3-D Secure challenge). The payment page shows ***TEST*** before the shop name. An accepted test payment marks your test order as paid automatically once the payment notification reaches your store, so your store must be reachable from the Internet, even in Test mode. To go live, fill in "Production credentials", set Mode to Production and save: the payment method is then offered to all your customers, or disappears from checkout if the production credentials are incomplete. Manual confirmation is then on by default: each accepted payment puts the order on hold until you have checked it in Vision and changed its status yourself (see the question about orders "On hold" in production mode).
It appears in the classic checkout, the Checkout block and on the "Pay for order" page only when: the Enable box is ticked and the store currency is the euro; PHP's OpenSSL extension is available (it is needed to verify the platform's notifications); the credentials section that matches Mode is complete: a 7-digit SITE, a 2- or 3-digit RANG, an IDENTIFIANT of 1 to 9 digits, a hexadecimal HMAC key and a payment URL starting with https://; in Test mode, you are logged in as an administrator or shop manager (other visitors see it only in Production mode). A value in the wrong format is not saved: the field keeps its previous value, so check it again after saving.
The payment platform could not verify the request with your HMAC key. In the credentials section that matches Mode, paste the HMAC key for that Mode again, in full: the test and production keys are different. If saving then shows "the HMAC key is not 128 characters long", check your copy and paste. Also check SITE, RANG and IDENTIFIANT in the same section.
The plugin checks the order before sending the customer to the payment page: "Incomplete billing address: … is missing.": the billing first name, last name, address, postcode, city and country are sent to the platform for 3-D Secure, and the plugin never fills in a missing value. Keep these fields in your checkout, including for virtual products; address line 2 and the phone number are optional. "Your email address is not accepted by the payment platform …": the billing email must have 6 to 80 characters, no accents before the @ and a dot after it. "The payment service is temporarily unavailable …": no payment server answered "OK" on its status page (/load.html, see External services) within 5 seconds. If this happens for every order, check that your server can make outgoing HTTPS requests to the payment server. The relqor log gives the reason ("payment not possible before redirection", "payment form not generated" or "no payment server available").
Relqor changes the status only when the platform's signed notification reaches your site address followed by /?wc-api=relqor_ipn, as a GET request, without any login; the customer's return never changes it. The plugin sends this address with every payment request; according to the Up2pay e-Transactions integration manual, it takes priority over an address saved in Vision. If a firewall, bot protection, maintenance mode or a password protects the whole site, let this URL through. The plugin does not filter by IP address. In the relqor log, find the line "Order N: redirecting to the payment page (reference …)". If no later line mentions the order or that reference, the plugin processed no notification for it. If a later line says "Invalid IPN signature — call ignored" with that reference, a request arrived but could not be verified, and the order was not changed. If the customer did not pay, the order stays Pending payment unless a notification reports a refusal or a cancellation. With stock management on (the WooCommerce default), WooCommerce cancels unpaid checkout orders after its "Hold stock" time (60 minutes by default). If Vision shows an accepted transaction for the order's reference and amount, set the order to Processing or Completed yourself.
If the order note starts with "Signed payment notification received", the order is waiting for your check (manual confirmation, on by default). WooCommerce sends the customer its on-hold email and, until you act, the order-received page shows "Payment being confirmed". Look up the reference from the note in Vision, with the order total as the amount (see "Does the signed notification prove that the payment reached my account?"), then: If your account has an accepted transaction for them, set the order to Processing or Completed: WooCommerce then treats it as paid, gives access to downloads and sends the customer its usual email for that status. Otherwise, do not deliver: leave the order on hold or cancel it. A payment whose payment page was shown while manual confirmation was on still puts the order on hold, even after you uncheck it. If the note says "Payment awaiting approval by the issuer (code 99999 …)", see the question about "Failed", "Cancelled" or "On hold" orders.
No. The platform signs its notifications with its own key, the same for every merchant and for its test platform, and the signed data does not identify the merchant account: a notification produced on the public test platform, or for another merchant account, is validly signed too, and its values can quote a declined transaction or a transaction of another order. That is why, by default in production mode, Relqor does not mark an order as paid on a notification alone: a signed "payment accepted" notification puts the order on hold, with a note giving the reference, the authorization number and the transaction number. In the Vision back office, check that your account has an accepted transaction (authorized or captured; not declined, cancelled or pending) for that reference and for the order amount: the transaction number alone proves nothing. Then set the order to Processing or Completed. Until you do, nothing is delivered automatically, not even downloads, and later notifications for that order (declined, cancelled or another payment) only add a note; if you set the order back to Pending payment, another signed payment notification puts it on hold again. The test platform's authorization number (XXXXXX) is refused in production mode: the order is left unchanged, with a note. In test mode, an accepted payment marks the order as paid automatically, unless the order has a payment attempt created in production mode: such an order keeps the production rules even after you switch back to test mode, so XXXXXX is refused and, with manual confirmation, an accepted payment puts it on hold.
Yes: in the settings, uncheck "Manual confirmation in Production". A signed "payment accepted" notification then marks the order as paid through the standard WooCommerce payment flow (Processing, or Completed for virtual downloadable products). The plugin cannot tell such a notification apart from one produced on the public test platform for the same order and amount, so an order could then be marked as paid, and downloads made available, without any real payment. If you turn it off, check in the Vision back office that your account has an accepted transaction (authorized or captured; not declined, cancelled or pending) for each order's reference and amount before delivering it. The test platform's authorization number (XXXXXX) is still refused.
The plugin sets these statuses after a signed notification and explains each one in an order note: Failed: any response code not listed below, usually a refusal, for example 00151 (insufficient funds), 00105 (do not honor), 00154 (card expired) or 00004 (invalid card number or security code). 00006 means access refused: check SITE, RANG, IDENTIFIANT and the HMAC key. Cancelled: 00030 (time-out on the payment page) or 00117 (customer cancellation reported by the authorization center). A customer who leaves the payment page with its Cancel link may get another code: on the test platform, this link carries 00001, and a notification with that code sets the order to Failed. An order cancelled with the note "Unpaid order cancelled - time limit reached." was cancelled by WooCommerce itself (see the question about "Pending payment" orders). On hold: 99999 (the card issuer has not confirmed the payment yet; according to the platform's manual, a final notification follows) or, in production mode with manual confirmation, an accepted payment waiting for your check (see the question about orders "On hold" in production mode). A refusal never changes the status of a paid order or of an order waiting for your confirmation: a note is added. After a refusal, the customer can pay again, and the next accepted payment is processed normally.

Sign In / Register

You need to sign in or register to use this feature.