Package paymentcryptographydata provides the API client, operations, and parameter types for Payment Cryptography Data Plane.
Package payment contains a simplified API of go-perun.
Package tarlanpaymentsgateway provide ability to make requests to Tarlan Payments Gateway API v3.
Package wos leverages the [Wallet Of Satoshi] REST API to process Bitcoin payments.
Golang bindings for the Mpesa Payment API (see https://openapiportal.m-pesa.com), to easily make your MPESA payments ready to GO.
Package be2bill implements client access to the Be2bill merchant API defined at http://developer.be2bill.com/API. Every initial transaction is made using a secure form. The Form Client API exposes methods that return the HTML code for payment or authorization buttons. The first step is to build a client for the given environment, using your credentials: To build a payment form button, call: Authorization form buttons are created similarly, except that the method to call is `BuildAuthorizationFormButton` that takes the same parameters. An authorization must be captured using the `Capture` method of the Direct Link Client API. All operations that do not require interactive data input from the client can be made using HTTP POST calls to the be2bill servers. The Direct Link Client API is an abstraction layer for these calls. Just like the Form Client API, the first step is to build a client for the given environment, using your credentials: Then, for example to capture a previously authorized transaction, call: Please note that access to the Direct Link Client API is not enabled by default. This service can only be activated by your account manager based on specific criteria. Please contact him or the support team for more information.
Package dpo provides functionality for interacting with DPO Group's payment gateway from Go applications. Currently the module only supports performing payments through DPOs verify token workflow. You are recommended to set the user agent for the client to some string that identifies your application. The dpo package exposes errors that are thrown from DPO API.
Package pay is a golang SDK for the Bronzecod payments REST API
Package paypal defines types and operations used to access the Paypal API The following authorization operations are defined for Payment: authorization: lookup, capture, reauthorize, and void authorized payments GET /v1/payments/authorization/<Authorization-Id> POST /v1/payments/authorization/<Authorization-Id>/capture POST /v1/payments/authorization/<Authorization-Id>/void POST /v1/payments/authorization/<Authorization-Id>/reauthorize Package paypal defines types and operations used to access the Paypal API The following billing-agreement operations are defined for payments: POST /v1/payments/billing-agreements POST /v1/payments/billing-agreements/<Payment-Token>/agreement-execute GET, PATCH /v1/payments/billing-agreements/<Agreement-Id> POST /v1/payments/billing-agreements/<Agreement-Id>/suspend POST /v1/payments/billing-agreements/<Agreement-Id>/re-activate POST /v1/payments/billing-agreements/<Agreement-Id>/cancel POST /v1/payments/billing-agreements/<Agreement-Id>/bill-balance POST /v1/payments/billing-agreements/<Agreement-Id>/set-balance GET /v1/payments/billing-agreements/<Agreement-Id>/transactions Package paypal defines types and operations used to access the Paypal API The following billing-plan operations are defined for payments: POST /v1/payments/billing-plans GET /v1/payments/billing-plans GET, PATCH /v1/payments/billing-plans/<Plan-Id> Package paypal defines types and operations used to access the Paypal API The following capture operations are defined for Payment: capture: lookup and refund captured payments GET /v1/payments/capture/<Capture-Id> POST /v1/payments/capture/<Capture-Id>/refund Package paypal defines types and operations used to access the Paypal API The following identity operations are defined POST /v1/identity/openidconnect/tokenservice GET /v1/identity/openidconnect/userinfo/?schema=<Schema> Package paypal defines types and operations used to access the Paypal API The following oreder operations are defined for Payment: order: manage orders GET /v1/payments/orders/<Order-Id> POST /v1/payments/orders/<Order-Id>/authorize POST /v1/payments/orders/<Order-Id>/do-void POST /v1/payments/orders/<Order-Id>/capture POST /v1/payments/capture/<Capture-Id>/refund Package paypal defines types and operations used to access the Paypal API The following payment operations are defined for Payment: payment: create,execute, update and lookup payments GET, POST /v1/payments/payment GET, PATCH /v1/payments/payment/<Payment-Id> POST /v1/payments/payment/<Payment-Id>/execute Package paypal defines types and operations used to access the Paypal API The following refund operations are defined for Payment: refund: lookup refund details GET /v1/payments/refund/<Refund-Id> Package paypal defines types and operations used to access the Paypal API Once a Payment is executed it becomes a Sale The following sale operations are defined for Payment: sale: lookup and refund completed payments GET /v1/payments/sale/<Transaction-Id> POST /v1/payments/sale/<Transaction-Id>/refund
Package paddle is an HTTP API client for the Paddle payment processing service. This package is unmaintained. It does not receive support or security updates. Please do not attempt to use it in production.
// 2021 Moses Narrow // // Skycoin Payment modal web app and api // // custom payment gateway integration with snipcart.com of skycoin and btcpayserver //
Package paypayopa provides SDK to use PayPay Open Payment API.
Package balanced provides a client implementation for the Balanced Payments API.
Package beanstream supplies the 3 APIs for processing payments: PaymentsAPI ProfilesAPI ReportingAPI Each API has its own Passcode and processes against your Merchant ID.
Package coveralls provide functions to interact with Coveralls API
Package beanstream supplies the 3 APIs for processing payments: PaymentsAPI ProfilesAPI ReportingAPI Each API has its own Passcode and processes against your Merchant ID.
Package paddle is an HTTP API client for the Paddle payment processing service.
Package beanstream supplies the 3 APIs for processing payments: PaymentsAPI ProfilesAPI ReportingAPI Each API has its own Passcode and processes against your Merchant ID.
Package Intouchpay provides a Go client for the IntouchPay Payments Gateway API.