Payment Policy

This policy applies to payments, payment attempts, receipts, refunds, disputes, and payment-related communications connected to orders placed through the Inkora Beauty Supplies storefront.

The accepted order, payment record, gateway record, refund record, receipt, invoice, customer notification, and provider confirmation together form the operational history of a transaction.

This policy should be read with the terms and conditions, privacy policy, shipping policy, and return and refund policy.

Nothing in this policy removes a consumer, banking, payment, data-protection, or legal right that cannot lawfully be excluded or restricted.

Before payment is authorised, checkout displays the products, quantities, product prices, discounts, shipping charge, tax, payment-related fee where applicable, currency, and final total.

The storefront recalculates these values on the server. A browser value, screenshot, cached page, altered request, or previously viewed price does not override the valid checkout calculation.

Any customer-facing payment fee must be included in the checkout total before the customer authorises payment. Provider fees absorbed by Inkora are not added later to an accepted order.

Inkora will not intentionally charge a higher amount than the amount properly disclosed and authorised for the payment attempt.

Where an obvious pricing, discount, tax, currency, shipping, or configuration error is detected before fulfilment, Inkora may pause the order and contact the customer about correction, cancellation, or refund while preserving applicable consumer rights.

The payment methods available for a particular order are the active methods displayed during checkout.

Method availability may depend on currency, minimum or maximum amount, provider operation, destination, order status, risk review, customer eligibility, and the gateway configuration in effect at checkout.

The appearance of a payment method elsewhere on the website does not guarantee that it will be available for every order.

Do not send payment to an account, link, QR code, telephone number, wallet, or individual that is not displayed through an authorised Inkora channel or confirmed by Inkora support.

Where Paystack is selected, Inkora creates a provider transaction using the order, customer, currency, outstanding balance, and unique transaction reference.

The customer completes payment through the Paystack-controlled checkout experience or another authorised Paystack payment channel.

A return to the Inkora website does not by itself determine whether payment succeeded. Inkora verifies the transaction with Paystack and may also receive an authenticated webhook notification.

Inkora validates the payment reference, status, amount, currency, customer information, order information, and relevant metadata before applying the payment to the order.

A correctly verified Paystack success can be processed safely even when the callback and webhook arrive more than once or in a different order.

Where bank transfer is offered, follow the account details and reference instructions shown for the order. A transfer is not treated as confirmed until Inkora verifies receipt and matches the funds to the correct order.

Use the order number or other required payment reference exactly as instructed. An incorrect or missing reference may delay matching and confirmation.

A transfer receipt, debit alert, screenshot, teller, or customer statement is evidence for review but does not replace confirmation that cleared funds were received in the correct account.

Do not transfer to a personal or substituted account merely because the request appears to come from a social-media profile, chat, telephone call, or unverified message.

Where an overpayment, duplicate transfer, unidentified transfer, or incorrect transfer occurs, Inkora may request reasonable transaction information before refunding, reallocating, or otherwise resolving the amount.

By submitting a payment, the payer confirms authority to use the selected payment method and authorises the disclosed transaction amount.

A customer placing an order for a business or another person is responsible for ensuring that the payer, account holder, cardholder, or transfer originator has authorised the transaction.

Inkora or the payment provider may request authentication, one-time confirmation, identity checks, address checks, transaction review, or other security steps.

A transaction may be declined, held, reversed, or investigated by the payment provider, financial institution, Inkora, or another authorised participant where security, fraud, compliance, account, or transaction concerns arise.

Inkora treats provider verification, authenticated provider notifications, cleared bank funds, or another reliable reconciliation source as the basis for confirming payment.

A successful payment record includes the amount, currency, payment method, status, internal reference, provider or gateway reference where available, and verification or payment timestamps.

Successful payments and successful refunds update the related order paid amount, refunded amount, payment status, and payment method through controlled database transactions.

A payment that cannot be matched to the correct order, customer, amount, currency, or reference may be held for investigation instead of being applied automatically.

Inkora may correct a payment record where reliable provider or banking evidence shows that the earlier status was incomplete or incorrect.

A pending or processing status means that final payment confirmation has not yet been recorded. Do not treat a debit alert, browser message, screenshot, or customer statement alone as final settlement.

A customer who sees a debit without an updated successful payment should keep the transaction reference and contact Inkora and, where necessary, the payment provider or financial institution.

Do not immediately make repeated payments solely because the browser did not return to Inkora. First review the order and payment status in the customer account.

A failed, abandoned, cancelled, or expired attempt does not count toward the order paid amount unless reliable reconciliation later confirms that funds were actually received.

Temporary provider, network, browser, bank, or webhook interruptions may delay status updates without changing the underlying financial result.

An eligible customer may use Retry Payment where the order uses Paystack, remains open, has an unpaid balance, and does not already have a final paid or refunded payment status.

The retry workflow rechecks customer ownership, order status, payment method, outstanding balance, currency, gateway limits, and the active Paystack configuration.

Where a recent valid Paystack checkout session exists, Inkora may resume it instead of creating another payment attempt.

After full payment is confirmed, other incomplete Paystack attempts for the same order may be cancelled as superseded.

A customer should not retry through an old, copied, modified, or third-party payment link that is not connected to the current Inkora order record.

An order may contain multiple payment attempts, but each confirmed payment amount must be supported by a distinct valid transaction record.

Repeated callbacks, browser refreshes, or duplicate webhook deliveries should not create duplicate successful value for the same payment reference.

Where more than one separate payment is successfully received or the total paid exceeds the amount properly due, Inkora will review the transaction records and the order balance.

A confirmed duplicate payment or overpayment may be refunded, applied to another authorised obligation, converted to store credit where lawfully offered and accepted, or resolved through another agreed method.

The customer may be asked to provide the order number, payer name, amount, date, bank or provider reference, and suitable proof that does not expose secret credentials.

A successful, partially refunded, or refunded payment may have an individual payment receipt linked to its payment number and receipt number.

The order invoice and payment receipt serve different purposes. The invoice summarises the order, while the receipt records a particular confirmed payment and any reflected refund status.

Customers should download documents through the authenticated account rather than relying only on screenshots or forwarded messages.

A receipt does not alter the product, shipping, return, tax, refund, or order terms recorded elsewhere in the transaction.

Contact Inkora where a receipt, invoice, order total, payment amount, payer detail, or reference appears incorrect.

A refund is created only against a valid payment and related order. It may be full, partial, item-based, shipping-based, or an approved adjustment.

The cumulative successful refunds must not exceed the refundable balance of the payment, order, or affected order items.

A refund may be issued to the original payment method, bank transfer, cash, store credit, or another approved method depending on the transaction, provider capability, customer agreement, and applicable requirements.

A refund can remain pending or processing while provider, bank, administrative, or reconciliation steps are completed.

After an approved refund is processed, the time required for funds to appear may depend on the payment provider, bank, card issuer, transfer channel, or other financial institution.

The customer account may show the refund number, amount, currency, method, status, transaction reference, related return, and processed date.

The refundable amount depends on the approved remedy and may include eligible product value, shipping, tax, or another approved adjustment.

The original provider transaction fee, customer-facing fee, delivery charge, return-shipping cost, discount, tax treatment, and prior refund may affect the final amount where permitted and properly disclosed.

A provider fee absorbed by Inkora does not automatically increase or reduce the customer refund.

A customer-facing fee that was charged as part of the order will be considered according to the reason for refund, applicable law, provider rules, and the approved refund record.

Inkora will not issue refunds above the confirmed refundable payment and order balance.

Cancelling an order does not by itself prove that a pending bank or provider transaction has stopped or reversed.

Where payment was already successful before cancellation, the amount must be handled through the applicable refund process.

Where a successful payment arrives after an order was cancelled, returned, completed, or otherwise closed, Inkora may record the payment without automatically reopening the order.

Inkora will review whether the appropriate outcome is refund, fulfilment by agreement, replacement order, store credit where offered and accepted, or another lawful resolution.

Contact Inkora first when a recognised transaction has a product, delivery, cancellation, return, or refund issue. A payment dispute or chargeback may require transaction records, delivery evidence, correspondence, refund information, and other supporting documentation to be provided to the payment provider or financial institution.

A customer should identify any unrecognised transaction promptly and protect the associated account, card, bank access, email, and device.

Inkora may suspend fulfilment, refund processing, account features, or related transactions while a payment dispute, chargeback, fraud report, or provider investigation is active, where reasonably necessary.

Inkora may accept, contest, or otherwise respond to a provider dispute based on the order, payment, delivery, return, refund, support, security, and communication records.

A chargeback does not automatically determine the underlying product, delivery, return, or contractual dispute between Inkora and the customer.

Nothing in this section prevents a customer from using a complaint or regulatory route available under applicable law.

Inkora does not intentionally request or store complete card numbers, card PINs, CVV codes, bank passwords, one-time passwords, or Paystack secret keys in the storefront application.

Paystack secret keys, webhook secrets, and other private gateway credentials must remain server-side and must never be sent to a customer.

Inkora uses measures such as customer ownership checks, CSRF protection, unique transaction references, server-side amount checks, HTTPS provider requests, provider verification, webhook signature validation, database locking, and idempotent reconciliation.

Customers should verify the website address, avoid public or untrusted devices where possible, protect one-time passwords, refuse remote-access requests, and never share secret credentials with support.

Report suspected phishing, substituted bank details, fake payment links, unauthorised transactions, or account compromise promptly.

Inkora processes payer name, email, telephone, payment method, amount, currency, status, transaction reference, gateway reference, receipt, refund, verification metadata, and related order information.

Payment providers, banks, card networks, fraud services, couriers, advisers, authorities, and other authorised recipients may process relevant information for payment, fulfilment, refund, dispute, fraud prevention, compliance, or legal purposes.

The privacy policy explains the applicable data categories, purposes, lawful bases, sharing, international processing, retention, security, and individual rights.

Do not put complete card information, bank passwords, PINs, OTPs, or payment secrets in contact enquiries, order notes, return evidence, or uploaded files.

Review the order and payment record in the customer account before contacting support.

Provide the order number, payment number or receipt number, amount, currency, payment date, payer name, and provider or bank reference where available.

Do not send secret authentication information. Where proof is necessary, conceal complete card numbers, account balances, unrelated transactions, and other unnecessary personal data.

Inkora may consult the payment provider, bank, courier, administrator, return record, refund record, or other relevant source while investigating the complaint.

Where the matter concerns a financial institution and is not resolved through its complaint process, the customer may use a complaint route available through the relevant regulator.

Inkora may update this policy to reflect payment methods, provider capabilities, fees, security controls, refund processes, dispute handling, legal requirements, or regulatory guidance.

The effective date identifies the current published version. Material changes may also be communicated through the storefront, checkout, customer account, or another appropriate channel.

A policy update does not retrospectively increase an amount already properly authorised or remove a right or remedy that applies to an existing transaction.