The following documentation describes the APIs available for PayIn and PayOut processes with GuardPay.
\nUrl: https://sandboxclient.guardpayapp.com
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"29465958","collectionId":"36bb0c1c-6499-47e7-aefc-d893077ffa57","publishedId":"2sBXinFpZx","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-03-29T03:03:47.000Z"},"item":[{"name":"Authentication","item":[{"name":"LogIn","id":"d09bd1ea-1cbe-4fc6-a26d-d6f20e43ba04","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"\t\t{\r\n \"User\": \"User\",\r\n \"Password\": \"Password\",\r\n \"Code\": \"Code\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://sandboxclient.guardpayapp.com/Api/Aplication/Login","description":"Functions
\nControl access to requests.
\nComply with security regulations for confidential information.
\nGenerate a required bearer token for each request. (This ensures that only the user can view their own information.)
\nThe generated token will be valid for 3 hours from its date and time of issuance. After this time, the token will automatically expire and a new one must be generated to continue using the services or making authenticated requests.
\nCreate payment link with paycheck interface
\nTo test PSE, select Banco Union Colombiana and request instructions for testing status changes on the platform.
\nTo test the Bancolombia button, it will only work between 7am and 5pm Colombia time in the sandbox environment.
\nTo test Nequi Push, keep in mind that it doesn't have a sandbox environment, so any tests you perform will be effective and will reduce balances if they accept payments from the app, just like it works in production.
\nCreate a direct PSE payment link
\nTo perform effective testing on bank code, send code 1022 and request instructions for testing state changes.
\nThis payment method does not have a sandbox environment, neither for direct calls nor through our checkout process.
\nTherefore, when this payment method is accessed through our sandbox, it is essentially a call to Nequi in production. Users must provide a phone number that has a Nequi account to ensure the transaction is successful.
On the other hand, when executed through any of the Nequi Push flows, a payment request will be sent to the entered number, and the payment will be processed if accepted.
Create a direct bancolombia button
\nThe testing environment for this payment method only operates from 7 am to 5 pm Colombian time
\nRequest disbursement of available funds.
\nSend to the client's primary and registered bank in Transfiya
\nPrioritize the bank: NEQUI
\nThis API generates dynamic validation to determine the best flow for sending funds to the customer via their selected bank.
\nFirst, it validates using the fastest and most immediate method, which is breb. If it cannot find the account in breb, it validates via Trasfiya, listing all the banks the customer uses. If it fails to validate either of these methods, it sends the payout via ACH, respecting its processing cycles.
\nWhen a payout status update occurs, the system sends an automatic notification via webhook to the URL configured by the client.
\nThe notification is sent to the route previously registered in the NotifyUrl field when the payout request was made.
{
\"IdDispersion\":\"10\",
\"descripcionEstado\":\"Pending Confirmation\",
\"idEstado\":\"5\",
\"mensaje\":\"Payment pending confirmation\"
}
Once the webhook notification is received, it is recommended to confirm the transaction status by making a request to the Data PayOut method.
\nThis allows you to validate and reconfirm the current information of the payout process directly from the system.
\nWhen there is an update in the status of a PayIn transaction, the system automatically sends a notification via webhook to the endpoint configured by the client.
\nThe URL where this webhook is sent must be previously provided by the client to the GuardPay team, since it is configured internally within the system.
\n{
\"idTransaccion\":\"10\",
\"descripcionEstado\":\"Pending Confirmation\",
\"idEstado\":\"5\",
\"mensaje\":\"Payment pending confirmation\"
}
Once the webhook notification is received, it is recommended to confirm the transaction status by making a request to the PayIn Status method.
\nThis allows you to validate and reconfirm the current information of the payment process directly from the system.
\n","_postman_id":"7fe87f26-35a2-4f71-ac4a-219dbebee5ff"}]}