Branded money, delivered intelligently
The Berkeley API, provides a Restful JSON API for clients to pay customers, suppliers, and employees, around the world via physical card, virtual prepaid cards, or real-time transfers. Our PCI-compliant platform enabled fast and secure real-time transactions using new payment and transfer services, supported by Visa and Mastercard.
Base URLs
Staging Environment: <https://api.staging.pungle.co>
Production Environment: <https://api.pungle.io>
Available endpoints
This API documentation includes details required to integrate to any of our product APIs, including:
CARD ISSUING
This set of API endpoints allow you to create Prepaid Card Programs within the Berkeley Payments platform which you can use to issue physical or virtual Visa or Mastercard prepaid cards.
DIRECTSEND
DirectSend enables real-time fund transfer to any Visa cardholder. You’ll receive real-time authorization of a transaction’s success.
The recipient only needs to provide card details to the sender - no bank routing numbers.
You can use these endpoints for real-time funds disbursements, P2P transfers and Prepaid Loads.
The majority of funds reach the recipient’s account within 30 minutes
DEBT COLLECTION
Debt Collection endpoints allow you to provide your Collections team the ability to receive payments on outstanding collections in real-time.
3D-SECURE
Combined with DirectSend allows you to reduce chargebacks and shift liability for transactions.
Request Formats
All requests should be made using JSON and include a Content Type and Accept header.
Idempotency
The Berkeley API supports idempotency for transaction requests. This allows users to retry transaction requests without performing the same action more than once. For example, if a transaction request fails due to a network connection error, you can send another transaction request with the same idempotency key to ensure that the transaction is not created again.
To perform idempotent transaction requests, provide an additional idempotency_key in the body of the request. This key must be unique (we suggest using GUID/UUIDS) for each transaction operation in a 24 hour period.