Download the PHP package naykel/payit without Composer
On this page you can find all versions of the php package naykel/payit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package payit
Short Description Payment gateways package for NayKel applications
License MIT
Homepage https://naykel.com.au
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package payit
NAYKEL Payment Management Package
-
Add check to make sure .env is set
- update the
resolvemethod in thePaymentPlatformResolverto be a more updated Laravel way of resolving the platform. - remove auth login used for development in layouts
- Route fires the handle payment method passing in the amount
- Create and return the payment intent.
- The PaymentIntent includes a client secret that the client side uses to securely complete the payment process.
What to Do After Creating a PaymentIntent Store the PaymentIntent ID: You need to store the PaymentIntent ID somewhere safe (e.g., in a session or database) because it will be used later to confirm the payment. This is useful in case you need to retrieve or confirm the payment later.
Send the client_secret to the Frontend: The client_secret is required on the client side to confirm the payment and to allow Stripe to communicate with the client. The frontend will use this client_secret to confirm the payment, either via Stripe Elements or Stripe's hosted Checkout page.
Confirm the Payment: Once the PaymentIntent is created, you’ll either confirm it on the client side or backend side (based on your flow). If using the client-side approach, Stripe will handle any 3D Secure or authentication challenges. If you're processing everything backend-side, you can confirm the payment manually.
