The AlinmaPay provider record holds the terminal details. Admins fill them once, and every website order uses the same record.

• Open Invoicing > Configuration > Payment Providers and pick AlinmaPay.
• Enter the Terminal ID, Terminal Password and Merchant Key from AlinmaPay.
• Add the Merchant ID and a Custom API URL only when the account needs them.
• Set State to Test Mode for the sandbox, or Enabled for live money.
• Turn on manual capture when the charge should wait for the shipment.

AlinmaPay sits with the other options on the Odoo website checkout. Shops tuning the cart step itself can look at Odoo Website Cart Settings.

Pay now hands the shopper to the gateway with the order total already filled in. Shops that also let buyers collect goods in person can add Odoo Website Store Pickup.

• The provider shows up once State is Enabled or Test Mode.
• Odoo passes the order reference, amount and currency to AlinmaPay.
• Billing name, email, street, city and country travel with the request.
• Shoppers come back to the Odoo payment status page after they pay.
• The customer portal shows the sales order with its payment message.

Card entry happens on the AlinmaPay hosted payment page, so no card number reaches Odoo.

Buyers choose Cards, type the card number, expiry, CVV and cardholder name, then confirm. Teams weighing a second gateway can compare the Odoo Website Wepay Payment Acquirer.

• The page lists the methods enabled on your AlinmaPay terminal.
• A terminal can carry mada, Visa, MasterCard and Apple Pay.
• Odoo signs each request with the Merchant Key before it leaves.
• AlinmaPay answers with an encrypted result that Odoo decrypts.
• The module keeps no saved cards, so every order opens the page.

With manual capture the checkout only authorizes the card. A transaction waits at Authorized until somebody acts on it.

Capture Transaction and Void Transaction sit at the top of the transaction form.

• The Capture dialog shows Authorized Amount and Amount To Capture.
• Lower that figure to capture part of the authorized money.
• Tick Void Remaining Amount to release the balance at the same time.
• Void Transaction cancels the whole authorization at AlinmaPay.
• Every capture lands as a child transaction under the first record.

Money can go back to the buyer in full or in part. Odoo sends the refund to AlinmaPay against the original transaction ID.

• Open the customer payment that the confirmed transaction created.
• Refund opens a dialog with Payment Amount and Refund Amount.
• Maximum Refund Allowed caps what is still open to send back.
• Odoo keeps the refund as a negative amount, such as -10.00 SR.
• Source Transaction points the refund at the payment it reverses.
• Each refund carries its own AlinmaPay provider reference.

Each attempt is a payment transaction in Draft, Pending, Authorized, Confirmed, Canceled or Error. Managers read the state without opening the AlinmaPay portal.

Groups that sell from several storefronts in one database can add Odoo Multi Website on top.

• Reference, Customer, Amount and Payment Method sit on the form.
• Provider Reference holds the AlinmaPay transaction ID.
• Created on and Last State Change Date show the timing of a charge.
• Child transactions list every capture and refund with its status.
• A gateway error message lands on the transaction for the admin.