2 min read
Endpoint
| Method | POST |
| Path | /partner/v1/payments/links |
| Ring | partner (OAuth) |
| Auth | OAuth |
Request
A JSON body describing the payment to collect (amount, reference, the payer context). Requires payments:write and an Idempotency-Key.
Response
A JSON object with the provisioned payment link and its status. The link is created via a PISP (open-banking payment initiation) rail. This endpoint provisions a collection; it does not itself release Credicorp funds — money-out is a separate governed manual gate, the single hard control in the platform.
Errors & notes
Sub-limited to 10 req/s — each call provisions a PISP payment. A 422 for an invalid amount or reference; a 403 without payments:write. Always idempotent-key the call so a retry does not provision two links.
Frequently asked questions
Does provisioning a payment link move Credicorp money?
No. This collects a payment via PISP. Releasing Credicorp funds (money-out) is a separate, governed manual gate — the platform's single hard control — and is not triggered by this endpoint.
What rate limit applies?
A 10 req/s sub-limit on top of your tier's bucket, because each call provisions a real PISP payment. Send an idempotency key so a retry never double-provisions.
Funding for UK limited companies
Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.