# Geopagos Developers Documentation > Integration tools and developer documentation for the Geopagos payments platform: Mobile SDK, Payments APIs and notifications. - [Geopagos Developers Documentation](/index.md) ## documents ### apis-cross - [Payment plans](/documents/apis-cross/payment-plans.md): Available only for Tap to phone. - [Card types](/documents/apis-cross/payment-plans/card-types.md): Overview - [How to determine the card type](/documents/apis-cross/payment-plans/how-to-determine-card-type.md): Primary Account Number (PAN) - [Points of sale](/documents/apis-cross/points-of-sale.md): Overview ### authentication To obtain an auth token an HTTP request must be made to Geopagos’s authentication server, credentials will be provided separately. - [Authentication](/documents/authentication.md): To obtain an auth token an HTTP request must be made to Geopagos’s authentication server, credentials will be provided separately. ### errors | Code | Label | The Problem | The Fix | - [ISO declined codes](/documents/errors.md): | Code | Label | The Problem | The Fix | ### external-payments Overview - [External payments](/documents/external-payments.md): Overview - [Implementation](/documents/external-payments/Integration.md): Overview ### in-person-payments Overview - [In person payments](/documents/in-person-payments.md): Overview - [QR code](/documents/in-person-payments/qr.md): Overview - [QR Cancellation](/documents/in-person-payments/qr/cancellation.md): Overview - [QR Code generation](/documents/in-person-payments/qr/generation.md): Overview - [EMVCo QR tramma](/documents/in-person-payments/qr/generation/tramma.md): Overview - [QR Payment](/documents/in-person-payments/qr/payment.md): Overview - [Pay with cards](/documents/in-person-payments/qr/payment/cards.md): Overview - [Pay with transfer](/documents/in-person-payments/qr/payment/transfer.md): This payment method is only available in Argentina - [Types of QR codes](/documents/in-person-payments/qr/types-of-qr-codes.md): Static QR code - [Tap on phone](/documents/in-person-payments/tap-on-phone.md): Overview - [Implementation](/documents/in-person-payments/tap-on-phone/implementation.md): Overview - [ToPP Application](/documents/in-person-payments/tap-on-phone/topp.md): Overview - [Terminals](/documents/in-person-payments/terminals.md): Overview - [Bluetooth](/documents/in-person-payments/terminals/bluetooth.md): There are several readers available to use, and all of them share them same interface with the core of Readers SDK. - [Implementation](/documents/in-person-payments/terminals/implementation.md): Overview - [SmartPOS](/documents/in-person-payments/terminals/smartpos.md): Devices - [POS Mode](/documents/in-person-payments/terminals/smartpos/pos-mode.md): Overview - [Transactional API](/documents/in-person-payments/transactional.md): Overview - [Implementation](/documents/in-person-payments/transactional/implementation.md): Overview ### online-payments Overview - [Online payments](/documents/online-payments.md): Overview - [Checkout API](/documents/online-payments/checkout-api.md): Overview - [Plugins](/documents/online-payments/plugins.md): Overview - [Tiendanube](/documents/online-payments/plugins/tiendanube.md): Overview - [WooCommerce](/documents/online-payments/plugins/woocommerce.md): Overview - [Recurring Payments](/documents/online-payments/recurring-payments.md): Overview ## references ### api-legacy - [API References](/references/api-legacy/api-references.md): > **This is a legacy API.** - [Get receipt (PNG)](/references/api-legacy/receipt-get-png.md): Return the PNG base64 encoded - [Refund ecommerce sale](/references/api-legacy/refund-non-present.md): Refund ecommerce sale ### api-recurring The Recurring Payments API allows you to create, query, and manage subscription plans, customers, payment methods, subscriptions, and charges. - [Recurring Payments API](/references/api-recurring.md): The Recurring Payments API allows you to create, query, and manage subscription plans, customers, payment methods, subscriptions, and charges. - [Get charge by id](/references/api-recurring/charges/charges-get.md): Get full details of a specific charge including attempt history. - [Get charges](/references/api-recurring/charges/charges-list.md): Get a paginated list of charges. Filter by subscription_id, status, created_after, created_before, or search. - [Checkout](/references/api-recurring/checkout.md): Overview - [Get customer by id](/references/api-recurring/customers/customers-get.md): Get full details of a specific customer. - [Get customers](/references/api-recurring/customers/customers-list.md): Get a paginated list of customers. Filter by email, name, or created_after. - [Get customer payment methods](/references/api-recurring/customers/customers-payment-methods-list.md): Get all payment methods associated with a customer. Filter by type, status, or brand. - [Get customer subscriptions](/references/api-recurring/customers/customers-subscriptions-list.md): Get all subscriptions associated with a customer. Filter by status with pagination. - [Get payment method by id](/references/api-recurring/payment-methods/payment-methods-get.md): Get the details of a specific payment method. - [Create plan](/references/api-recurring/plans/plans-create.md): Create a new subscription plan. Response includes subscriptionUrl for checkout. - [Get plan by id](/references/api-recurring/plans/plans-get.md): Get a subscription plan by its identifier. - [Get plans](/references/api-recurring/plans/plans-list.md): Get a paginated list of subscription plans. - [Update plan](/references/api-recurring/plans/plans-update.md): Update an existing subscription plan. - [Cancel subscription](/references/api-recurring/subscriptions/subscriptions-cancel.md): Cancel a subscription. Changes status to cancelled and sets cancelled_at. - [Get subscription by id](/references/api-recurring/subscriptions/subscriptions-get.md): Get full details of a specific subscription. - [Get subscriptions](/references/api-recurring/subscriptions/subscriptions-list.md): Get a paginated list of subscriptions. Filter by customer_id, plan_id, status, created_after, created_before, or search. - [Update subscription](/references/api-recurring/subscriptions/subscriptions-update.md): Update specific fields of an existing subscription. All fields are optional; only sent fields are updated. ### api-wallet - [Generate token](/references/api-wallet/generate-token.md): Generate an Acceptor Token to be used in a payment. - [Get installments](/references/api-wallet/get-installments.md): Recives the order_Id, amount (if the order has the 'status' field with 'open_amount' value) and bins and return all available plans for the defined order. - [Get order payments](/references/api-wallet/get-order-payments.md): Get a payment from the given order_id - [Get payment](/references/api-wallet/get-payment.md): Retrieve a payment by reference number - [Interoperable QR (Argentina)](/references/api-wallet/interoperable-qr-argentina.md): This contract define the APIs exposed by acquirers to any wallet operating QR payment solutions inside Argentina. - [Make payment](/references/api-wallet/make-payment.md): Execute a payment from the given order_id ### api - [Create authorization](/references/api/create-authorization.md): Allow to create an authorization for a payment authorized externally - [Confirm a payment](/references/api/payment-confirm.md): Confirm an in progress present payment. - [Check 3DS enrollment](/references/api/payment-ecommerce-3-ds-check-enrollment.md): Checks if the card is enrolled in 3D Secure authentication and returns the authentication URL if required. - [Confirm payment](/references/api/payment-ecommerce-confirm.md): Confirms a pending ecommerce payment transaction. - [Execute payment](/references/api/payment-ecommerce-execute.md): Executes the payment transaction after initialization and any required authentication steps. - [Initialize payment](/references/api/payment-ecommerce-initialize.md): Initializes an ecommerce payment transaction with the provided payment method and plan. - [Get installment options](/references/api/payment-ecommerce-installments.md): Returns available installment plans for a card based on the BIN and billing information. - [Validate OTP](/references/api/payment-ecommerce-otp-validate.md): Validates the One-Time Password (OTP) sent to the cardholder for authentication. - [Get authorization by reference number](/references/api/payment-history-authorization-by-reference.md): Gets complete authorization data by reference number for final state transactions including payment intent information. - [Get payment intent](/references/api/payment-history-payment-intent.md): See all the information of a payment intent with all related authorizations through the payment intent id. - [Search payments](/references/api/payment-history-search.md): Search and return payments made in the last six months from the search date. - [Start payment (without GeoPagos BackOffice)](/references/api/payment-initialize.md): Start a new payment using Readers SDK (without GeoPagos BackOffice). - [Create a payment link](/references/api/payment-link-create.md): Creates a payment link that can be shared with customers to allow them to make the payment. - [Get payment link](/references/api/payment-link-get.md): Retrieves the details of an existing payment link by its ID. - [Upload signature](/references/api/payment-present-signature.md): Add a signature to a payment. - [Start payment](/references/api/payment-present-start.md): Start a new payment using Readers SDK. - [Start payment (with Intent)](/references/api/payment-present-start-intent.md): Start a new payment using Readers SDK with payment intent for Caja POS. - [Cancel QR code](/references/api/payment-qr-cancel.md): Cancel a QR code generated for point-of-sale transactions. - [Generate QR code](/references/api/payment-qr-generate.md): Generate QR tramma that will be added to an image - [Start payment](/references/api/payment-tap-to-phone-start.md): Start a new payment using TTP SDK. - [Tokenize card](/references/api/payment-token-create.md): Creates a secure token for a credit or debit card with enhanced features including channel support, device tokenization, and payment link association. When channels includes RECURRING, additional validations are required (holder name, email, card type, brand). - [Send email voucher](/references/api/payment-voucher-email.md): Allows you to send the voucher by email - [Get PDF voucher](/references/api/payment-voucher-pdf.md): Generate and download a PDF voucher for an authorization through the payment reference number. - [Get PNG voucher](/references/api/payment-voucher-png.md): Generate and download a PNG voucher for an authorization through the payment reference number to be used with the SmartPOS's printer. - [Payments API](/references/api/payments-api.md): The Payments API allows you to interact directly with all the information you need to develop your payments solution. - [Get payment plans](/references/api/plan-resolve.md): Return a list of available installments through the card BIN - [Confirm payment plan selection](/references/api/plan-select.md): Confirm payment plan selection - [Update point of sale](/references/api/point-of-sale-update.md): Update point of sale - [Create a point of sale](/references/api/points-of-sale-create.md): Create a point of sale - [Delete point of sale](/references/api/points-of-sale-delete.md): Delete point of sale - [Get point of sale](/references/api/points-of-sale-get.md): Get point of sale - [Create intent](/references/api/points-of-sale-intent.md): Allow to create an intent associated to a POS, optionally if Currency and QR nodes are sended it will creates a QR. - [Cancel Payment Intent](/references/api/points-of-sale-intent-cancel.md): Cancels a payment intent associated to a point of sale. - [Cancel Intents by POS](/references/api/points-of-sale-intents-cancel-all.md): Cancels all pending payment intents associated to a point of sale. - [Search points of sale](/references/api/points-of-sale-list.md): Search points of sale - [Cancel Refund Pending by POS](/references/api/points-of-sale-refunds-cancel-pending.md): Cancels all pending refunds associated to a point of sale. - [Create a Refund](/references/api/points-of-sale-refunds-create.md): Initiates a refund process for a previously completed transaction. - [Confirm a refund](/references/api/refund-confirm.md): Confirm an in progress refund. - [Start a refund for ecommerce sale](/references/api/refund-ecommerce-start.md): Start a new refund for an ecommerce channel - [Start a refund using a device](/references/api/refund-present-start.md): Start a new refund using a physical reader - [Start a refund for Qr sale](/references/api/refund-qr-start.md): Start a new refund for a Qr channel and payment method type transfer - [Start a refund using ToPP](/references/api/refund-tap-to-phone-start.md): Start a new refund using tap to phone - [Start annulment authorization](/references/api/transaction-annulments.md): Attempt to perform an annulment. - [Confirm annulment authorization](/references/api/transaction-annulments-confirm.md): Attempt to confirm an annulment. - [Start refund authorization](/references/api/transaction-refunds.md): Attempt to perform a refund. - [Confirm refund authorization](/references/api/transaction-refunds-confirm.md): Attempt to confirm a refund. - [Start sale authorization](/references/api/transaction-sales.md): Attempt to perform a sale. - [Confirm sale authorization](/references/api/transaction-sales-confirm.md): Attempt to confirm a sale. ### gateway-query - [Gateway Query](/references/gateway-query/gateway-query.md): A programmatic query service for gateway transactions - [Get a list of payments transactions.](/references/gateway-query/get-a-list-of-payments-transactions.md): It is recommended to use [filter] or [page] to improve the query. - [Get a list of sale transactions.](/references/gateway-query/get-a-list-of-sale-transactions.md): It is recommended to use [filter] or [page] to improve the query. - [Get the sale transaction that match the given payment id.](/references/gateway-query/get-the-sale-transaction-that-match-the-given-payment-id.md): Get the sale transaction that match the given payment id. ### notifications What is the event model? - [Introduction](/references/notifications.md): What is the event model? - [Event: Commission Calculated](/references/notifications/events/commission-calculated.md): Schema definition - [Event: Merchant Transaction Completed](/references/notifications/events/merchant-transaction-completed.md): Schema definition - [Event: Transaction completed](/references/notifications/events/transaction-completed.md): Schema definition ### plugins - [Plugins integration](/references/plugins/integration.md): Choose one of the available plugins below to understand how merchants can seamlessly integrate the plugin once - [Tiendanube integration guide](/references/plugins/integration/tiendanube.md): Pre-condition - [WooCommerce integration guide](/references/plugins/integration/woocommerce.md): Pre-condition ### sdk - [Terminals SDK](/references/sdk/bluetooth-readers.md) - [Android](/references/sdk/bluetooth-readers/android.md) - [Changelog](/references/sdk/bluetooth-readers/android/Changelog.md): All notable changes to this project will be documented in this file. - [Device Connection](/references/sdk/bluetooth-readers/android/connected-devices.md): Note: If you prefer the older connection flow, you can continue to use it without any - [Introduction](/references/sdk/bluetooth-readers/android/Fake Reader/introduction.md): Overview - [Predefined Cards](/references/sdk/bluetooth-readers/android/Fake Reader/predefinedCards.md): Overview - [Using Custom Behaviors](/references/sdk/bluetooth-readers/android/Fake Reader/usingCustomBehaviors.md): Overview - [Using Predefined Behaviors](/references/sdk/bluetooth-readers/android/Fake Reader/usingPredefinedBehaviors.md): Overview - [Installation and configuration](/references/sdk/bluetooth-readers/android/installation-configuration.md): Basic steps for installation and configuration of the native Android SDK. - [MoreFun Device Properties Configuration](/references/sdk/bluetooth-readers/android/MoreFun SmartPOS/device-properties-configuration.md): The MoreFun SmartPOS SDK allows you to configure various device properties directly from your application, including kiosk mode and permissions. - [Customize PIN keyboard](/references/sdk/bluetooth-readers/android/MoreFun SmartPOS/pin-keyboard-customization.md): To configure the texts displayed on the MoreFun reader's PIN screen, it's necessary to input the texts within the SDKMoreFunKeyboardTexts object. - [Use of printer (Deprecated)](/references/sdk/bluetooth-readers/android/MoreFun SmartPOS/printer.md): Note: Please see the new procedure to manage the printer in this section - [Contactless PIN Decider](/references/sdk/bluetooth-readers/android/Plugins/contactless-pin-decider.md): Overview - [Printer](/references/sdk/bluetooth-readers/android/printer.md): Create printer - [Scanning](/references/sdk/bluetooth-readers/android/scanning.md): Scan devices - [SDK Javadoc](/references/sdk/bluetooth-readers/android/sdk-javadoc.md): SDK Javadoc - [Transaction](/references/sdk/bluetooth-readers/android/transaction.md): Transaction flow and transaction intent - [Use of printer (Deprecated)](/references/sdk/bluetooth-readers/android/Urovo SmartPOS/printer.md): Note: Please see the new procedure to manage the printer in this section - [Urovo configuration](/references/sdk/bluetooth-readers/android/Urovo SmartPOS/urovo-configuration.md): Customize PIN keyboard - [Fallback](/references/sdk/bluetooth-readers/fallback.md): Normally, a terminal should not allow magnetic stripe transactions with a chip-enabled card. - [Payments](/references/sdk/bluetooth-readers/iOS.md): An easy to integrate solution to accomplish payments, refunds and cancellations alongside a card reader - [Changelog](/references/sdk/bluetooth-readers/iOS/Changelog.md): All notable changes to this project will be documented in this file. - [PAN Hash](/references/sdk/bluetooth-readers/iOS/Plugins/panHash.md): Overview - [Signature](/references/sdk/bluetooth-readers/iOS/Plugins/Signature.md): Overview - [React Native](/references/sdk/bluetooth-readers/react-native.md): The SDK provides multiple options for your workflow. - [Transactional data](/references/sdk/bluetooth-readers/sdk.md) - [Required data](/references/sdk/bluetooth-readers/sdk/required-data.md): * Only applies for Android SDK - [Required data (JSON)](/references/sdk/bluetooth-readers/sdk/required-data-json.md): * Only applies for Android SDK - [Collect logs](/references/sdk/collect-logs.md): The Readers SDK provides a mechanism to collect logs, when the Readers SDK is initialized it's possible to provide an - [Device configurations](/references/sdk/configurations.md): There are certain configurations that can be done on the fly before each transaction, such as terminal capabilities, - [CVM Limit](/references/sdk/configurations/cvm-limit.md): Overview - [PIN support](/references/sdk/pin-support.md): Overview - [Invocation SDK (ToPP)](/references/sdk/tap-on-phone.md): Overview - [Android](/references/sdk/tap-on-phone/android.md): Overview - [React Native](/references/sdk/tap-on-phone/react-native.md): The @geopagos/react-native-softpos-sdk package wraps the native ToPP (Tap on Phone with PIN) SDK for React Native applications. It exposes a TypeScript API to initialize the SDK, retrieve device and application metadata, and execute sale transactions through the certified standalone ToPP app. - [How to update readers](/references/sdk/update-readers.md): This section provides a technical explanation of how to update readers using the SDK in iOS, Android, and React Native. Below, you will find step-by-step instructions to manage a reader update — from creating the configurator to providing the device and configuration. ## bug-report In the case that a bug is found, logs should be shared to be able to identify the issue. The bug report must contain: - [Report a bug](/bug-report.md): In the case that a bug is found, logs should be shared to be able to identify the issue. The bug report must contain: